From alsa-devel-owner@alsa.jcu.cz  Sun Nov 29 14:34:34 1998
Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.6.51])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id OAA23729;
	Sun, 29 Nov 1998 14:27:59 +0100
Received: from cs.vu.nl (orbital.xs4all.nl [194.109.37.98])
	by smtp1.xs4all.nl (8.8.8/8.8.8) with ESMTP id OAA16344;
	Sun, 29 Nov 1998 14:27:57 +0100 (CET)
Message-ID: <36614D53.4E076BDC@cs.vu.nl>
Date: Sun, 29 Nov 1998 13:34:11 +0000
From: Andy Lo A Foe <arloafoe@cs.vu.nl>
MIME-Version: 1.0
To: Jaroslav Kysela <perex@jcu.cz>, alsa-devel@jcu.cz
Subject: Re: MINOR numbers - READ PLEASE!!!
References: <Pine.LNX.3.96.981129113552.3605B-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:

> I don't know how exactly devfs works, but I'm thinking that devfs is
> generating virtual devices (like files in proc filesystem)? Thus we still
> need allocate minor numbers.

I don't think so, since lookup of devices is not done by major/minor number but
by searching
in the devfs tables. The current /proc/asound/dev entries are dynamically
created character special files which are linked to /dev entries. You still have
the 8-bit minor device limit.

http://www.atnf.csiro.au/~rgooch/linux/docs/devfs.txt

The devfs FAQ

> > should use asoundlib for interfacing with ALSA anyway. So it doesn't really
> > matter what we choose now, right?
>
> Static linked applications willn't work...

But it is reasonable to break compatibility when moving to say 1.0 right? Only
when commerical (closed source) vendors start to use ALSA (and for some reason
want to link statically) does backward compatibility  become an issue (IMHO)...

Andy

--
Andy Lo A Foe, arloafoe@cs.vu.nl |  Linux v2.1.128  | PII 266
http://www.cs.vu.nl/~arloafoe    | GSM: 0622-440695 | Bebox 133
http://orbital.xs4all.nl/andy    |   ICQ: 7472949   | IRCNet: Adnans




