From alsa-devel-owner@alsa.jcu.cz  Tue Feb 16 12:04:50 1999
Received: from ife.ee.ethz.ch (ife-fast.ee.ethz.ch [129.132.24.193])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id MAA27860
	for <alsa-devel@alsa.jcu.cz>; Tue, 16 Feb 1999 12:04:05 +0100
Received: from ife.ee.ethz.ch (eldrich.ee.ethz.ch [129.132.24.203])
	by ife.ee.ethz.ch (8.8.5/8.8.5) with ESMTP id MAA06495
	for <alsa-devel@alsa.jcu.cz>; Tue, 16 Feb 1999 12:04:04 +0100 (MET)
Message-ID: <36C950A4.7DAC0710@ife.ee.ethz.ch>
Date: Tue, 16 Feb 1999 12:04:04 +0100
From: Thomas Sailer <sailer@ife.ee.ethz.ch>
MIME-Version: 1.0
To: alsa-devel@alsa.jcu.cz
Subject: Re: ISApnp
References: <Pine.LNX.3.96.990215210639.8823E-100000@entry.jcu.cz>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

Jaroslav Kysela wrote:

> 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.

Not really anymore, since in Linux 2.2.1 the recommended interface
(/proc/bus/pci/*) no longer exports symbolic info, only the raw numbers.
The PCI ID database now lives in userspace, and only the drivers
themselves need to know what PCI ID they're looking for.

Tom

