boot-architecture  

Messages by Thread

• • Re: eBPF as replacement for UEFi EBC and ACPI AML Leif Lindholm
  • Re: eBPF as replacement for UEFi EBC and ACPI AML Alexander Graf
  • Re: eBPF as replacement for UEFi EBC and ACPI AML Leif Lindholm
  • Re: eBPF as replacement for UEFi EBC and ACPI AML François Ozog
• DT Evo call today Bill Mills
• Today's DT Evo call canceled Bill Mills
• [EBBR PATCH] Relax Update requirements by dropping ESRT Grant Likely
  • Re: [EBBR PATCH] Relax Update requirements by dropping ESRT Heinrich Schuchardt
  • Re: [EBBR PATCH] Relax Update requirements by dropping ESRT Grant Likely
• Verified Boot for Embedded (VBE) proposal Simon Glass
• DT Evo call today July 12 Bill Mills
  • Re: DT Evo call today July 12 Bill Mills
• No EBBR Biweekly for 5th or 19th July Grant Likely
• FF-A watchdog service François Ozog
  • Re: FF-A watchdog service Heinrich Schuchardt
  • Re: FF-A watchdog service Tom Rini
  • Re: FF-A watchdog service François Ozog
  • Re: FF-A watchdog service François Ozog
• DTE call for June 28 canceled Bill Mills
• EBBR Biweekly for 2021-Jun-21 -- cancelled Grant Likely
• Devietree Eco Call Today Jun 14 3PM UTC Bill Mills
  • Re: Devietree Eco Call Today Jun 14 3PM UTC, Notes Bill Mills
• EBBR biweekly CANCELLED for 7th Jun Grant Likely
• DTE Meeting Monday May 31: Should we cancel? Bill Mills
  • Re: DTE Meeting Monday May 31: Should we cancel? Bill Mills
• Fwd: [SystemArchAC] SystemReady IR ACS Beta available for Certification Grant Likely
• RPI4 booting with SystemReady-IR flow François Ozog
  • Re: RPI4 booting with SystemReady-IR flow Bill Mills
  • Re: RPI4 booting with SystemReady-IR flow Bill Mills
  • Re: RPI4 booting with SystemReady-IR flow AKASHI Takahiro
  • Re: RPI4 booting with SystemReady-IR flow François Ozog
  • Re: RPI4 booting with SystemReady-IR flow Grant Likely
  • Re: RPI4 booting with SystemReady-IR flow François Ozog
  • Re: RPI4 booting with SystemReady-IR flow Heinrich Schuchardt
• EBBR Biweekly for 24 May 2021 Grant Likely
  • Re: EBBR Biweekly for 24 May 2021 Ilias Apalodimas
• DeviceTree Evolution call for Monday May 17 Bill Mills
  • Re: DeviceTree Evolution call for Monday May 17 Grant Likely
  • Re: DeviceTree Evolution call for Monday May 17 Frank Rowand
• [PATCH v4] Add RISC-V support content to the EBBR specification Atish Patra
  • Re: [PATCH v4] Add RISC-V support content to the EBBR specification Atish Patra
  • Re: [PATCH v4] Add RISC-V support content to the EBBR specification Grant Likely
  • Re: [PATCH v4] Add RISC-V support content to the EBBR specification Atish Patra
  • Re: [PATCH v4] Add RISC-V support content to the EBBR specification Grant Likely
  • Re: [PATCH v4] Add RISC-V support content to the EBBR specification Grant Likely
  • Re: [PATCH v4] Add RISC-V support content to the EBBR specification Matthias Brugger
  • Re: [PATCH v4] Add RISC-V support content to the EBBR specification Daniel Thompson
  • Re: [PATCH v4] Add RISC-V support content to the EBBR specification Grant Likely
  • Re: [PATCH v4] Add RISC-V support content to the EBBR specification Matthias Brugger
  • Re: [PATCH v4] Add RISC-V support content to the EBBR specification Grant Likely
  • Re: [PATCH v4] Add RISC-V support content to the EBBR specification Atish Patra
  • Re: [PATCH v4] Add RISC-V support content to the EBBR specification Grant Likely
  • Re: [PATCH v4] Add RISC-V support content to the EBBR specification Atish Patra
  • Re: [PATCH v4] Add RISC-V support content to the EBBR specification Atish Patra
  • Re: [PATCH v4] Add RISC-V support content to the EBBR specification Daniel Thompson
• Fwd: EBBR Testing topic for today? Grant Likely
  • Re: EBBR Testing topic for today? Masami Hiramatsu
  • Re: EBBR Testing topic for today? Grant Likely
  • Re: EBBR Testing topic for today? Masami Hiramatsu
  • Re: EBBR Testing topic for today? Masami Hiramatsu
  • Re: EBBR Testing topic for today? Grant Likely
  • Re: EBBR Testing topic for today? Masami Hiramatsu
  • Re: EBBR Testing topic for today? AKASHI Takahiro
  • Re: EBBR Testing topic for today? Masami Hiramatsu
  • Re: EBBR Testing topic for today? Grant Likely
  • Re: EBBR Testing topic for today? AKASHI Takahiro
  • Re: EBBR Testing topic for today? Vincent Stehlé
  • Re: EBBR Testing topic for today? Heinrich Schuchardt
  • Re: EBBR Testing topic for today? Vincent Stehlé
  • Re: EBBR Testing topic for today? Masami Hiramatsu
  • Re: EBBR Testing topic for today? Vincent Stehlé
  • Re: EBBR Testing topic for today? Masami Hiramatsu
• EBBR biweekly for 10 May 2021 Grant Likely
• Re: [System-dt] System Device Tree call - May 2021 Stefano Stabellini
  • Re: [System-dt] System Device Tree call - May 2021 Stefano Stabellini
  • RE: [System-dt] System Device Tree call - May 2021 Nathalie Chan King Choy
• [PATCH v3] Add RISC-V support content to the EBBR specification Atish Patra
  • Re: [PATCH v3] Add RISC-V support content to the EBBR specification Heinrich Schuchardt
  • Re: [PATCH v3] Add RISC-V support content to the EBBR specification Atish Patra
  • Re: [PATCH v3] Add RISC-V support content to the EBBR specification Heinrich Schuchardt
• How to add metadata to device-trees Heinrich Schuchardt
  • Re: How to add metadata to device-trees Joakim Bech
  • Re: How to add metadata to device-trees Heinrich Schuchardt
• Canceling meeting for Monday May 3 Bill Mills
• System Device Tree call - May 2021 Nathalie Chan King Choy
  • RE: System Device Tree call - May 2021 Nathalie Chan King Choy
• EBBR v2.0.0 released Grant Likely
• Reminder: EBBR Biweekly for 26 April 2021 Grant Likely
• FW update on A-class Arm devices Jose Marinho
  • Re: FW update on A-class Arm devices Heinrich Schuchardt
  • Re: FW update on A-class Arm devices Grant Likely
• Re: [v5.4 stable] arm: stm32: Regression observed on "no-map" reserved memory region Rob Herring
  • Re: [v5.4 stable] arm: stm32: Regression observed on "no-map" reserved memory region Ard Biesheuvel
  • Re: [v5.4 stable] arm: stm32: Regression observed on "no-map" reserved memory region Rob Herring
  • Re: [v5.4 stable] arm: stm32: Regression observed on "no-map" reserved memory region Florian Fainelli
  • Re: [v5.4 stable] arm: stm32: Regression observed on "no-map" reserved memory region Quentin Perret
  • Re: [v5.4 stable] arm: stm32: Regression observed on "no-map" reserved memory region Florian Fainelli
  • Re: [v5.4 stable] arm: stm32: Regression observed on "no-map" reserved memory region Florian Fainelli
  • Re: [v5.4 stable] arm: stm32: Regression observed on "no-map" reserved memory region Quentin Perret
  • Re: [v5.4 stable] arm: stm32: Regression observed on "no-map" reserved memory region Quentin Perret
  • Re: [v5.4 stable] arm: stm32: Regression observed on "no-map" reserved memory region Alexandre TORGUE
  • Re: [v5.4 stable] arm: stm32: Regression observed on "no-map" reserved memory region Quentin Perret
  • Re: [v5.4 stable] arm: stm32: Regression observed on "no-map" reserved memory region Alexandre TORGUE
  • Re: [v5.4 stable] arm: stm32: Regression observed on "no-map" reserved memory region Alexandre TORGUE
  • Re: [v5.4 stable] arm: stm32: Regression observed on "no-map" reserved memory region Quentin Perret
• DTE call today Bill Mills
  • Re: DTE call today François Ozog
  • Re: DTE call today Bill Mills
  • Re: DTE call today François Ozog
  • Re: DTE call today Frank Rowand
• Fwd: [TF-A] [RFC] TF-A threat model François Ozog
• Next week's reach out Council François Ozog
• EBBR Biweekly cancelled for today Grant Likely
• Hand over blocks in SynQuacer SoC Masami Hiramatsu
• Firmware: Sustainability vs planned obsolescence François Ozog
  • Re: Firmware: Sustainability vs planned obsolescence Loïc Minier
  • Re: Firmware: Sustainability vs planned obsolescence François Ozog
  • Re: Firmware: Sustainability vs planned obsolescence Heinrich Schuchardt
  • Re: Firmware: Sustainability vs planned obsolescence François Ozog
  • Re: Firmware: Sustainability vs planned obsolescence Heinrich Schuchardt
  • Re: Firmware: Sustainability vs planned obsolescence François Ozog
  • Re: Firmware: Sustainability vs planned obsolescence Loïc Minier
  • Re: [OCP-OSF] Firmware: Sustainability vs planned obsolescence ron minnich
  • Re: [OCP-OSF] Firmware: Sustainability vs planned obsolescence Loïc Minier
  • Re: [OCP-OSF] Firmware: Sustainability vs planned obsolescence ron minnich
  • Re: [OCP-OSF] Firmware: Sustainability vs planned obsolescence François Ozog
  • Re: [OCP-OSF] Firmware: Sustainability vs planned obsolescence Ryan O'Leary
  • Re: [OCP-OSF] Firmware: Sustainability vs planned obsolescence Loïc Minier
  • Re: [OCP-OSF] Firmware: Sustainability vs planned obsolescence ron minnich
  • Re: [OCP-OSF] Firmware: Sustainability vs planned obsolescence François Ozog
  • Re: [OCP-OSF] Firmware: Sustainability vs planned obsolescence ron minnich
  • Re: [OCP-OSF] Firmware: Sustainability vs planned obsolescence Leif Lindholm
  • Re: [OCP-OSF] Firmware: Sustainability vs planned obsolescence ron minnich
  • RE: [OCP-OSF] Firmware: Sustainability vs planned obsolescence Desimone, Nathaniel L
  • Re: [OCP-OSF] Firmware: Sustainability vs planned obsolescence ron minnich
  • Re: [OCP-OSF] Firmware: Sustainability vs planned obsolescence ron minnich
  • Re: [OCP-OSF] Firmware: Sustainability vs planned obsolescence François Ozog
• Trusted Substrate architecture call: HandOverBlocks discussion François Ozog
  • Re: Trusted Substrate architecture call: HandOverBlocks discussion Heinrich Schuchardt
  • Re: Trusted Substrate architecture call: HandOverBlocks discussion François Ozog
• Re: [TF-A] Glitching protection Joanna Farley
• Firmware FuSa workshop François Ozog
  • Re: Firmware FuSa workshop Heinrich Schuchardt
  • Re: Firmware FuSa workshop François Ozog
  • RE: [TF-A] Firmware FuSa workshop Miklos Balint
• Glitching protection François Ozog
  • Re: Glitching protection Heinrich Schuchardt
  • Re: Glitching protection Joakim Bech
  • Re: Glitching protection Heinrich Schuchardt
  • Re: Glitching protection François Ozog
  • Re: Glitching protection Heinrich Schuchardt
  • Re: Glitching protection Joakim Bech
  • Re: Glitching protection Ard Biesheuvel
  • Re: Glitching protection François Ozog
• DTE call today 4pm UK, noon US eastern Bill Mills
• Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages François Ozog
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Simon Glass
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages François Ozog
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages François Ozog
  • RE: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Harb Abdulhamid OS
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages François Ozog
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Simon Glass
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Joanna Farley
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Bill Fletcher
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Julius Werner
  • RE: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages raghu.ncstate
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Simon Glass
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Grant Likely
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Simon Glass
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Julius Werner
  • RE: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages raghu.ncstate
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages François Ozog
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Manish Pandey2
  • RE: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Harb Abdulhamid OS
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Simon Glass
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Okash Khawaja
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Joanna Farley
  • RE: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Madhukar Pappireddy
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Jeremy Linton
  • RE: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Madhukar Pappireddy
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Joanna Farley
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Joanna Farley
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Joanna Farley
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Joanna Farley
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Manish Pandey2
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages François Ozog
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Simon Glass
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages François Ozog
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Julius Werner
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Simon Glass
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Julius Werner
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages François Ozog
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Daniel Thompson
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Manish Pandey2
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Julius Werner
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages François Ozog
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Simon Glass
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Julius Werner
  • RE: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages raghu.ncstate
  • Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages Simon Glass

• Earlier messages
• Later messages