Re: [coreboot] Coreboot and INT13H
On Sat, Jul 22, 2017 at 9:01 AM ingegneriafore...@alice.it < ingegneriafore...@alice.it> wrote: > \ > However this allow me to do the following question: in which a way should > be done the service "Eject Media" that corresponds to INT 13H, AH=46H ? It > seems to me that this service is executed, for example, when i need to > eject a usb stick. > no, it's not. It's not needed. Linux does not use it for example as far as I know, and has not for many years. > Can you confirm this ? and that is Coreboot is indipendent from the kernel > of a linux OS (in particular the grub 2) ? > It always has been, be design. But if grub 2 uses any BIOS services then it will need seabios there. > > 2 - The last question. I don't understand very well the answer of Ron: > "to expand on patrick's comment, any sort of output in the boot stage of > coreboot significantly slows boot time. This is not a problem on most > firmware, but on coreboot it's a big issue. Even the addition of 100 > milliseconds is a real detriment to boot time". > > Why ? > > > I'm not sure what your "Why?" is about, can you be more specific? ron -- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Coreboot and INT13H
to expand on patrick's comment, any sort of output in the boot stage of coreboot significantly slows boot time. This is not a problem on most firmware, but on coreboot it's a big issue. Even the addition of 100 milliseconds is a real detriment to boot time. -- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Coreboot and INT13H
2017-07-19 23:24 GMT+02:00 ingegneriafore...@alice.it < ingegneriafore...@alice.it>: > 1- where (the name of the file) the INT 13H is implemented in the coreboot > source code ? > It's not. coreboot doesn't provide BIOS services. For those, see seabios ( www.seabios.org) > 2- if the INT 13H interrupt, when invoked by OS (or application programs), > can do writing operations in the filesystem of the drive attached to the PC > or only limits to writing operations in memory regions different by the > filesystem ? > Not applicable 3- Is a way to see on the screen the fully sequence of operations coreboot > execute during the boot ? (i don't use QUEMU but program directly the bios > eeprom chip). coreboot boots too fast for any meaningful screen output so we dropped support for that years ago. There's a log in memory (cbmem -c) or on serial, if configured. Patrick -- Google Germany GmbH, ABC-Str. 19, 20354 Hamburg Registergericht und -nummer: Hamburg, HRB 86891, Sitz der Gesellschaft: Hamburg Geschäftsführer: Matthew Scott Sucherman, Paul Terence Manicle -- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
