OP-TEE Firewall Framework: Revision history

20 November 2024

• curprev12:5812:58, 20 November 2024m6,231 bytes+22No edit summaryTag: 2017 source edit
  Approved on 13:50, 20 November 2024

24 October 2024

• curprev10:3410:34, 24 October 2024m6,209 bytes-1,868No edit summaryTag: 2017 source edit
  Approved on 11:49, 20 November 2024

23 October 2024

• curprev13:2013:20, 23 October 2024m8,077 bytes+263No edit summaryTag: 2017 source edit
• curprev12:5612:56, 23 October 2024m7,814 bytes+868→ Device tree configurationTag: 2017 source edit
• curprev12:4312:43, 23 October 2024m6,946 bytes+319→ Framework usage: review commentTag: 2017 source edit
• curprev12:3512:35, 23 October 2024m6,627 bytes+225→ Firewall controllers: review commentTag: 2017 source edit
• curprev11:0411:04, 23 October 2024m6,402 bytes+903typo + review commentsTag: 2017 source edit

22 October 2024

• curprev15:5515:55, 22 October 2024m5,499 bytes-71No edit summaryTag: 2017 source edit
• curprev15:5415:54, 22 October 2024m5,570 bytes-122No edit summaryTag: 2017 source edit
• curprev15:2415:24, 22 October 20245,692 bytes+5,692Created page with "<noinclude>{{ApplicableFor |MPUs list=STM32MP13x, STM32MP15x, STM32MP21x, STM32MP23x, STM32MP25x |MPUs checklist=STM32MP13x, STM32MP15x, STM32MP21x, STM32MP23x, STM32MP25x }}</noinclude> ==Framework purpose== There are now multiple hardware firewalls implemented across multiple products. Drivers are shared between these products, using the same code. When it comes to firewalls, the purpose mostly stays the same: Protect hardware resources. But the implementation differs..."Tag: 2017 source edit