From owner-freebsd-current Sat Sep 4 7:18:36 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 A5011152E7 for ; Sat, 4 Sep 1999 07:18:22 -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 PAA43185; Sat, 4 Sep 1999 15:20:00 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 4 Sep 1999 15:20:00 +0100 (BST) From: Doug Rabson To: "Zach N. Heilig" Cc: Steve Price , freebsd-current@freebsd.org Subject: Re: PNP ids missing in sio.c In-Reply-To: <19990904060615.A32986@murkwood.znh.org> 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, Zach N. Heilig wrote: > On Sat, Sep 04, 1999 at 10:21:51AM +0100, Doug Rabson wrote: > > The pnp command should no longer be needed (crossed fingers) since the new > > code automatically detects devices and assigns resources to them. > > What about the situation where: > > pnp sound card (soundblaster awe64). > non pnp network card (irq 5, port 0x300, setup ability unknown -- even > windows can't properly find it without help) > > Although I just replaced that network card last week (etherexpress > 100+), and replaced the soundblaster (with a pci es1370 based card) > this might be an issue for others. The BIOS put the sound card on irq > 9, ports 0x220, 0x330, 0x388, 0x620/0xa20/0xe20, and drqs 1,7 ... (this > was fine), but the new pnp code insisted on changing the sound card to > irq 5, same ports, and drqs 1,5 even though the bios had configured it > somewhere else. > > The network card used the 'ed' driver, so that device wasn't compiled in > the kernel right after the the switchover (but it still conflicted with > the sound card until I yanked it). > > This is of course a special case, a cranky network card and a > non-compiling driver for it. If the new pnp code avoids using resources > hard-wired to non-pnp isa devices (it may, I changed hardware before the > code was fixed), there shouldn't be any problems. It was an excellent > excuse to boot that nic anyway. The trick for this is to make sure that the config file contains accurate descriptions of all your non-pnp hardware. In this case, if you have: device ed0 at isa? port 0x300 irq 5 ... then the subsequent pnp probes should avoid those port and irq settings. -- 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