Dear coreboot readers!
This is the automatic build system of coreboot.
The developer "ruik" checked in revision 4265 to the coreboot repository. This caused the following changes:
Change Log: Following patch fixes the XIP computation issue. I removed the normal image because it was not working anyway (it was hardcoded) and because it allows me to fix the XIP base to something sane (and use generic computation and approach)
This board is bit tricky because until now it required the VGA BIOS on the flash start. XIP will work with 64KB aligned base, therefore the VGA ROM image must be aligned too to 64KB.
Signed-off-by: Rudolf Marek r.marek@assembler.cz Acked-by: Ronald G. Minnich rminnich@gmail.com
Build Log: Configuration of asus:m2v-mx_se has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=4265&device=m2v-mx_se&a...
If something broke during this checkin please be a pain in ruik's neck until the issue is fixed.
If this issue is not fixed within 24h the revision should be backed out.
Best regards, coreboot automatic build system
Hmm the ./buildtarget worked for me. I will try to fix it tomorrow. Too tired now. It seems I'm hit by some option caveat again. If someone knows, please help.
Thanks,
Rudolf
Hi all,
I'm not able to fix it. The ./buildtarget asus/m2v-mx_se and compilation works. The abuild build does not. Seems I'm missing a clue what is so different.Abuild seems to ignore the .../target/Config.lb. Because ifI put back default ROM_SIZE and FALLBACK_SIZE to ...mainboard/... it starts to compile again, but for some reason it wants to do the normal/fallback but only fallback should be build.
Anyone a hint how to fix that?
Thanks, Rudolf
-----Original Message----- From: coreboot-bounces@coreboot.org [mailto:coreboot-bounces@coreboot.org] On Behalf Of Rudolf Marek Sent: Monday, May 11, 2009 3:21 PM To: coreboot@coreboot.org Subject: Re: [coreboot] build service results for r4265
Hi all,
I'm not able to fix it. The ./buildtarget asus/m2v-mx_se and compilation works. The abuild build does not. Seems I'm missing a clue what is so different.Abuild seems to ignore the .../target/Config.lb. Because ifI put back default ROM_SIZE and FALLBACK_SIZE to ...mainboard/... it starts to compile again, but for some reason it wants to do the normal/fallback but only fallback should be build.
That's right. Abuild only uses Config-abuild.lb. Unless Config-abuild.lb is present, abuild generates its own.
I think the easiest fix here would be for you to make a Config-abuild.lb which is a copy of your Config.lb, but replace
payload ../payload.elf
with
payload __PAYLOAD__
The auto-generated Config-abuild.lb will always have a normal image.
Thanks, Myles