Robo L wrote: > > I mean, that Grub print via lowlevel printig (int 0x10) with > proprietary string data. It's true that most BIOSes are proprietary and we're against non-free firmware. Unfortunately, however, most motherboards around aren't supported by any free firmware so we have to cope with what we have. We encourage you to use motherboards with free firmware. I'm aware of 3 categories of such: 1) Coreboot has made a great job in freeing x86-based mobos. You can consult their list here: http://www.coreboot.org/Supported_Motherboards 2) Touchbook by always innovating http://alwaysinnovating.com/home/index.htm claims to use U-Boot and supply the complete sources. I haven't checked this claim however 3) Yeeloong by Lemote http://www.lemote.com/english/yeeloong.html. It uses PMON, soon GRUB will work as firmware on it too (big parts are done) On BIOS grub uses its interrupts by default because this interface usually supports the hardware user has and on coreimg stage it allows to shave off few bytes. However we move to using our own drivers since firmware interface is often buggy and/or incomplete. > > Please can You tell me what is a reason? How is a solution? Is it a > correct by the licence? GRUB doesn't link with BIOS > > Many thanks > > Robo > > -- > ----------------------------------------- > E=mc2 > ------------------------------------------------------------------------ > > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > http://lists.gnu.org/mailman/listinfo/grub-devel >
-- Regards Vladimir 'φ-coder/phcoder' Serbinenko
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
