[coreboot] Regarding offset adjustment for building coreboot.

Hi All, I have build coreboot with release payload. Name Offset Type Size bootsplash.img 0x0bootsplash 37443 cmos_layout.bin0x9280 cmos_layout 1132 fspd.bin 0x9740 (unknown)4608

Re: [coreboot] Regarding offset adjustment for building coreboot.

Hi Patrick, On 08.04.2016 09:57, Patrick Georgi via coreboot wrote: > 2016-04-08 9:51 GMT+02:00 rajashaker Goud : >> I have build coreboot with release payload. > > [ stripped to list only the empty regions] >> Name Offset Type

Re: [coreboot] Regarding offset adjustment for building coreboot.

Hi Rajashaker, On 08.04.2016 09:51, rajashaker Goud wrote: > So in my case i need to adjust the offset coz after config i have empty > space available. > please help me in changing the offset. > i dont have idea regarding which part of code need to change to adjust > offset. I don't know how to

Re: [coreboot] Regarding offset adjustment for building coreboot.

2016-04-08 11:17 GMT+02:00 Nico Huber : > you also stripped: > > fallback/payload 0x1b140payload 769955 > > I guess he means that a fresh build with a bigger (865KiB instead of > 752KiB) payload fails. Of course you're right. I misunderstood the

Re: [coreboot] Linux as payload

On 2016-04-07 06:31 PM, daoud yessine wrote: > Hi > > how to build coreboot with linux as payload ? > I need Bzimage only ? > what about the file system ? > > thanks > ᐧ Hello, I'm using a linux payload. Here are a few pitfalls you should mind: * Fedora's prebuild kernel doesn't work any

Re: [coreboot] Linux as payload

I use initramfs and it works wondefully well. Figures, Patrick Georgi did that code :-) ron -- coreboot mailing list: coreboot@coreboot.org https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] ASUS KFSN4-DRE (K8) Automated Test Failure [master]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/08/2016 11:29 AM, Raptor Engineering Automated Coreboot Test Stand wrote: > The ASUS KFSN4-DRE (K8) fails verification for branch master as of commit > 5a577251263369d259bee033e41584d7c562ca6d > > The following tests failed: > BOOT_FAILURE

Re: [coreboot] Regarding offset adjustment for building coreboot.

2016-04-08 9:51 GMT+02:00 rajashaker Goud : > I have build coreboot with release payload. [ stripped to list only the empty regions] > Name Offset Type Size > (empty)0xd8380null 48152 >

[coreboot] ASUS KFSN4-DRE (K8) Automated Test Failure [master]

The ASUS KFSN4-DRE (K8) fails verification for branch master as of commit 5a577251263369d259bee033e41584d7c562ca6d The following tests failed: BOOT_FAILURE Commits since last successful test: 5a57725 Revert "nb/amd/mct_ddr3: Enable DIMM parity when RDIMMs installed" ba817d0 nb/amd/mct_ddr3:

Re: [coreboot] Regarding offset adjustment for building coreboot.

Not knowing which platform this is makes it a little harder to determine what's locked in place. We'd also need to know if this is getting built from the top of the coreboot.org tree, an old coreboot.org commit or an private repo with many changes from coreboot.org. Microcode should be able to

[coreboot] New Defects reported by Coverity Scan for coreboot

Hi, Please find the latest report on new defect(s) introduced to coreboot found with Coverity Scan. 20 new defect(s) introduced to coreboot found with Coverity Scan. 152 defect(s), reported by Coverity Scan earlier, were marked fixed in the recent build analyzed by Coverity Scan. New

Re: [coreboot] Regarding offset adjustment for building coreboot.

The FSP is rebased with the Intel BCT tool, not the FITC tool. > On Apr 8, 2016, at 7:38 AM, Martin Roth wrote: > > Not knowing which platform this is makes it a little harder to > determine what's locked in place. We'd also need to know if this is > getting built from the

Re: [coreboot] Linux as payload

You'll want both. The file system is what goes in the initrd config option Add a payload (A Linux payload) ---> (bzImage) Linux path and filename () Linux command line () Linux initrd Martin On Thu, Apr 7, 2016 at 10:31 AM, daoud yessine wrote: > Hi > > how to

Re: [coreboot] Alix 2d13 coreboot breaking source

Hi Patrick Yes i rebuild the Compilers after every coreboot build. So the steps where 1.)Git bisect start 2.)Git bisect good 3.)Git bisect bad 4.)Make crossgcc-i386 5.)Make 6.)Check the coreboot Image live on physical alix 7.)Make clean 8.)Make

[coreboot] Alix 2d13 coreboot breaking source

Hi guys Finally i found out, which git commit broke coreboot to build for a «Alix 2d13». I used «git bisect» recommended by «PaulePanther» in october 2015 to identify the commit. A doc about the different git commits and their results can be found here:

Re: [coreboot] Cleaning up old commits in gerrit

All of the patches that have not been touched in at least 18 months have been abandoned. Here is the list of patches that were abandoned: https://review.coreboot.org/#/q/status:abandoned+comment:%22touched+in+18+months%22 If you see a patch in that list that you feel should be picked back up,

Re: [coreboot] Alix 2d13 coreboot breaking source

Just to clarify: Did you rebuild the compilers after applying that commit? It doesn't touch anything that ends up affecting the coreboot binaries with a given toolchain. 2016-04-08 21:47 GMT+02:00 Reto Rayen : > Hi guys > > > > Finally i found out, which git commit broke