From alsa-devel-owner@alsa.jcu.cz  Sun Feb 21 01:08:15 1999
Received: from medelec.uia.ac.be (fnet@medelec.uia.ac.be [143.169.17.1])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id BAA24721
	for <alsa-devel@alsa.jcu.cz>; Sun, 21 Feb 1999 01:08:09 +0100
Received: (from fnet@localhost)
	by medelec.uia.ac.be (8.8.8/8.8.8) id BAA11837
	for alsa-devel@alsa.jcu.cz; Sun, 21 Feb 1999 01:08:09 +0100
To: alsa-devel@alsa.jcu.cz
From: "O/T-Track+ 2.66b" <"O/T-Track+=202.66b"@f854.n292.z2.fidonet.org>
Date: Sat, 20 Feb 99 22:32:43 +0100
Subject: Message *bounced*
Message-ID: <3655839448@f854.n292.z2.ftn>
In-Reply-To: <2826770656@entry.jcu.cz>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

************************************************************************
***  WARNING -- WARNING -- WARNING -- WARNING -- WARNING -- WARNING  ***
************************************************************************
*
*      The e-mail-message appended below is list- or mailserver-related
*
*   That type of mail will by definition not be processed on this system.
*
*    If you have reason to believe your message was removed without due
*     reason then kindly inform 'postmaster@f854.n292.z2.fidonet.org'.
*
************************************************************************

    From:  Jaroslav Kysela @2:292/875
    To:    Michael Putijewsky @2:244/3311.2
    Subj.: Re: ISApnp
    Dated: 15 Feb 99  21:21:47
    [processed here:  20 Feb 99 22:32:43]

@TOPT 2
@INTL 2:244/3311 2:292/875
@MSGID: entry.jcu.cz a87d18e0
@REPLY: screech.cs.alfred.edu 2888a5c4
@REPLYADDR: alsa-devel@alsa.jcu.cz
@REPLYTO: 2:292/875@fidonet UUCP
@CHRS: LATIN-1 2
@RFC-Received: (from fnet@localhost) by infomag.infomag.iguana.be
(8.6.12/8.6.10) id VAA04682 for
Michael.Putijewsky@p2.f3311.n244.z2.fidonet.org;
Thu, 18 Feb 1999 21:12:48 +0100
@RFC-Received: from cimmeria.iguana.be (qmailr@cimmeria.iguana.be [194.7.8.7])
	by medelec.uia.ac.be (8.8.8/8.8.8) with SMTP id SAA29928 	for
<Michael_Putijewsky@p2.f3311.n244.z2.fidonet.org>; Wed, 17 Feb 1999 18:37:35
+0100
@RFC-Received: (qmail 24515 invoked from network); 17 Feb 1999 17:37:32 -0000
@RFC-Received: from mx6.gmx.net (195.63.104.86)   by cimmeria.iguana.be with
SMTP; 17 Feb 1999 17:37:32 -0000
@RFC-Received: (qmail 5899 invoked by alias); 15 Feb 1999 21:10:51 -0000
@RFC-Received: (qmail 5886 invoked by uid 0); 15 Feb 1999 21:10:51 -0000
@RFC-Received: from marvin.jcu.cz (160.217.1.3)   by mx6.gmx.net with SMTP; 15
Feb 1999 21:10:51 -0000
@RFC-Received: (from petidomo@localhost) 	by marvin.jcu.cz (8.9.1a/8.9.1) id
VAA26739; 	Mon, 15 Feb 1999 21:22:02 +0100
@RFC-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
@RFC-Message-ID: <Pine.LNX.3.96.990215210639.8823E-100000@entry.jcu.cz>
@RFC-In-Reply-To:
<Pine.LNX.4.05.9902151441450.11988-100000@screech.cs.alfred.edu>
@RFC-Delivered-To: GMX delivery to t0mcat@gmx.de
@RFC-Sender: alsa-devel-owner@alsa.jcu.cz
@RFC-Precedence: list
@RFC-X-Resent-By: Global Message Exchange <forwarder@gmx.net>
@RFC-X-Resent-For: t0mcat@gmx.de
@RFC-X-Resent-To: tomcat@main-kinzig.de,
Michael_Putijewsky@p2.f3311.n244.z2.fidonet.org
To: "Christopher T. Lansdown" <lansdoct@screech.cs.alfred.edu>
From: Jaroslav Kysela <perex@jcu.cz>
Reply-To: alsa-devel@alsa.jcu.czcc: "Alsa Developer's List" <alsa-devel@jcu.cz>

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

------
To unsubscribe from <alsa-devel@alsa.jcu.cz> mailing list send message
'unsubscribe' in the body of message to <alsa-devel-request@alsa.jcu.cz>.

@Via ifmail 2:292/875@fidonet, Wed Feb 17 1999 at 18:37 (2.10-tx8.3)
@Via ifmail 2:292/862@fidonet, Thu Feb 18 1999 at 21:15 (2.10-tx8.3)

@Via D'Bridge 1.58 2:292/854  02/20 21:48


