> > Actually that's what we do in the FILO payload.
What is libflashrom used for in FILO? Was it intended at some point that FILO be able to reflash the BIOS, or is it being used for something like reading the flash chip in order to load other things? -Matt On Thu, Feb 14, 2019 at 3:45 PM Nico Huber <nic...@gmx.de> wrote: > Hi Matt, > > On 14.02.19 18:56, Patrick Georgi via coreboot wrote: > > Am Do., 14. Feb. 2019 um 18:47 Uhr schrieb Vadim Bendebury > > <vben...@chromium.org>: > >> Why does it have to be done by Seabios as opposed to Linux? It is easy > >> to create a USB stick which would boot Linux compiled with permissions > >> needed and with startup files which will program the new firmware image. > >> This would be much easier to debug and modify when needed, right? > > I think the idea is to provide flashing from within the boot flow. But > > even then I wouldn't rely on SeaBIOS for that, but use libflashrom to > > build a payload: SeaBIOS can load other payloads, as can GRUB2, so > > that increases the potential user base of the flashing feature, and it > > would be smaller than a disk image of a Linux that's put into flash > > (which sounds rather convoluted to me). > > libflashrom and libpayload integrate very well. Actually that's what we > do in the FILO payload. The upstream code is stale, though, and won't > compile with current libflashrom. Let me know if you want to try that > path (FILO is a pain to compile atm). > > Nico >
_______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
