From alsa-devel-owner@alsa.jcu.cz  Mon Feb 15 21:22:20 1999
Received: from entry.jcu.cz (IDENT:perex@entry.jcu.cz [160.217.1.111])
	by marvin.jcu.cz (8.9.1a/8.9.1) with SMTP id VAA26705;
	Mon, 15 Feb 1999 21:21:47 +0100
Date: Mon, 15 Feb 1999 21:21:47 +0100 (CET)
From: Jaroslav Kysela <perex@jcu.cz>
To: "Christopher T. Lansdown" <lansdoct@screech.cs.alfred.edu>
cc: "Alsa Developer's List" <alsa-devel@jcu.cz>
Subject: Re: ISApnp
In-Reply-To: <Pine.LNX.4.05.9902151441450.11988-100000@screech.cs.alfred.edu>
Message-ID: <Pine.LNX.3.96.990215210639.8823E-100000@entry.jcu.cz>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

On Mon, 15 Feb 1999, Christopher T. Lansdown wrote:

> Jaroslav,
> 	Is the isapnp module supposed to report what settings that it
> gives cards in dmesg?  It doesn't seem to in the output of one user who's
> having trouble.  Is that the way that isapnp.o is coded, or is that part
> of the trouble?  Btw, will trouble be encountered if a user uses isapnp,
> pnpdump, etc., that is, if a user uses the user-space utilities as well as
> isapnp.o?

The user which uses the isapnp module wouldn't use another utilities which
manage ISA PnP devices like isapnptools. It can (and will) cause the
driver malfunction.

The isapnp module (driver) provides all functions like isapnp/pnpdump
programs + more (it allows detection and special hardware configuration
for the front end hardware driver).

The most of troubles are caused that I and other driver programmers don't
know about all ISA PnP ID's which soundcard manufactures use for their
soundcards. Unfortunately most of people send us contents of /proc/isapnp
file (although this information is requested as critical in the INSTALL
file) in second or third e-mail.

It's same situation as for PCI bus. When new PCI card appears, the PCI
vendor and device ID must be added to linux/pci.h and to the lowlevel
driver (if any). Except that device IDs for ISA PnP devices aren't managed
in some common file.

							Jaroslav

-----
Jaroslav Kysela <perex@jcu.cz>
Academic Computer Centre, University of South Bohemia
Branisovska 31, C. Budejovice, CZ-370 05 Czech Republic


