All of lore.kernel.org
 help / color / mirror / Atom feed
From: Giacomo Catenazzi <cate@dplanet.ch>
To: "Michael Lazarou (ETL)" <Michael.Lazarou@etl.ericsson.se>
Cc: "'Giacomo Catenazzi'" <cate@debian.org>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: ISA hardware discovery -- the elegant solution
Date: Mon, 14 Jan 2002 15:47:29 +0100	[thread overview]
Message-ID: <3C42EF81.5060607@dplanet.ch> (raw)
In-Reply-To: <F50839283B51D211BC300008C7A4D63F0C1075A2@eukgunt002.uk.eu.ericsson.se>



Michael Lazarou (ETL) wrote:


>>Not a problem. Autoconfiguration is made to help configuring
>>the kernel, before to compile it. So you need a linux working
>>machine (actually you can cross-compile).
>>
>>Our task is to allow user to compile a kernel, with the
>>needed drivers, without the non used drivers.
>>
> 
> OK, well I guess I am a little confused.
> 
> If I hit an autoconfigurator button then I would expect a kernel that
> will boot and know everything there is to know about my machine.


Actually there is no yet 'autoconfigurator button'.
I recommend to run a std configuration tool and to check
the configuration before the kernel build phase.

> Without probing the hardware how will the autoconfigurator cope with 
> the hardware changing underneath it?


We probe the hardware (but in a soft manner).
Better: we probe nothing, we ask kernel to give us the results
of already done kernel probes. Thus we never hang, we never crash
machine, no 10-15 reboots to install a new kernel.
The good news: this is nearly enought.

Linux is magic: it can do infinite loops in 5 sec, but also
it can configure automatically a new kernel without real hardware
probes!.

	giacomo


  reply	other threads:[~2002-01-14 14:49 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-14 14:25 ISA hardware discovery -- the elegant solution Michael Lazarou (ETL)
2002-01-14 14:47 ` Giacomo Catenazzi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-14 18:36 Stephen Shirley
     [not found] <fa.r42lgsv.1b5e3p9@ifi.uio.no>
2002-01-14 12:30 ` Giacomo Catenazzi
2002-01-14 11:17 Michael Lazarou (ETL)
2002-01-14 16:11 ` Eric S. Raymond
2002-01-14 16:59   ` Eli Carter
2002-01-14 17:11     ` Wichert Akkerman
2002-01-14 18:33   ` Oliver Xymoron
2002-01-14 23:02     ` Tom Gilbert
2002-01-14 18:58   ` Andrew Pimlott
     [not found] <fa.dardpev.1m1emjp@ifi.uio.no>
2002-01-14 10:14 ` Giacomo Catenazzi
2002-01-14 16:16   ` Eric S. Raymond
2002-01-14 16:38     ` Giacomo Catenazzi
2002-01-14 16:34       ` Eric S. Raymond
2002-01-14 17:48     ` Alan Cox
2002-01-14 17:55       ` Mr. James W. Laferriere
2002-01-14 18:08         ` Alan Cox
2002-01-14 17:59       ` Eric S. Raymond
2002-01-14 18:35         ` Alan Cox
2002-01-14  8:03 Zwane Mwaikambo
2002-01-14  9:44 ` Alan Cox
2002-01-14 14:00   ` Zwane Mwaikambo
2002-01-14  1:58 Eric S. Raymond
2002-01-14  2:54 ` Larry McVoy
2002-01-14  8:46 ` Eric W. Biederman
2002-01-14  8:48   ` Eric S. Raymond
2002-01-14  9:17     ` H. Peter Anvin
2002-01-14 17:34     ` 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=3C42EF81.5060607@dplanet.ch \
    --to=cate@dplanet.ch \
    --cc=Michael.Lazarou@etl.ericsson.se \
    --cc=cate@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.