Re: [SeaBIOS] [Qemu-devel] SeaVGABIOS and winxp
Michael Tokarev wrote: > Maybe this Standard VGA should be named something like Old VGA? IBM PC/XT/AT 128K VGA ? //Peter ___ SeaBIOS mailing list SeaBIOS@seabios.org http://www.seabios.org/mailman/listinfo/seabios
Re: [SeaBIOS] [Qemu-devel] SeaVGABIOS and winxp
On Mon, Apr 16, 2012 at 02:44:28AM +0400, Michael Tokarev wrote: > On 16.04.2012 02:22, Kevin O'Connor wrote: > > Select VGA_BOCHS in Kconfig for the qemu "standard" vga. The > > "standard vga" option in seabios kconfig is for emulating old IBM 128K > > vga cards (ie, not super vga) - I suppose this is a bit misleading. > > Oh. Indeed, VGA_BOCHS works, and it is _very_ similar to how > vgabios from bochs project works. > > And indeed, this is quite a bit confusing. The menut text is also > a bit interesting, -- "Bochs DISPI interface VGA BIOS" (what is > "DISPI" ?). The "DISPI" refers to the custom protocol that is used to transmit VBE requests between the vga bios and bochs (and is also implemented in qemu). Unfortunately, there aren't well recognized names for these interfaces. I'm open to changing the Kconfig descriptions if there are better names. -Kevin ___ SeaBIOS mailing list SeaBIOS@seabios.org http://www.seabios.org/mailman/listinfo/seabios
Re: [SeaBIOS] [Qemu-devel] SeaVGABIOS and winxp
On 16.04.2012 02:22, Kevin O'Connor wrote: > Select VGA_BOCHS in Kconfig for the qemu "standard" vga. The > "standard vga" option in seabios kconfig is for emulating old IBM 128K > vga cards (ie, not super vga) - I suppose this is a bit misleading. Oh. Indeed, VGA_BOCHS works, and it is _very_ similar to how vgabios from bochs project works. And indeed, this is quite a bit confusing. The menut text is also a bit interesting, -- "Bochs DISPI interface VGA BIOS" (what is "DISPI" ?). Maybe this Standard VGA should be named something like Old VGA? Testing further Thanks! /mjt ___ SeaBIOS mailing list SeaBIOS@seabios.org http://www.seabios.org/mailman/listinfo/seabios
Re: [SeaBIOS] [Qemu-devel] SeaVGABIOS and winxp
On Mon, Apr 16, 2012 at 01:58:47AM +0400, Michael Tokarev wrote: > On 16.04.2012 01:07, Kevin O'Connor wrote: > > On Mon, Apr 16, 2012 at 12:17:09AM +0400, Michael Tokarev wrote: > >> On 15.04.2012 06:48, Kevin O'Connor wrote: > >>> * Many enhancements to VGA BIOS code - it should now be feature complete > >>> with LGPL vgabios. > >> > >> This is something which prompted me to test the new release, > >> but it gives... interesting results. > >> > >> WinXP guest is unable to find drivers for the video adaptor > >> with -vga std and this vgabios.bin, not even its "standard VGA" > >> fallback driver. The device in question is detected as "Other > >> devices / Video controller (VGA compat.)", and its identification > >> looks like: > >> > >> PCI\VEN_1234&DEV_&SUBSYS_11001AF4&REV_00\3&13C0B0C5&0&10 > >> > >> This appears to be bogus somehow, no? > > > > It seems to work okay for me. What did you select in Kconfig, where > > did you put the resulting out/vgabios.bin file, and what emulator are > > you using? > > Kconfig was all defaults except VGA ROM pieces (which are off > by default). I selected VGA_STANDARD_VGA, VGA_VBE, VGA_PCI and > left OVERRIDE_PCI_ID UNselected, since I didn't know what to > put there. Maybe the last item was my mistake. Select VGA_BOCHS in Kconfig for the qemu "standard" vga. The "standard vga" option in seabios kconfig is for emulating old IBM 128K vga cards (ie, not super vga) - I suppose this is a bit misleading. -Kevin ___ SeaBIOS mailing list SeaBIOS@seabios.org http://www.seabios.org/mailman/listinfo/seabios
Re: [SeaBIOS] [Qemu-devel] SeaVGABIOS and winxp
On 16.04.2012 01:58, Michael Tokarev wrote: > On 16.04.2012 01:07, Kevin O'Connor wrote: >> On Mon, Apr 16, 2012 at 12:17:09AM +0400, Michael Tokarev wrote: >>> On 15.04.2012 06:48, Kevin O'Connor wrote: * Many enhancements to VGA BIOS code - it should now be feature complete with LGPL vgabios. >>> >>> This is something which prompted me to test the new release, >>> but it gives... interesting results. >>> >>> WinXP guest is unable to find drivers for the video adaptor >>> with -vga std and this vgabios.bin, not even its "standard VGA" >>> fallback driver. The device in question is detected as "Other >>> devices / Video controller (VGA compat.)", and its identification >>> looks like: >>> >>> PCI\VEN_1234&DEV_&SUBSYS_11001AF4&REV_00\3&13C0B0C5&0&10 The identification is the same as with seabios-1.6.2 and vgabios-0.6 - the "other vgabios" from bochs project. I just tried to re-install the video driver in 1.6.2 & 0.6, by deleting the device in device manager and rebooting the virtual machine - and it is unable to find any drivers too, saying this is some "Other device - vga compatible", -- i.e. exactly as with 1.7 and vgarom from it. The only difference is that with 1.6.2 & vgabios, even if the device is listed as "other device", there are a ton of various video modes available, while with 1.7 & vga rom from it, only one mode -- 640x480, 16 colors -- is available. >>> This appears to be bogus somehow, no? Bogus or not, but it was the same with bochs vgabios.. :) Thank you! /mjt ___ SeaBIOS mailing list SeaBIOS@seabios.org http://www.seabios.org/mailman/listinfo/seabios
Re: [SeaBIOS] [Qemu-devel] SeaVGABIOS and winxp
On 16.04.2012 01:07, Kevin O'Connor wrote: > On Mon, Apr 16, 2012 at 12:17:09AM +0400, Michael Tokarev wrote: >> On 15.04.2012 06:48, Kevin O'Connor wrote: >>> * Many enhancements to VGA BIOS code - it should now be feature complete >>> with LGPL vgabios. >> >> This is something which prompted me to test the new release, >> but it gives... interesting results. >> >> WinXP guest is unable to find drivers for the video adaptor >> with -vga std and this vgabios.bin, not even its "standard VGA" >> fallback driver. The device in question is detected as "Other >> devices / Video controller (VGA compat.)", and its identification >> looks like: >> >> PCI\VEN_1234&DEV_&SUBSYS_11001AF4&REV_00\3&13C0B0C5&0&10 >> >> This appears to be bogus somehow, no? > > It seems to work okay for me. What did you select in Kconfig, where > did you put the resulting out/vgabios.bin file, and what emulator are > you using? Kconfig was all defaults except VGA ROM pieces (which are off by default). I selected VGA_STANDARD_VGA, VGA_VBE, VGA_PCI and left OVERRIDE_PCI_ID UNselected, since I didn't know what to put there. Maybe the last item was my mistake. The binaries were put into right place where qemu-kvm picked them -- -bios /path/to/seabios/git/out/bios.bin, and vgabios.bin into the standard qemu-kvm directory, as vgabios-stdvga.bin. I think I learned where to put this stuff by now, after maintaining Debian package of qemu-kvm for over 2 years... ;) This is qemu-kvm 1.0, I haven't tried with current qemu git version. > Also, if using qemu/kvm add "-chardev stdio,id=seabios -device > isa-debugcon,iobase=0x402,chardev=seabios" to the command line and > post the resulting debug log. Here it is: Start bios (version rel-1.7.0-0-ga026308-dirty-20120416_09-gandalf) Ram Size=0x4000 (0x high) Relocating init from 0x000e4360 to 0x3ffe1bb0 (size 58148) CPU Mhz=3217 === PCI bus & bridge init === PCI: pci_bios_init_bus_rec bus = 0x0 === PCI device probing === Found 6 PCI devices (max PCI bus is 00) === PCI new allocation pass #1 === PCI: check devices === PCI new allocation pass #2 === PCI: init bases bus 0 (primary) type io max 40 sum 50 base c000 size 40: 1 bar(s), c000 -> c03f size 10: 1 bar(s), c040 -> c04f type mem max 1 sum 11000 base febe size1: 1 bar(s), febe -> febe size 1000: 1 bar(s), febf -> febf0fff type prefmem max 100 sum 100 base fd00 size 100: 1 bar(s), fd00 -> fdff PCI: map device bdf=00:00.0 PCI: map device bdf=00:01.0 PCI: map device bdf=00:01.1 bar 4, addr c040, size 10 [io] PCI: map device bdf=00:01.3 PCI: map device bdf=00:02.0 bar 0, addr fd00, size 100 [prefmem] bar 6, addr febe, size 1 [mem] PCI: map device bdf=00:03.0 bar 0, addr c000, size 40 [io] bar 1, addr febf, size 1000 [mem] PCI: init bdf=00:00.0 id=8086:1237 PCI: init bdf=00:01.0 id=8086:7000 PCI: init bdf=00:01.1 id=8086:7010 PCI: init bdf=00:01.3 id=8086:7113 PCI: init bdf=00:02.0 id=1234: PCI: init bdf=00:03.0 id=1af4:1001 PIIX3/PIIX4 init: elcr=00 0c Found 1 cpu(s) max supported 1 cpu(s) MP table addr=0x000fdb00 MPC table addr=0x000fdb10 size=224 SMBIOS ptr=0x000fdae0 table=0x000fd9d0 size=263 ACPI DSDT=0x3fffe470 ACPI tables: RSDP=0x000fd9a0 RSDT=0x3fffe430 Scan for VGA option rom Running option rom at c000:0003 Start SeaVGABIOS (version rel-1.7.0-0-ga026308-dirty-20120416_11-gandalf) enter vga_post: a=0010 b= c= d= ds= es=f000 ss= si= di=d0a0 bp= sp=6e6a cs=f000 ip=c60c f=6e9a Turning on vga text mode console set VGA mode 3 SeaBIOS (version rel-1.7.0-0-ga026308-dirty-20120416_09-gandalf) Found 1 lpt ports Found 1 serial ports ATA controller 1 at 1f0/3f4/0 (irq 14 dev 9) ATA controller 2 at 170/374/0 (irq 15 dev 9) found virtio-blk at 0:3 ebda moved from 9fc00 to 9dc00 Searching bootorder for: /pci@i0cf8/*@3 DVD/CD [ata1-0: QEMU DVD-ROM ATAPI-4 DVD/CD] Searching bootorder for: /pci@i0cf8/*@1,1/drive@1/disk@0 PS2 keyboard initialized All threads complete. Scan for option roms Searching bootorder for: /rom@genroms/vapic.bin drive 0x000fd950: PCHS=8322/16/63 translation=lba LCHS=522/255/63 s=8388608 Running option rom at c880:0003 Returned 57344 bytes of ZoneHigh e820 map has 7 items: 0: - 0009dc00 = 1 RAM 1: 0009dc00 - 000a = 2 RESERVED 2: 000f - 0010 = 2 RESERVED 3: 0010 - 3fffe000 = 1 RAM 4: 3fffe000 - 4000 = 2 RESERVED 5: feffc000 - ff00 = 2 RESERVED 6: fffc - 0001 = 2 RESERVED enter handle_19: NULL Booting from Hard Disk... Booting from :7c00 set VGA mode 12 pnp call arg1=0 set VGA mode 3 set VGA mode 12 VBE mode set: 102 set VGA mode 102 VBE mode set: 102 set VGA mode 102 set VGA mode 12 set VGA mode 12 [win displays login p
Re: [SeaBIOS] SeaVGABIOS and winxp
On Mon, Apr 16, 2012 at 12:17:09AM +0400, Michael Tokarev wrote: > On 15.04.2012 06:48, Kevin O'Connor wrote: > > * Many enhancements to VGA BIOS code - it should now be feature complete > > with LGPL vgabios. > > This is something which prompted me to test the new release, > but it gives... interesting results. > > WinXP guest is unable to find drivers for the video adaptor > with -vga std and this vgabios.bin, not even its "standard VGA" > fallback driver. The device in question is detected as "Other > devices / Video controller (VGA compat.)", and its identification > looks like: > > PCI\VEN_1234&DEV_&SUBSYS_11001AF4&REV_00\3&13C0B0C5&0&10 > > This appears to be bogus somehow, no? It seems to work okay for me. What did you select in Kconfig, where did you put the resulting out/vgabios.bin file, and what emulator are you using? Also, if using qemu/kvm add "-chardev stdio,id=seabios -device isa-debugcon,iobase=0x402,chardev=seabios" to the command line and post the resulting debug log. -Kevin ___ SeaBIOS mailing list SeaBIOS@seabios.org http://www.seabios.org/mailman/listinfo/seabios
Re: [SeaBIOS] [Qemu-devel] [ANNOUNCE] SeaBIOS 1.7.0
On 15.04.2012 06:48, Kevin O'Connor wrote: > The 1.7.0 version of SeaBIOS has now been released. For more > information on the release, please see: > > http://seabios.org/Releases > > > New in this release: > > * Many enhancements to VGA BIOS code - it should now be feature complete with > LGPL vgabios. This is something which prompted me to test the new release, but it gives... interesting results. WinXP guest is unable to find drivers for the video adaptor with -vga std and this vgabios.bin, not even its "standard VGA" fallback driver. The device in question is detected as "Other devices / Video controller (VGA compat.)", and its identification looks like: PCI\VEN_1234&DEV_&SUBSYS_11001AF4&REV_00\3&13C0B0C5&0&10 This appears to be bogus somehow, no? Thanks! /mjt ___ SeaBIOS mailing list SeaBIOS@seabios.org http://www.seabios.org/mailman/listinfo/seabios
Re: [SeaBIOS] [PATCH v2] x86emu: Correctly handle 0x66 prefix for some instructions
What is the outcome of this patch? I mean, does it actually fix something visible, instead of a potential problem? [] >>> Anyone interested in this ? Is there a maintainer for x86emu ? The >>> MAINTAINERS file in xorg-docs doesn't mention anything about it. >> >> CCed: Adam Jackson >> >> Adam, you seem to be the maintainer of the xorg vesa driver. I think >> this patch is closely related. Would you mind taking a look at it ? I asked another question related to xorg vesa driver, also related to qemu, about it being unable to find available resolutions when run under qemu -- this: http://lists.x.org/archives/xorg-devel/2012-March/030037.html Is this 0x66 issue related to my question somehow? :) Thanks, /mjt ___ SeaBIOS mailing list SeaBIOS@seabios.org http://www.seabios.org/mailman/listinfo/seabios
Re: [SeaBIOS] [Qemu-devel] [ANNOUNCE] SeaBIOS 1.7.0
On 15.04.2012 06:48, Kevin O'Connor wrote: > The 1.7.0 version of SeaBIOS has now been released. For more > information on the release, please see: > > http://seabios.org/Releases Um. I can't compile it here, due to an error in ./tools/buildversion.sh. $ sh -x ./tools/buildversion.sh out/vgaversion.c VAR16 + OUTFILE=out/vgaversion.c + VAR16MODE=VAR16 + [ -d .git ] + git describe --tags --long --dirty + VERSION=rel-1.7.0-0-ga026308 + date +%Y%m%d_%H%M%S + hostname + VERSION=rel-1.7.0-0-ga026308-20120415_235702-gandalf + echo Version: rel-1.7.0-0-ga026308-20120415_235702-gandalf Version: rel-1.7.0-0-ga026308-20120415_235702-gandalf + [ VAR16 == VAR16 ] [: 1: VAR16: unexpected operator + cat AFIAK, "==" operator is a bash(?) extension, standard POSIX shell only mentions "=" operator. Changing this "==" to "=" makes it buildable. Thanks, /mjt ___ SeaBIOS mailing list SeaBIOS@seabios.org http://www.seabios.org/mailman/listinfo/seabios
Re: [SeaBIOS] [ANNOUNCE] SeaBIOS 1.7.0
Great! :) Nice to see a new release out. Please make a notice about the release on the front page of the seabios website. On Sun, Apr 15, 2012 at 4:48 AM, Kevin O'Connor wrote: > The 1.7.0 version of SeaBIOS has now been released. For more > information on the release, please see: > > http://seabios.org/Releases > > > New in this release: > > * Many enhancements to VGA BIOS code - it should now be feature complete with > LGPL vgabios. > * Support for virtio-scsi. > * Improved USB drive (usb-msc) support. > * Several USB controller bug fixes and improvements. > * Runtime ACPI AML PCI hotplug construction. > * Support for running on i386 and i486 CPUs. > * Enhancements to PCI init when running on emulators. > * Several bug fixes > > > For information on obtaining SeaBIOS, please see: > > http://seabios.org/Download > > -Kevin > > ___ > SeaBIOS mailing list > SeaBIOS@seabios.org > http://www.seabios.org/mailman/listinfo/seabios ___ SeaBIOS mailing list SeaBIOS@seabios.org http://www.seabios.org/mailman/listinfo/seabios
Re: [SeaBIOS] BEV and bootorder
On Sun, Apr 15, 2012 at 02:39:45PM +0200, Fred . wrote: > 2012/4/15 Gleb Natapov : > > On Sun, Apr 15, 2012 at 02:24:05PM +0200, Fred . wrote: > >> Why would anyone want to define some devices as unbootable? > >> > > Because he does not want to boot from them. > > Then the partition should not be flagged as a boot partition, and it > won't be booted from. > Then it proceeds to try to boot from the next device. Adding flag to qemu is easier then modifying partitions. In reality all partitions are marked as boot partition during format. And there are other bootable devices besides HDs. > > > >> On Sun, Apr 15, 2012 at 8:57 AM, Gleb Natapov wrote: > >> > On Sat, Apr 14, 2012 at 11:19:31PM -0400, Kevin O'Connor wrote: > >> >> On Thu, Apr 12, 2012 at 01:30:36PM -0600, Steve Goodrich wrote: > >> >> > I'm working towards a goal of having specific devices be bootable, and > >> >> > *only* those devices. For example, if my bootorder file specifies > >> >> > SATA > >> >> > drive 3, I do not want it to try SATA drives 0, 1, and 2, nor any > >> >> > other HDD > >> >> > or floppy that it finds. > >> >> > > >> >> > My first question is: how do I do this? > >> >> > >> >> There is no current way to do this. I suppose one could code support > >> >> for a "stop boot" option to the boot order file - so that if it was > >> >> listed in the file the boot would stop after trying all options prior > >> >> to it. > >> >> > >> > I thought to add skipboot file. If device is in skipboot file it is not > >> > considered for booting from. > >> > > >> >> > If that can't be answered, can someone explain to me the relationship > >> >> > between the bootorder file and the BEV (Boot Execution Vector) > >> >> > configured in > >> >> > boot.c? > >> >> > >> >> All possible boot options (both BEV and BCV) are assembled in a sorted > >> >> list pointed to by boot.c:BootList. The bootorder file alters the > >> >> default sort order of that list. During the latter parts of the POST > >> >> phase, the BCVs are executed and only BEVs remain. The list of BEVs > >> >> is generated from the BootList. So, in a nutshell, the bootorder file > >> >> determines the order of the BEVs that SeaBIOS will attempt to boot > >> >> from. > >> >> > >> >> -Kevin > >> >> > >> >> ___ > >> >> SeaBIOS mailing list > >> >> SeaBIOS@seabios.org > >> >> http://www.seabios.org/mailman/listinfo/seabios > >> > > >> > -- > >> > Gleb. > >> > > >> > ___ > >> > SeaBIOS mailing list > >> > SeaBIOS@seabios.org > >> > http://www.seabios.org/mailman/listinfo/seabios > > > > -- > > Gleb. -- Gleb. ___ SeaBIOS mailing list SeaBIOS@seabios.org http://www.seabios.org/mailman/listinfo/seabios
Re: [SeaBIOS] BEV and bootorder
Why would anyone want to define some devices as unbootable? On Sun, Apr 15, 2012 at 8:57 AM, Gleb Natapov wrote: > On Sat, Apr 14, 2012 at 11:19:31PM -0400, Kevin O'Connor wrote: >> On Thu, Apr 12, 2012 at 01:30:36PM -0600, Steve Goodrich wrote: >> > I'm working towards a goal of having specific devices be bootable, and >> > *only* those devices. For example, if my bootorder file specifies SATA >> > drive 3, I do not want it to try SATA drives 0, 1, and 2, nor any other HDD >> > or floppy that it finds. >> > >> > My first question is: how do I do this? >> >> There is no current way to do this. I suppose one could code support >> for a "stop boot" option to the boot order file - so that if it was >> listed in the file the boot would stop after trying all options prior >> to it. >> > I thought to add skipboot file. If device is in skipboot file it is not > considered for booting from. > >> > If that can't be answered, can someone explain to me the relationship >> > between the bootorder file and the BEV (Boot Execution Vector) configured >> > in >> > boot.c? >> >> All possible boot options (both BEV and BCV) are assembled in a sorted >> list pointed to by boot.c:BootList. The bootorder file alters the >> default sort order of that list. During the latter parts of the POST >> phase, the BCVs are executed and only BEVs remain. The list of BEVs >> is generated from the BootList. So, in a nutshell, the bootorder file >> determines the order of the BEVs that SeaBIOS will attempt to boot >> from. >> >> -Kevin >> >> ___ >> SeaBIOS mailing list >> SeaBIOS@seabios.org >> http://www.seabios.org/mailman/listinfo/seabios > > -- > Gleb. > > ___ > SeaBIOS mailing list > SeaBIOS@seabios.org > http://www.seabios.org/mailman/listinfo/seabios ___ SeaBIOS mailing list SeaBIOS@seabios.org http://www.seabios.org/mailman/listinfo/seabios
Re: [SeaBIOS] BEV and bootorder
2012/4/15 Gleb Natapov : > On Sun, Apr 15, 2012 at 02:24:05PM +0200, Fred . wrote: >> Why would anyone want to define some devices as unbootable? >> > Because he does not want to boot from them. Then the partition should not be flagged as a boot partition, and it won't be booted from. Then it proceeds to try to boot from the next device. > >> On Sun, Apr 15, 2012 at 8:57 AM, Gleb Natapov wrote: >> > On Sat, Apr 14, 2012 at 11:19:31PM -0400, Kevin O'Connor wrote: >> >> On Thu, Apr 12, 2012 at 01:30:36PM -0600, Steve Goodrich wrote: >> >> > I'm working towards a goal of having specific devices be bootable, and >> >> > *only* those devices. For example, if my bootorder file specifies SATA >> >> > drive 3, I do not want it to try SATA drives 0, 1, and 2, nor any other >> >> > HDD >> >> > or floppy that it finds. >> >> > >> >> > My first question is: how do I do this? >> >> >> >> There is no current way to do this. I suppose one could code support >> >> for a "stop boot" option to the boot order file - so that if it was >> >> listed in the file the boot would stop after trying all options prior >> >> to it. >> >> >> > I thought to add skipboot file. If device is in skipboot file it is not >> > considered for booting from. >> > >> >> > If that can't be answered, can someone explain to me the relationship >> >> > between the bootorder file and the BEV (Boot Execution Vector) >> >> > configured in >> >> > boot.c? >> >> >> >> All possible boot options (both BEV and BCV) are assembled in a sorted >> >> list pointed to by boot.c:BootList. The bootorder file alters the >> >> default sort order of that list. During the latter parts of the POST >> >> phase, the BCVs are executed and only BEVs remain. The list of BEVs >> >> is generated from the BootList. So, in a nutshell, the bootorder file >> >> determines the order of the BEVs that SeaBIOS will attempt to boot >> >> from. >> >> >> >> -Kevin >> >> >> >> ___ >> >> SeaBIOS mailing list >> >> SeaBIOS@seabios.org >> >> http://www.seabios.org/mailman/listinfo/seabios >> > >> > -- >> > Gleb. >> > >> > ___ >> > SeaBIOS mailing list >> > SeaBIOS@seabios.org >> > http://www.seabios.org/mailman/listinfo/seabios > > -- > Gleb. ___ SeaBIOS mailing list SeaBIOS@seabios.org http://www.seabios.org/mailman/listinfo/seabios
Re: [SeaBIOS] BEV and bootorder
On Sun, Apr 15, 2012 at 02:24:05PM +0200, Fred . wrote: > Why would anyone want to define some devices as unbootable? > Because he does not want to boot from them. > On Sun, Apr 15, 2012 at 8:57 AM, Gleb Natapov wrote: > > On Sat, Apr 14, 2012 at 11:19:31PM -0400, Kevin O'Connor wrote: > >> On Thu, Apr 12, 2012 at 01:30:36PM -0600, Steve Goodrich wrote: > >> > I'm working towards a goal of having specific devices be bootable, and > >> > *only* those devices. For example, if my bootorder file specifies SATA > >> > drive 3, I do not want it to try SATA drives 0, 1, and 2, nor any other > >> > HDD > >> > or floppy that it finds. > >> > > >> > My first question is: how do I do this? > >> > >> There is no current way to do this. I suppose one could code support > >> for a "stop boot" option to the boot order file - so that if it was > >> listed in the file the boot would stop after trying all options prior > >> to it. > >> > > I thought to add skipboot file. If device is in skipboot file it is not > > considered for booting from. > > > >> > If that can't be answered, can someone explain to me the relationship > >> > between the bootorder file and the BEV (Boot Execution Vector) > >> > configured in > >> > boot.c? > >> > >> All possible boot options (both BEV and BCV) are assembled in a sorted > >> list pointed to by boot.c:BootList. The bootorder file alters the > >> default sort order of that list. During the latter parts of the POST > >> phase, the BCVs are executed and only BEVs remain. The list of BEVs > >> is generated from the BootList. So, in a nutshell, the bootorder file > >> determines the order of the BEVs that SeaBIOS will attempt to boot > >> from. > >> > >> -Kevin > >> > >> ___ > >> SeaBIOS mailing list > >> SeaBIOS@seabios.org > >> http://www.seabios.org/mailman/listinfo/seabios > > > > -- > > Gleb. > > > > ___ > > SeaBIOS mailing list > > SeaBIOS@seabios.org > > http://www.seabios.org/mailman/listinfo/seabios -- Gleb. ___ SeaBIOS mailing list SeaBIOS@seabios.org http://www.seabios.org/mailman/listinfo/seabios
