From owner-freebsd-current Sat Sep 4 7:48: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 678F715C90 for ; Sat, 4 Sep 1999 07:47:56 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id PAA43542; Sat, 4 Sep 1999 15:47:56 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 4 Sep 1999 15:47:56 +0100 (BST) From: Doug Rabson To: Steve Price Cc: freebsd-current@freebsd.org Subject: Re: PNP ids missing in sio.c In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 4 Sep 1999, Steve Price wrote: > On Sat, 4 Sep 1999, Doug Rabson wrote: > > # The reason I didn't move the old ids wholesale is that the old system > # matched against the vendor id (which is bogus for multifunction cards). > # The new system matches with the logical device id which is often different > # from the vendor id. Some simple single function cards use the same id for > # both (as yours does) but I can't tell this without seeing the pnpinfo > # output. > > For others who are interested here's the old list. I can vouche > for the USR3031. If anyone else has one of the others or a PNP > modem/sio card not listed here, can you send me the output of > pnpinfo? I'll compile the list for my commit and forward it to > you Doug if you'd like. That would be very useful, thanks. I have committed your patch but possibly this alternative would work better (with the latest version of isa_common.c which I just committed) since it will preserve the card's description instead of replacing it with the fairly meaningless "USR3031". Index: sio.c =================================================================== RCS file: /home/ncvs/src/sys/isa/sio.c,v retrieving revision 1.261 diff -u -r1.261 sio.c --- sio.c 1999/09/04 14:31:56 1.261 +++ sio.c 1999/09/04 14:42:24 @@ -573,7 +573,7 @@ {0x0205d041, "Multiport serial device (non-intelligent 16550)"}, /* PNP0502 */ {0x1005d041, "Generic IRDA-compatible device"}, /* PNP0510 */ {0x1105d041, "Generic IRDA-compatible device"}, /* PNP0511 */ - {0x31307256, "USR3031"}, /* USR3031 */ + {0x31307256, NULL}, /* USR3031 */ {0} }; > # The pnp command should no longer be needed (crossed fingers) since the new > # code automatically detects devices and assigns resources to them. > > So what happens if someone wants to "wire" down a device? It > was no big deal for me that it used to be sio1 and is now sio4, > but one should be able to imagine a scenario (just like with > SCSI disks?) that you'd need to be explicit about what resources > and device number the card gets. Of course I could be dead wrong > too. :-) I don't think there is much use for wiring down the resources (wiring the unit number I can see uses for). For the case where the pnp code must avoid certain resources (e.g. for hardware which is present but with no drivers), I expect I will add a list of resource ranges to avoid when allocating pnp resources. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message