All of lore.kernel.org
 help / color / mirror / Atom feed
* [parisc-linux] Fwd: A call for boot loader IDs
@ 2003-12-05 20:40 Helge Deller
  2003-12-05 20:43 ` Christoph Hellwig
  0 siblings, 1 reply; 4+ messages in thread
From: Helge Deller @ 2003-12-05 20:40 UTC (permalink / raw)
  To: parisc-linux

Is this something we should care about for PALO ?

Helge

----------  Forwarded Message  ----------

Subject: A call for boot loader IDs
Date: Friday 05 December 2003 17:38
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org

Hi all,

So far only a small number of boot loaders have actually officially
registered their IDs, this is the list that I have:

  type_of_loader: 
        If your boot loader has an assigned id (see table below),
        enter 0xTV here, where T is an identifier for the boot loader
        and V is a version number.  Otherwise, enter 0xFF here.

        Assigned boot loader ids:
        0  LILO
        1  Loadlin
        2  bootsect-loader
        3  SYSLINUX
        4  EtherBoot
        5  ELILO

        Please contact <hpa@zytor.com> if you need a bootloader ID
        value assigned.

I would really appreciate if other boot loaders -- especially GRUB,
which is widely used -- would let me know (a) what they are currently
doing, and (b) whether or not they need an official allocation.  It's
probably unwise to not do so, at least for the ones which have a
significant user community.

The purpose of this ID is so we can work around individual boot loader
issues if we should have a need to adjust or change the boot
protocol.  Not reporting a unique ID makes this impossible.

	 -hpa

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [parisc-linux] Fwd: A call for boot loader IDs
  2003-12-05 20:40 [parisc-linux] Fwd: A call for boot loader IDs Helge Deller
@ 2003-12-05 20:43 ` Christoph Hellwig
  2003-12-05 20:46   ` Helge Deller
  0 siblings, 1 reply; 4+ messages in thread
From: Christoph Hellwig @ 2003-12-05 20:43 UTC (permalink / raw)
  To: Helge Deller; +Cc: parisc-linux

On Fri, Dec 05, 2003 at 09:40:19PM +0100, Helge Deller wrote:
> Is this something we should care about for PALO ?

This sounds _very_ x86-centric :)

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [parisc-linux] Fwd: A call for boot loader IDs
  2003-12-05 20:43 ` Christoph Hellwig
@ 2003-12-05 20:46   ` Helge Deller
  2003-12-05 20:47     ` Christoph Hellwig
  0 siblings, 1 reply; 4+ messages in thread
From: Helge Deller @ 2003-12-05 20:46 UTC (permalink / raw)
  To: parisc-linux

On Friday 05 December 2003 21:43, Christoph Hellwig wrote:
> On Fri, Dec 05, 2003 at 09:40:19PM +0100, Helge Deller wrote:
> > Is this something we should care about for PALO ?
> 
> This sounds _very_ x86-centric :)

Sure, but at least ELILO is iA64.

Helge

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [parisc-linux] Fwd: A call for boot loader IDs
  2003-12-05 20:46   ` Helge Deller
@ 2003-12-05 20:47     ` Christoph Hellwig
  0 siblings, 0 replies; 4+ messages in thread
From: Christoph Hellwig @ 2003-12-05 20:47 UTC (permalink / raw)
  To: Helge Deller; +Cc: parisc-linux

On Fri, Dec 05, 2003 at 09:46:14PM +0100, Helge Deller wrote:
> On Friday 05 December 2003 21:43, Christoph Hellwig wrote:
> > On Fri, Dec 05, 2003 at 09:40:19PM +0100, Helge Deller wrote:
> > > Is this something we should care about for PALO ?
> > 
> > This sounds _very_ x86-centric :)
> 
> Sure, but at least ELILO is iA64.

it's for any EFI platform.  and intel wants to push EFI for
x86 aswell.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2003-12-05 20:47 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-12-05 20:40 [parisc-linux] Fwd: A call for boot loader IDs Helge Deller
2003-12-05 20:43 ` Christoph Hellwig
2003-12-05 20:46   ` Helge Deller
2003-12-05 20:47     ` Christoph Hellwig

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.