linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: walt <wa1ter@hotmail.com>
To: Torrey Hoffman <thoffman@arnor.net>
Cc: Giuliano Pochini <pochini@shiny.it>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ALSA busted in 2.5.69
Date: Fri, 09 May 2003 11:14:37 -0700	[thread overview]
Message-ID: <3EBBF00D.8040108@hotmail.com> (raw)
In-Reply-To: <fa.juutvqv.1inovpj@ifi.uio.no>

Torrey Hoffman wrote:
> On Fri, 2003-05-09 at 01:09, Giuliano Pochini wrote:
> 
>>On 08-May-2003 Torrey Hoffman wrote:
>>
>>>ALSA isn't working for me in 2.5.69.  It appears to be because
>>>/proc/asound/dev is missing the control devices.
> 
> ...
> 
>>If you are not using devfs, you need to create the devices. There is a
>>script in the ALSA-driver package to do that. Otherwise I can't help
>>you because I never tried devfs and linux 2.5.x.
> 
> 
> No.  /dev/snd is a symbolic link to /proc/asound/dev,
> and that symbolic link was created by the script you mention.
> (I am not using devfs.)
> 
> So the missing "/dev/snd/controlC0" should actually be created
> by the ALSA modules in the proc filesystem as
> "/proc/asound/dev/controlC0".  But only the timer device is there.

Warning:  I'm no expert on any of this -- but -- I'm listening to sound
right now using 2.5.69 (with devfs) and this is what I see:

There are NO symlinks from /dev to /proc.  None.

/dev/snd and /dev/sound are real directories -- neither is a symlink.

#ls -l /dev/snd
total 0
crw-------    1 wa1ter   audio    116,   0 Dec 31  1969 controlC0
crw-------    1 wa1ter   audio    116,  32 Dec 31  1969 controlC1
crw-------    1 wa1ter   audio    116,  64 Dec 31  1969 controlC2
crw-------    1 wa1ter   audio    116,  96 Dec 31  1969 controlC3
crw-------    1 wa1ter   audio    116, 128 Dec 31  1969 controlC4
crw-------    1 wa1ter   audio    116, 160 Dec 31  1969 controlC5
crw-------    1 wa1ter   audio    116, 192 Dec 31  1969 controlC6
crw-------    1 wa1ter   audio    116, 224 Dec 31  1969 controlC7
crw-------    1 wa1ter   audio    116,  24 Dec 31  1969 pcmC0D0c
crw-------    1 wa1ter   audio    116,  16 Dec 31  1969 pcmC0D0p
crw-------    1 wa1ter   audio    116,  25 Dec 31  1969 pcmC0D1c
crw-------    1 wa1ter   audio    116,  17 Dec 31  1969 pcmC0D1p
crw-------    1 wa1ter   audio    116,   1 Dec 31  1969 seq
crw-------    1 wa1ter   audio    116,  33 Dec 31  1969 timer

#ls -l /dev/sound
total 0
crw-------    1 wa1ter   audio     14,  12 Dec 31  1969 adsp
crw-------    1 wa1ter   audio     14,   4 Dec 31  1969 audio
crw-------    1 wa1ter   audio     14,   3 Dec 31  1969 dsp
crw-------    1 wa1ter   audio     14,   0 Dec 31  1969 mixer
crw-------    1 wa1ter   audio     14,   1 Dec 31  1969 sequencer
crw-------    1 wa1ter   audio     14,   8 Dec 31  1969 sequencer2

#ls -l /dev/dsp
lr-xr-xr-x    1 root     root            9 May  9 10:33 /dev/dsp -> sound/dsp
#ls -l /dev/adsp
lr-xr-xr-x    1 root     root           10 May  9 10:33 /dev/adsp -> sound/adsp


Seems to me that any symlinks to /proc don't really belong in /dev.
Any opinions to the contrary?  (Remember:  my sound is working just fine.)





       reply	other threads:[~2003-05-09 18:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.j6n4o02.sl813a@ifi.uio.no>
     [not found] ` <fa.juutvqv.1inovpj@ifi.uio.no>
2003-05-09 18:14   ` walt [this message]
2003-05-09 19:12     ` ALSA busted in 2.5.69 Andy Pfiffer
2003-05-09 19:41       ` David van Hoose
2003-05-10  6:04       ` Norbert Wolff
2003-05-10 23:20         ` David Ford
2003-05-11  0:12           ` [RFC] devfs [was Re: ALSA busted in 2.5.69] David van Hoose
2003-05-11  0:36             ` David Ford
2003-05-11  0:14         ` ALSA busted in 2.5.69 David van Hoose
2003-05-09 19:48 Downing, Thomas
  -- strict thread matches above, loose matches on Subject: below --
2003-05-08 23:39 Torrey Hoffman
2003-05-09  8:09 ` Giuliano Pochini
2003-05-09  9:08   ` Jan Dittmer
2003-05-09 15:23   ` Torrey Hoffman
2003-05-09 19:37 ` Jose Luis Domingo Lopez

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=3EBBF00D.8040108@hotmail.com \
    --to=wa1ter@hotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pochini@shiny.it \
    --cc=thoffman@arnor.net \
    /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;
as well as URLs for NNTP newsgroup(s).