SeaBIOS

seabios@seabios.org

4 participants
3801 discussions

[ANNOUNCE] SeaBIOS 1.7.0
by Kevin O'Connor 17 Apr '12

17 Apr '12

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

8 17

Re: [SeaBIOS] BEV and bootorder
by Gleb Natapov 15 Apr '12

15 Apr '12

On Sun, Apr 15, 2012 at 02:39:45PM +0200, Fred . wrote: > 2012/4/15 Gleb Natapov <gleb(a)redhat.com>: > > 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 <gleb(a)redhat.com> 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(a)seabios.org > >> >> http://www.seabios.org/mailman/listinfo/seabios > >> > > >> > -- > >> > Gleb. > >> > > >> > _______________________________________________ > >> > SeaBIOS mailing list > >> > SeaBIOS(a)seabios.org > >> > http://www.seabios.org/mailman/listinfo/seabios > > > > -- > > Gleb. -- Gleb.

1 0

Re: [SeaBIOS] BEV and bootorder
by Gleb Natapov 15 Apr '12

15 Apr '12

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 <gleb(a)redhat.com> 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(a)seabios.org > >> http://www.seabios.org/mailman/listinfo/seabios > > > > -- > > Gleb. > > > > _______________________________________________ > > SeaBIOS mailing list > > SeaBIOS(a)seabios.org > > http://www.seabios.org/mailman/listinfo/seabios -- Gleb.

2 1

Re: [SeaBIOS] BEV and bootorder
by Kevin O'Connor 15 Apr '12

15 Apr '12

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. > 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

3 2

Re: [SeaBIOS] Is there a way to disable the LAN device in ICH chip?
by Srini Amble 14 Apr '12

14 Apr '12

On 04/13/2012 06:21 PM, Idwer Vollering wrote: > > > Op 13 april 2012 23:27 schreef Srini Amble <srini.amble(a)windriver.com > <mailto:srini.amble@windriver.com>> het volgende: > > I have an x86 board which has X58 and ICH10 chipset. If any of you > know how I can disable the LAN device in ICH chipset (dev ID 25 > and function number 0) in SeaBIOS then please share it with me. > > > How do you start SeaBIOS? E.G. if you use coreboot to start SeaBIOS > you can (AFAIK) disable the LAN device from devicetree.cb. SeaBIOS is the payload for coreboot in my case. Looking at the source files I have for coreboot and SeaBIOS I do not see reference to 'devicetree.cb' any where. Also, any pointer to how to disable the device in 'devicetree.cb' is much appreciated.

2 1

Is there a way to disable the LAN device in ICH chip?
by Srini Amble 13 Apr '12

13 Apr '12

I have an x86 board which has X58 and ICH10 chipset. If any of you know how I can disable the LAN device in ICH chipset (dev ID 25 and function number 0) in SeaBIOS then please share it with me.

2 1

BEV and bootorder
by Steve Goodrich 12 Apr '12

12 Apr '12

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? 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? Thanks! -- Steve G.

1 0

Why drive_s is allocated from f-segment?
by Gleb Natapov 12 Apr '12

12 Apr '12

Hi Kevin, Is there a reason why drive_s structures are allocated from f-segment? The space for f-segment allocations are barely sufficient for bios tables. -- Gleb.

2 4

Re: [SeaBIOS] From 16 bit to 32bit
by Kevin O'Connor 12 Apr '12

12 Apr '12

On Thu, Apr 12, 2012 at 04:10:21PM +0900, Daniel Castro wrote: > On Thu, Apr 12, 2012 at 9:34 AM, Kevin O'Connor <kevin(a)koconnor.net> wrote: > > On Wed, Apr 11, 2012 at 09:09:44PM +0900, Daniel Castro wrote: > >> Hello All, > >> > >> Since the hypercall on 16bit is not working, how can I transition the > >> CPU to 32bit while doing the I/O stuff. > >> And maybe get back to 16 Bit? > > > > See the call32() function. > > Thanks for the answer Kevin, correct me if I am wrong, but I can only > pass a single pointer argument to the function? Yes - one parameter to the target function. > Also in the pointer argument I get the return value, right? No, the return code of the target function becomes the return code of call32. -Kevin

1 0

Re: [SeaBIOS] From 16 bit to 32bit
by Kevin O'Connor 12 Apr '12

12 Apr '12

On Wed, Apr 11, 2012 at 09:09:44PM +0900, Daniel Castro wrote: > Hello All, > > Since the hypercall on 16bit is not working, how can I transition the > CPU to 32bit while doing the I/O stuff. > And maybe get back to 16 Bit? See the call32() function. -Kevin

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

SeaBIOS