public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Crilly <jim@why.dont.jablowme.net>
To: Mike Bell <kernel@mikebell.org>,
	Arjan van de Ven <arjan@infradead.org>, Greg KH <greg@kroah.com>,
	Dmitry Torokhov <dtor_core@ameritech.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] ndevfs - a "nano" devfs
Date: Tue, 28 Jun 2005 19:43:10 -0400	[thread overview]
Message-ID: <20050628234310.GA29653@mail> (raw)
In-Reply-To: <20050628222318.GC4673@mikebell.org>

On 06/28/05 03:23:18PM -0700, Mike Bell wrote:
> On Tue, Jun 28, 2005 at 05:49:29PM -0400, Jim Crilly wrote:
> > I took a quick look and for OSS devices linphone seems to just loop over
> > /dev/dsp* so if the names were moved, I doubt it would work. 
> > 
> > But it also seems to have ALSA support and in that case it uses 
> > snd_card_get_name in a for loop to build a list of available cards, since 
> > all ALSA functions use card index numbers they should work fine independent 
> > of device file names.
> 
> No, they shouldn't. Try it and see. Yes, your /program/ uses the sound
> card index, but that's because the ALSA library internally assumes that
> sound card index 0 corresponds to certain device nodes.

I stand corrected then. I didn't actually try anything with linphone, the
ALSA API just makes it look like the device nodes don't matter.

> 
> Eventually every program has to be able to find the device node. That's
> just obvious, if you don't need the device node why have it in the first
> place? And if it can't predict what that device node will be named, the
> only thing it can do (short of creating its own private device node,
> which breaks all sorts of stuff /and/ is dumb /and/ doesn't work unless
> you're root) is search over every single device node in /dev to find the
> one with the correct major/minor. Or ask the user to type it in
> manually, which is all well and good for maybe an admin configuring some
> system, but is completely broken for anything GUI or automatic.
> 
> Hence my conclusion, predictable device file names are a requirement.
> udev's "name the device whatever you want" works fine for running vi on
> /etc/fstab, but when you want a program to do anything intelligent like
> present a list of available choices, you need to be able to find the
> device node.

Well it looks like the ALSA library already abstracts the device node
enough that the app itself doesn't know what file is being used because it
just calls snd_card_get_name, snd_open_pcm, etc with the ALSA index. So
wouldn't it be feasible to make ALSA a little bit smarter so that it could
track/find the device nodes no matter what name they have? I'm not
advocating for or against it, but from my cursory look at the API it looks
possible to do without breaking any ALSA apps.

Jim.

  reply	other threads:[~2005-06-29  0:03 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-24  8:18 [ANNOUNCE] ndevfs - a "nano" devfs Greg KH
2005-06-24 12:23 ` Michael Tokarev
2005-06-24 15:16   ` Greg KH
2005-06-24 15:40     ` Michael Tokarev
2005-06-24 16:26       ` Greg KH
2005-06-24 14:32 ` Bill Gatliff
2005-06-24 15:17 ` Steven Rostedt
2005-06-24 15:20   ` Greg KH
2005-06-24 17:10 ` Michael Tokarev
2005-06-24 17:10 ` Bill Gatliff
2005-06-28  7:40   ` Greg KH
2005-06-24 19:05 ` Mike Bell
2005-06-24 21:55   ` J.A. Magallon
2005-06-24 19:22 ` Alexey Dobriyan
2005-06-25  0:57 ` Kyle Moffett
2005-06-25  7:37   ` Denis Vlasenko
2005-06-28  7:41   ` Greg KH
2005-06-28 19:56     ` Tom Rini
2005-06-28 21:08       ` Olaf Hering
2005-06-28 21:25         ` Tom Rini
2005-06-28 22:08           ` Michael Tokarev
2005-06-28 22:23             ` Tom Rini
2005-06-25 22:15 ` Matt Mackall
2005-06-25 23:43   ` Greg KH
2005-06-26  8:23     ` Russell King
2005-06-28  3:36       ` Greg KH
2005-06-27  7:19     ` Mike Bell
2005-06-27 22:35       ` Dmitry Torokhov
2005-06-27 23:26         ` Mike Bell
2005-06-28  7:40           ` Greg KH
2005-06-28  9:08             ` Mike Bell
2005-06-28  9:21               ` Arjan van de Ven
2005-06-28  9:40                 ` Mike Bell
2005-06-28 21:49                 ` Jim Crilly
2005-06-28 22:23                   ` Mike Bell
2005-06-28 23:43                     ` Jim Crilly [this message]
2005-06-29  0:12                       ` Mike Bell
2005-06-29  0:39                         ` David Lang
2005-06-29  0:53                           ` Mike Bell
2005-06-28 12:00             ` Oliver Neukum
2005-06-28 20:08               ` Greg KH
2005-06-29  6:41                 ` Oliver Neukum
2005-06-29 16:06                   ` Greg KH
2005-06-29 16:22                     ` Oliver Neukum
     [not found] ` <200506270819.20108.arnd@arndb.de>
2005-06-28  3:46   ` Greg KH
     [not found] <OF831AC472.851744FE-ON8025702A.004A57EC-8025702A.004B5AE9@sophos.com>
2005-06-24 15:23 ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2005-06-24 15:32 tvrtko.ursulin
2005-06-24 16:27 ` Greg KH
2005-06-27 15:21 Adam J. Richter
2005-06-27 23:27 ` J.A. Magallon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050628234310.GA29653@mail \
    --to=jim@why.dont.jablowme.net \
    --cc=arjan@infradead.org \
    --cc=dtor_core@ameritech.net \
    --cc=greg@kroah.com \
    --cc=kernel@mikebell.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox