From owner-freebsd-multimedia Sun Dec 29 04:50:36 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA29195 for multimedia-outgoing; Sun, 29 Dec 1996 04:50:36 -0800 (PST) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id EAA29190 for ; Sun, 29 Dec 1996 04:50:33 -0800 (PST) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id NAA25849; Sun, 29 Dec 1996 13:12:17 +0100 From: Luigi Rizzo Message-Id: <199612291212.NAA25849@labinfo.iet.unipi.it> Subject: Re: Sound Blaster PnP babble To: hasty@rah.star-gate.com (Amancio Hasty) Date: Sun, 29 Dec 1996 13:12:17 +0100 (MET) Cc: smpatel@umiacs.umd.edu, jkh@time.cdrom.com, multimedia@freebsd.org In-Reply-To: <199612290952.BAA05133@rah.star-gate.com> from "Amancio Hasty" at Dec 29, 96 01:52:34 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-multimedia@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >From The Desk Of Sujal Patel : > > On Sat, 28 Dec 1996, Jordan K. Hubbard wrote: > > > > > :-) > > > > > > BTW, any luck with Sound Blaster PnP lately? We've had a lot of people > > > asking about it.. > > > > The card should work just fine. There are several things to note though: > > > > 1 - If you have a PnP bios, you don't need to use my PnP driver. If you > > don't use the driver though, you need to "guess" where the BIOS configured > > your card :-) There is sample code to read the PnP BIOS's configuration > > in ~smpatel/public_html/pnpget* (I haven't had time to clean this up yet). > > I thought that the PnP bios does not activate ISA PnP cards. It does > assigned them a CSN and appropiate resources however the devices will > remain inactive till the OS or program activates them. At any rate, I am not sure about the details. For instance my board is recognised at bootup, but as you try to use /dev/audio the process blocks -- probably because of incorrect DMA/IRQ configuration. The parameters in the kernel match those shown by "pnpinfo" though. > there are enough bogus PnP bioses floating around that the safest > bet is to depend on the driver for proper PnP initialization and > activation. In fact one of the buggy PnP Bios force me to write > the PnP code in the GUS PnP driver. And some boards report strange info as well. Mine gives the following output from "pnpinfo" (slightly reformatted): I/O Range 0x534 .. 0x534, alignment 0x4, len 0x4 [not 16-bit addr] where the "[not 16-bit addr]" means, according to the PnP specs, that only A9..A0 are decoded (and these cannot possibly represent 0x534!) Luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________