Am Dienstag, den 19.03.2013, 22:18 -0400 schrieb Kevin O'Connor:
On Wed, Mar 20, 2013 at 12:59:53AM +0100, Paul Menzel wrote:
Am Dienstag, den 19.03.2013, 19:05 -0400 schrieb Kevin O'Connor:
Basically everything under the BIOS interfaces menu is low-level and
should not be changed without
Paul Menzel wrote:
it would be nice if it is clear for noobs like me, what certain
option do and what effects they have.
The good way to fix that is for you to send patches for the Kconfig
help messages. *After* you have researched what the options do.
//Peter
pgptDFHdnLwQL.pgp
Description:
Date: Tue, 19 Mar 2013 10:36:15 +0100
Without the boot interface , GRUB 2 (package grub-pc 1.99-7 from Debian
Sid/unstable) is not loaded when running coreboot with SeaBIOS 1.7.2.1
as payload on the ASRock E350M1. Only the SeaBIOS banner is shown and
nothing else happens afterward.
If SeaBIOS is useless without this, then maybe the option to disable it
should be removed?
On Tue, Mar 19, 2013 at 11:00 AM, Paul Menzel
paulepan...@users.sourceforge.net wrote:
Date: Tue, 19 Mar 2013 10:36:15 +0100
Without the boot interface , GRUB 2 (package grub-pc 1.99-7 from Debian
Paul Menzel wrote:
I still do not understand how SeaBIOS uses the interfaces itself
and how SeaBIOS is of any use at all without being able to boot
something. At least I do not know of such a use case.
Payloads can also not be started without that option?
//Peter
pgpOPwSGiBmrd.pgp
On Tue, Mar 19, 2013 at 11:00:30AM +0100, Paul Menzel wrote:
Date: Tue, 19 Mar 2013 10:36:15 +0100
Without the boot interface , GRUB 2 (package grub-pc 1.99-7 from Debian
Sid/unstable) is not loaded when running coreboot with SeaBIOS 1.7.2.1
as payload on the ASRock E350M1. Only the SeaBIOS
Kevin O'Connor wrote:
Basically everything under the BIOS interfaces menu is low-level
and should not be changed without understanding the implications.
Maybe hide those behind a CONFIG_EXPERT option?
//Peter
___
SeaBIOS mailing list
Am Dienstag, den 19.03.2013, 19:05 -0400 schrieb Kevin O'Connor:
On Tue, Mar 19, 2013 at 11:00:30AM +0100, Paul Menzel wrote:
Date: Tue, 19 Mar 2013 10:36:15 +0100
Without the boot interface , GRUB 2 (package grub-pc 1.99-7 from Debian
Sid/unstable) is not loaded when running coreboot
Am Dienstag, den 19.03.2013, 17:18 +0100 schrieb Peter Stuge:
Paul Menzel wrote:
I still do not understand how SeaBIOS uses the interfaces itself
and how SeaBIOS is of any use at all without being able to boot
something. At least I do not know of such a use case.
Payloads can also not be
Paul Menzel wrote:
Again as in the other thread this probably stems from the fact that I
have the (wrong(?)) assumption that BIOS interfaces are not needed for
GRUB or Linux.
GRUB needs BIOS interfaces. GRUB 2 as payload might not, but GRUB 2
on a random debian system does. It's clear that
Am Mittwoch, den 20.03.2013, 01:03 +0100 schrieb Peter Stuge:
Paul Menzel wrote:
Again as in the other thread this probably stems from the fact that I
have the (wrong(?)) assumption that BIOS interfaces are not needed for
GRUB or Linux.
GRUB needs BIOS interfaces. GRUB 2 as payload might
Paul Menzel wrote:
I do not even know what the BIOS boot interface does and how it is
utilized. I guess I should read up about that.
Hundreds if not thousands of interrupt services and about a dozen
data structures.
//Peter
pgpIFHbM5p9U6.pgp
Description: PGP signature
On Wed, Mar 20, 2013 at 12:20:51AM +0100, Peter Stuge wrote:
Kevin O'Connor wrote:
Basically everything under the BIOS interfaces menu is low-level
and should not be changed without understanding the implications.
Maybe hide those behind a CONFIG_EXPERT option?
It's possible, but
On Wed, Mar 20, 2013 at 12:59:53AM +0100, Paul Menzel wrote:
Am Dienstag, den 19.03.2013, 19:05 -0400 schrieb Kevin O'Connor:
Basically everything under the BIOS interfaces menu is low-level and
should not be changed without understanding the implications. (If one
disables the boot
14 matches
Mail list logo
