From ultra-devel-owner@ultra.jcu.cz  Sun Mar  1 23:11:55 1998
Received: from ctc.swva.net (root@ctc.swva.net [165.166.123.19])
	by marvin.jcu.cz (8.8.8/8.8.8) with ESMTP id XAA13510
	for <ultra-devel@jcu.cz>; Sun, 1 Mar 1998 23:11:47 +0100
Received: from robin (CVA09-09.swva.net [206.99.244.181])
	by ctc.swva.net (8.8.5/8.8.5) with SMTP id RAA17337
	for <ultra-devel@jcu.cz>; Sun, 1 Mar 1998 17:12:42 -0500
Message-Id: <3.0.3.32.19980301171220.006bcbb8@mail.vt.edu>
Date: Sun, 01 Mar 1998 17:12:20 -0500
To: ultra-devel@jcu.cz
From: Alan Robinson <ar@vt.edu>
Subject: linux/sounddetect.h
In-Reply-To: <Pine.LNX.3.96.980301205957.17418D-100000@entry.jcu.cz>
References: <Pine.LNX.3.96.980228141559.1055A-101000@orbital>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Reply-To: ultra-devel@ultra.jcu.cz
Sender: ultra-devel-owner@ultra.jcu.cz
Precedence: list

I don't know what the expected use of the sound card ID numbers are, but if
the end user ever needs to get access to them, then some sort of hierarchy
might be nice... Say the ID is a 32 bit number:

First Byte:  Type of sound card, ie, chipset.  For instance, GF1.
Second Byte: Specific sound card. For instance, GUS-MAX.
Third Byte: Revision number. For instance, 1.7.

I am not sure if the revision number would really be useful, but I think
the other two pieces of information would be useful. If application ever
wants to know what sort of sound card it is working with (say, it wants to
eliminate ultraclicks, if running on a GF1), then being able to check the
chipset with a single compare would be really nice.  

With the current number scheme, the program would have to check the sound
card type, seeing if it equals SND_CARD_TYPE_GUS_ACE, SND_CARD_TYPE_ACE,
etc. And if a new sound card came out with a GF1 chipset, then new code
would have to be added to check for it.

Just a thought.



