Path link: https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2923/
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Dec 23 2019
Add PSA_DOOLBELL signal to assigned_signals
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2927/
Dec 20 2019
Bug spotted while creating test suite:
Add dependence deadlock check: https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2924/
Align psa_wait() to PSA FF 1.0.0
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2380/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2402/
Align psa_close to psa ff 1.0.0
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2487/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2444/
Detect the current handling handle in psa_call
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2768/
Enhance the psa_call to process the invalid message
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2769/
Add an ipc test for psa_call
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2818/
Align psa_version to PSA FF 1.0.0
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2920/
As the PSA FF 1.0.0 mentioned in 3.5.2:
Add a doc about how to add a secure partition: https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2921/
Dec 19 2019
Dec 18 2019
Keep this task here since there would be another update.
Now one handle could only have one message body, and this message body is allocated while handle is created. So there is no resource allocation issue for the message (we do have this problem for handle but this ticket is not the case). Close this task as done.
Dec 17 2019
Patch had been merged to the master branch.
Dec 16 2019
Dec 14 2019
Related reviews:
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2814/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2815/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2816/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2817/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/3046/
How can we add name? To do it we have to follow best write my essay sites where we are just waiting for those things where we just want to take from description and all which we need. So here are some simple method which tell you to add.
Dec 13 2019
Dec 12 2019
patches to implement panic-related functions:
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2779/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2780/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2781/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2782/
Dec 11 2019
Dec 6 2019
Related changes:
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2679/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2742/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2954/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/3139/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/3140/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/3141/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/3142/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/3143/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/3144/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/3145/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/3146/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/3147/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/3148/
Patch had been merged into the master branch.
The topic of the patches for this:
https://review.trustedfirmware.org/q/topic:%22out_of_tree_build%22+(status:open%20OR%20status:merged)
Dec 5 2019
Snapcraft distributes builds for the latest stable versions of CMake: https://snapcraft.io/cmake
Perhaps consider recommended it be installed through that? On Ubuntu it is as simple as sudo snap install cmake --classic.
Changes for this issue had been merged.
Dec 4 2019
Snapcraft distributes builds for the latest stable versions of CMake: https://snapcraft.io/cmake
Dec 2 2019
CC312 support on Musca-B1 was merged to master:
Nov 29 2019
Change for this issue: https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2661/
Nov 28 2019
Change for the following documents
- Code Generation With Jinja2
- Non-Secure Interrupt Handling
- Non-secure Client Management
- Secure Partition Interrupt Handling
- Uniform Secure Service Signature
Nov 27 2019
Issue for this change: https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2651/
@kevin-peng-hao has sent out the design in TF-M mailing list for review. Please check @ademars .
Nov 22 2019
Nov 21 2019
Fix issue if no RoT Service is defined in the services attribute, then at least one IRQ must be declared: https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2591/
Nov 20 2019
Related reviews:
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2568/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2569/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2570/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2571/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2572/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2573/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2574/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2575/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2576/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2577/
Nov 18 2019
Related changes:
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2458/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2521/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2522/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2523/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2524/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2525/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2526/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2527/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2528/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2529/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2530/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2531/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2532/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2533/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2534/
Nov 15 2019
Change for this issue had been merged.
Nov 14 2019
For 'Cooperative Scheduling Rules':
https://review.trustedfirmware.org/c/trusted-firmware-m/+/2466
Nov 13 2019
Nov 11 2019
Related patches:
Proposed implementation of this task: https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2450/
Change for this issue had been merged.
patches link:
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2445/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2446/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2447/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2448/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2449/