On 20.07.2008 22:57, ron minnich wrote: > On Wed, Jul 16, 2008 at 6:47 PM, Kevin O'Connor <[EMAIL PROTECTED]> wrote: > >> Hi Myles, >> >> On Wed, Jul 16, 2008 at 07:29:29PM -0600, Myles Watson wrote: >> >>>> Finding the option roms is easy - they are located between 0xc0000 and >>>> 0xe0000 and are 2KiB aligned. >>>> >>> That can be true after Coreboot copies them there. Devices which have >>> option ROMs on the card are located somewhere in the PCI address space until >>> they are copied. On-board devices have their option ROMs contained >>> somewhere in the BIOS chip. >>> >> Right. I'm a proponent of having coreboot be responsible for copying >> the option roms to their locations in ram. Once coreboot loads the >> option roms then seabios can easily locate and run them > > you're assuming they would all fit at one time into 64k. Not > necessarily the case. What has to happen is copy (or map) the rom, run > it, remove it, and so on. At least that's how I remember it working. > It was easier in the emulator as the copy step is not needed. >
If any of the option ROMs install interrupt handlers (video etc.) they may have to remain in memory after being run. > Whatever happens with this discussion, we still need to be able to run > with things like linux as payload and seabios not there. At linuxworld > next month, at least one booth will be showing Intel's rapidboot, > which we all know as linux-as-booloader. > > intel is showing that linux can be used as a bootloader. I wish they'd > gotten the memo 10 years ago but better late than never. > The most interesting thing about this is that they must have figured out a way to boot Windows from Linux. Maybe some of their code can be reused for SeaBIOS. Regards, Carl-Daniel -- http://www.hailfinger.org/ -- coreboot mailing list [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
