-----Original Message----- From: Pattrick Hueper [mailto:phueper@hueper.net] Sent: Friday, December 19, 2008 1:38 PM To: Myles Watson Cc: jordan@cosmicpenguin.net; Coreboot Subject: Re: [coreboot] YABEL and images in LAR files
On Fri, Dec 19, 2008 at 8:37 PM, Myles Watson mylesgw@gmail.com wrote:
well following the BIOS spec (i think its somewhere in the PNP BIOS spec... i have to check... ) the BIOS copies the ROM to RAM... since YABEL uses its own "virtual" memory it _has_ to copy the ROM to its RAM...
Yes. Right now there's just a redundant copy, since Coreboot copies it
to
RAM too.
true, but YABEL still has to copy it, after all the code runs from copy... can we modify coreboot to not copy the image from ROM if YABEL is selected, but pass the location of the image in ROM to YABEL?
...
Currently, the ROM is always copied from the Expansion ROM bar of PCI devices.... i havent had to initialize any onboard devices. If there is a parameter to run_bios that points to the location of the Option ROM i could pass that parameter to YABEL and only use the Expansion ROM BAR if that parameter is not set (null?).
That's what I was thinking.
Ok, i will try to implement that and send patches.
That would be great. Once that's done I think I'll try YABEL on a "factory" BIOS from inside Coreboot. Qemu would be an easy place to try that.
Thanks, Myles