>> Could this section be updated in order to reduce the number of different
>> interpretations?
>
> Yes, it can be clarified. As Daniel says, this section is only
> intended for platforms where there is no other place to store
> firmware. If the OS and the firmware need to share a logical block
>
a
On Mon, Jul 22, 2024 at 2:46 PM Ghennadi Procopciuc
wrote:
>
> On 7/22/2024 2:45 PM, Daniel Thompson wrote:
> > On Fri, Jul 19, 2024 at 07:51:26PM +, Ghennadi Procopciuc wrote:
> >>> Yes, ideally this is what EBBR recommends as the second-best option (the
> >>> best
> >>> option being to u
On 7/22/2024 2:45 PM, Daniel Thompson wrote:
> On Fri, Jul 19, 2024 at 07:51:26PM +, Ghennadi Procopciuc wrote:
>>> Yes, ideally this is what EBBR recommends as the second-best option (the
>>> best
>>> option being to use a dedicated storage).
>>
>> Ok, I thought that the ideal case is when al
On Fri, Jul 19, 2024 at 07:51:26PM +, Ghennadi Procopciuc wrote:
> > Yes, ideally this is what EBBR recommends as the second-best option (the
> > best
> > option being to use a dedicated storage).
>
> Ok, I thought that the ideal case is when all firmware images are stored on a
> dedicated sto
> > Questions:
> > 1. Does the above paragraph mean that, if the device allows, all
> > firmware
> binaries (TF-A, U-Boot, and some others)
> > must be stored in a dedicated firmware partition formatted with a
> > FAT
> filesystem and GUID Partition Table (GPT)
> > disk layout
On Fri, Jul 19, 2024 at 02:12:59PM +, Ghennadi Procopciuc wrote:
> Greetings everyone,
>
> I came across the following paragraph while reading the 'Firmware Partition
> Filesystem' chapter from EBBR v2.2.0
> and I would like to clarify my understanding:
> Where possible, firmware images
Greetings everyone,
I came across the following paragraph while reading the 'Firmware Partition
Filesystem' chapter from EBBR v2.2.0
and I would like to clarify my understanding:
Where possible, firmware images and data should be stored in a
filesystem. Firmware can be stored either in a
