Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 14 Jan 2002 09:27:05 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 14 Jan 2002 09:26:49 -0500 Received: from albatross-ext.wise.edt.ericsson.se ([194.237.142.116]:39300 "EHLO albatross-ext.wise.edt.ericsson.se") by vger.kernel.org with ESMTP id ; Mon, 14 Jan 2002 09:26:09 -0500 Message-ID: From: "Michael Lazarou (ETL)" To: "'Giacomo Catenazzi'" Cc: "'esr@thyrsus.com'" , Linux Kernel List Subject: RE: ISA hardware discovery -- the elegant solution Date: Mon, 14 Jan 2002 15:25:50 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > -----Original Message----- > From: Giacomo Catenazzi [mailto:cate@debian.org] > >> > >>The kernel's device drivers have, of course, to include probe > >>routines, and those hard-compiled in typically log the presence of > >>their hardware to /var/log/mesg when it loads. By scanning that > >>file, we in effect get to use those probes. > >> > > > > Doesn't this mean that you would need a fully functional kernel > > before you get to run the autoconfigurator? > > > 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. Without probing the hardware how will the autoconfigurator cope with the hardware changing underneath it? Michael - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/