From owner-freebsd-stable Fri Jun 5 19:27:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05947 for freebsd-stable-outgoing; Fri, 5 Jun 1998 19:27:38 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05936 for ; Fri, 5 Jun 1998 19:27:27 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id SAA02536; Fri, 5 Jun 1998 18:21:22 -0700 (PDT) Message-Id: <199806060121.SAA02536@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Ugo Paternostro cc: Mike Smith , eivind@yes.no (Eivind Eklund), freebsd-stable@FreeBSD.ORG, Luigi Rizzo Subject: Re: PnP support for if_ed, and more... In-reply-to: Your message of "Fri, 05 Jun 1998 13:20:24 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Jun 1998 18:21:22 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Linking this into the kernel would be bad; it ought to be read from a > > file. I think I am close to having BIOS disk access working at least > > /kernel.config ? There is (currently) a 512-byte limit on kernel.config. I'm still evaluating the relative merits of the NetBSD bootinfo method vs. my "Extras" mechanism for bringing extra data in with the kernel load; either way, this is how this table will be read I feel (it would make it practical to fetch it via any method used to load the kernel, not just via BIOS disk). > P.S.: still offering a bit of manpower to do the work... :-) Well, let's say it > all: point me in the right direction, and I will evaluate the possibility :-) > WARNING: I know almost nothing about FreeBSD insides =:-/ but I learn fast, and > I think that I am a good programmer... ;-) Get the table from http://www.microsoft.com/hwdev/download/respec/devids.txt and then work out a mechanism to scan the 'compatible device ID' descriptors (0x1c) and pretend that the device is one of these if the first pass (try for an exact match on the device ID) fails. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message