All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Erik A. Hendriks" <hendriks@lanl.gov>,
	Andrew Morton <akpm@zip.com.au>,
	linux-kernel@vger.kernel.org,
	Werner Almesberger <wa@almesberger.net>
Subject: Re: [RFC] x86 ELF bootable kernels/Linux booting Linux/LinuxBIOS
Date: Sun, 03 Feb 2002 11:48:29 -0800	[thread overview]
Message-ID: <3C5D940D.4000406@zytor.com> (raw)
In-Reply-To: <m1elk7d37d.fsf@frodo.biederman.org>	<3C586355.A396525B@zip.com.au> <m1zo2vb5rt.fsf@frodo.biederman.org>	<3C58B078.3070803@zytor.com> <m1vgdjb0x0.fsf@frodo.biederman.org>	<3C58CAE0.4040102@zytor.com> <20020131103516.I26855@lanl.gov>	<m1elk6t7no.fsf@frodo.biederman.org> <3C59DB56.2070004@zytor.com>	<m1r8o5a80f.fsf@frodo.biederman.org> <3C5A5F25.3090101@zytor.com>	<m1hep19pje.fsf@frodo.biederman.org> <3C5ADDD1.6000608@zytor.com>	<m1665fame3.fsf@frodo.biederman.org> <3C5C54D2.2030700@zytor.com>	<m1k7tv8p2z.fsf@frodo.biederman.org> <3C5C98E6.2090701@zytor.com> <m1y9ia76f7.fsf@frodo.biederman.org>

Eric W. Biederman wrote:

> 
> O.k. I have been thinking about this some more, and I have come up with a couple
> alternate of solutions.
> 
> The simplest is the observation that right now 10MB is about what it
> takes to hold every Linux driver out there.  So all you really need is
> a 16MB system, to avoid a device probing loader.  And probably
> noticeably less than that.  The only systems I see having real
> problems are old systems where device enumeration is not reliable, and
> require human intervention anyway.
> 
> A second is to just make certain there is some kind of fallback path
> so if the image is too large have a way to load a smaller one.  When
> you consider that older systems had less memory it has a reasonable
> chance of working properly.
> 
> My final and favorite is to take an ELF image, define a couple of ELF
> note types, and add a bunch those notes saying which pieces are
> hardware dependent.  So a smart ELF loader can prune the image as it
> is loaded, and a stupid one will just attempt to load everything.  And
> with the setup for this not being bootloader specific it will probably
> encourage device pruning loaders.
> 
> Am I being optimistic or are there any pressing cases for callbacks to
> the firmware?
> 


Ok, now let me ask the question that hopefully should be obvious to 
everyone now...

WHAT'S THE POINT?

All you're doing is an awfully complex song and dance to *avoid* 
implementing a solution that, while imperfect, is thoroughly established 
and has worked for 20 years.

	-hpa



  parent reply	other threads:[~2002-02-03 19:49 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-30 19:54 [RFC] x86 ELF bootable kernels/Linux booting Linux/LinuxBIOS Eric W. Biederman
2002-01-30 21:19 ` Andrew Morton
2002-01-30 23:52   ` Keith Owens
2002-01-31  2:42   ` Eric W. Biederman
2002-01-31  2:48     ` H. Peter Anvin
2002-01-31  4:27       ` Eric W. Biederman
2002-01-31  4:41         ` H. Peter Anvin
2002-01-31  5:15           ` Eric W. Biederman
2002-01-31  5:59             ` H. Peter Anvin
     [not found]               ` <m1n0yvaucy.fsf@frodo.biederman.org>
2002-01-31 17:57                 ` H. Peter Anvin
2002-01-31 22:34                   ` Eric W. Biederman
2002-01-31 22:52                     ` H. Peter Anvin
2002-02-01  7:52                       ` Eric W. Biederman
2002-01-31 17:35           ` Erik A. Hendriks
2002-01-31 23:36             ` Eric W. Biederman
2002-02-01  0:03               ` H. Peter Anvin
2002-02-01  9:03                 ` Eric W. Biederman
2002-02-01  9:25                   ` H. Peter Anvin
2002-02-01 15:42                     ` Eric W. Biederman
2002-02-01 18:26                       ` H. Peter Anvin
2002-02-02 16:17                         ` Eric W. Biederman
2002-02-02 21:06                           ` H. Peter Anvin
2002-02-02 23:02                             ` Eric W. Biederman
2002-02-03  1:56                               ` H. Peter Anvin
2002-02-03 18:43                                 ` Eric W. Biederman
2002-02-03 19:39                                   ` H. Peter Anvin
2002-02-03 22:18                                     ` Rob Landley
2002-02-03 22:24                                       ` H. Peter Anvin
2002-02-03 22:59                                         ` Rob Landley
2002-02-03 23:01                                           ` H. Peter Anvin
2002-02-03 23:47                                             ` Rob Landley
2002-02-04  1:34                                               ` H. Peter Anvin
2002-02-04  9:53                                             ` Marco Colombo
2002-02-04 16:19                                               ` H. Peter Anvin
2002-02-04 19:55                                     ` Eric W. Biederman
2002-02-04 20:51                                       ` Alan Cox
2002-02-04 20:40                                         ` H. Peter Anvin
2002-02-03 19:48                                   ` H. Peter Anvin [this message]
2002-02-04 20:16                                     ` Eric W. Biederman
2002-02-04  4:29                                   ` Keith Owens
2002-02-04 20:01                                     ` Eric W. Biederman
2002-02-04 12:49                         ` Werner Almesberger
2002-02-04 16:26                           ` H. Peter Anvin
2002-02-04 19:45                           ` Eric W. Biederman
2002-02-04 21:02                             ` Werner Almesberger
2002-02-04 21:08                               ` H. Peter Anvin
2002-02-05  7:45                                 ` Eric W. Biederman
2002-02-01  0:46               ` Keith Owens
2002-01-31  3:03     ` Keith Owens
2002-02-01  7:22       ` Greg KH
2002-01-30 21:32 ` H. Peter Anvin
2002-01-31  2:31   ` Eric W. Biederman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C5D940D.4000406@zytor.com \
    --to=hpa@zytor.com \
    --cc=akpm@zip.com.au \
    --cc=ebiederm@xmission.com \
    --cc=hendriks@lanl.gov \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wa@almesberger.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.