On Wed, Jun 9, 2010 at 12:34 PM, Stefan Reinauer <[email protected]> wrote: > On 6/9/10 8:00 PM, Myles Watson wrote: >> On Wed, Jun 9, 2010 at 1:45 AM, Stefan Reinauer >> <[email protected]> wrote: >> >>> SeaBIOS VGA hooks for Getac P470 and Roda RK886EX notebooks >>> >> It seems surprising to want to make SeaBIOS have this much stuff >> that's board-specific. > int15 hooks are designed to be board specific. > >> It seems like a more generic way to set hooks >> from CBFS would be nice. >> > Loading an int handler dynamically from CBFS and linking it at runtime? > Sounds doable but complex. It may not be worth the trouble.
> As long as it's only 2 intel and a number of VIA based boards that > require a special int15 handler it might not be that bad. > > Generally it's also possible to locally patch the SeaBIOS source code. Sure. Harder for end users, but just as easy for developers. > The runtime distinction is only required if you want to use the same > SeaBIOS binary on several mainboards that require to have different > int15 handlers. > >> I'm thinking something like seabios/hooks which has a list of >> interrupts handlers and where they should be installed. >> > It would need to be 0xe0000 - 0xfffff unless we want to start cutting > out more memory. I meant where as in what interrupt to patch, not what address to run at. SeaBIOS should be able to use whatever address it wants to. > Alternatively we could add an SMI "function call" to coreboot that does > the deed. That would simplify the code in SeaBIOS significantly but add > more requirements for SMM. I'm not sure what's best. Maybe few enough boards will need their own handlers that it doesn't really matter. Thanks, Myles -- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
