Re: [coreboot] cbfstool: CBFS alignment broken due to FMAP

[mailto:coreboot-boun...@coreboot.org] Im Auftrag von Ben Gardner Gesendet: Montag, 18. Januar 2016 21:54 An: Patrick Georgi Cc: coreboot Betreff: Re: [coreboot] cbfstool: CBFS alignment broken due to FMAP Thank you. That worked. On Mon, Jan 18, 2016 at 2:46 PM, Patrick Georgi <pgeo...@google.

Re: [coreboot] cbfstool: CBFS alignment broken due to FMAP

rick Georgi > Cc: coreboot > Betreff: Re: [coreboot] cbfstool: CBFS alignment broken due to FMAP > > Thank you. That worked. > > On Mon, Jan 18, 2016 at 2:46 PM, Patrick Georgi <pgeo...@google.com> wrote: >> 2016-01-18 21:34 GMT+01:00 Ben Gardner <gardner@gmail.com&

Re: [coreboot] cbfstool: CBFS alignment broken due to FMAP

2016-01-18 21:34 GMT+01:00 Ben Gardner : > Is there a work-around for this? For example, is there an option to > pad the FMAP out to 4 KB? The workaround is indeed to increase the FMAP region's size to 4K. To do this, edit $(top)/Makefile.inc, line 708 (since you're on x86,

Re: [coreboot] cbfstool: CBFS alignment broken due to FMAP

Thank you. That worked. On Mon, Jan 18, 2016 at 2:46 PM, Patrick Georgi wrote: > 2016-01-18 21:34 GMT+01:00 Ben Gardner : >> Is there a work-around for this? For example, is there an option to >> pad the FMAP out to 4 KB? > The workaround is indeed to

[coreboot] cbfstool: CBFS alignment broken due to FMAP

Hi all, With the latest cbfstool in master, the alignment option is broken in cbfstool. Or rather, the alignment is relative to the CBFS start, not the actual ROM address, and the 256-byte FMAP throws off the alignment. In my case, I have a ROM size of 16 MB and the BIOS region starts at