Nico Huber wrote:
> wear leveling
> ring buffer
> sanitation phase
> optimizing every update
> Defragmentation
..
> Might work?
Please don't invent a new format, don't reinvent JFFS2 and/or UBI..
Let's make CBFS work for this, please. Reusing the existing data
structure is incredibly valuable, ev
Hi Felix,
On 30.09.2017 20:28, Felix Held wrote:
> Hi!
>
>> Write strategy: Invalidate any entry with matching key, append after
>> last entry if there is enough space in the current erase block. If
>> not, finalize current erase block with an invalid entry spanning the
>> free space of the block
On 30.09.2017 19:28, Peter Stuge wrote:
> Nico Huber wrote:
>>> We already have a simple coreboot-native key-value store: CBFS
Well, I had a look at it now. And indeed it is a coreboot-native key-
value store and could be used in the same way I imagined my proposed
storage format. But it's not sim
Hi!
Write strategy: Invalidate any entry with matching key, append after
last entry if there is enough space in the current erase block. If
not, finalize current erase block with an invalid entry spanning the
free space of the block, write variable into next erase block. If we
run out of erase b
Nico Huber wrote:
> > We already have a simple coreboot-native key-value store: CBFS
>
> Well, I never looked close, but everybody kept telling me for years that
> CBFS is not designed for updates.
But it is!?
Not in-place updates, because CBFS isn't tied to eraseblock sizes,
but a CBFS entry co
On 30.09.2017 16:12, Peter Stuge wrote:
> Nico Huber wrote:
>> In-flash variable format
>>
>>
>> I like to keep things simple and assume that a key=value approach
>> suffices (for this layer). Though, as we have certainly to deal with
>> NOR flash chips (and their erase blo
Nico Huber wrote:
> In-flash variable format
>
>
> I like to keep things simple and assume that a key=value approach
> suffices (for this layer). Though, as we have certainly to deal with
> NOR flash chips (and their erase blocks), we can't just store things
> in a table t
Hi Melissa,
On 28.09.2017 07:59, Melissa Yi wrote:
> Hi All,
> Does anyone know how to implement variable read/write in coreboot?
> like: how to create a block nvram to be accessed by uefipayload?
I don't know any quick solution. Though, here are my thoughts on the
matter: AFAIK, coreboot cur
On Sat, Sep 30, 2017 at 08:37:55AM +, Thomasheidler via coreboot wrote:
> I have GRUB2 as a payload in coreboot and I am trying to have it load
> Trisquel 7.0 Live (Test Trisquel without installing) from an encrypted LUKS
> partition on a USB flash drive. I am able to decrypt the LUKS contain
Hello,
I have GRUB2 as a payload in coreboot and I am trying to have it load Trisquel
7.0 Live (Test Trisquel without installing) from an encrypted LUKS partition on
a USB flash drive. I am able to decrypt the LUKS container and GRUB finds the
Trisquel ISOLINUX menu, but fails to load the OS. W
Hi 799,
On 29.09.2017 13:34, One7two99 wrote:
> Hello Nico,
>
>> I suspect some misconfiguration or that something confuses the libpay-
>> load VGA driver (which these two secondary payload rely on).
>
> This might be true, but I don't understand why I can see the SeaBios
> Menu (Press ESC) and
11 matches
Mail list logo