Marc Jones wrote: > > Myles Watson wrote: >> Here's my attempt at fixing abuild for serengeti_cheetah_fam10. >> >> It's pretty trivial, since I'm just using the ROM_IMAGE_SIZE in >> Config.lb and putting it in Config-abuild.lb. When I reduce this size >> (past what it is in Config-abuild.lb), it gives me the same overlap >> error in my system that abuild is seeing. >> >> I also added XIP_ROM_SIZE, although I admit freely that I don't know >> anything about this variable. I just wanted to make it match Marc's >> Config.lb. >> >> Maybe the right thing to do would be to remove both XIP_ROM_SIZE >> references in Config-abuild.lb >> >> Either way, I think the ROM_IMAGE_SIZE change will help. > > Myles, > > Thanks, the bigger problem is that the rom generated by the auto abuild > is larger than expected. We are investigating the tool chain. Once we > understand what is going on I will feel more comfortable with increasing > the ROM_IMAGE_SIZE. > > Marc > >
I made a very sexy picture of what a failover coreboot v2 image looks like and what ROM_IMAGE_SIZE and other variables are. http://www.coreboot.org/Anatomy_of_a_Failover_LinuxBIOSv2_Image Marc -- Marc Jones Senior Firmware Engineer (970) 226-9684 Office mailto:[EMAIL PROTECTED] http://www.amd.com/embeddedprocessors -- linuxbios mailing list linuxbios@linuxbios.org http://www.linuxbios.org/mailman/listinfo/linuxbios
