linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Torrey Hoffman <thoffman@arnor.net>
To: Giuliano Pochini <pochini@shiny.it>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: RE: ALSA busted in 2.5.69
Date: 09 May 2003 08:23:42 -0700	[thread overview]
Message-ID: <1052493821.1209.6.camel@torrey.et.myrio.com> (raw)
In-Reply-To: <XFMail.20030509100906.pochini@shiny.it>

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.

(This works under Red Hat 9's standard kernel with the ALSA 0.9.3
drivers, by the way.)

Torrey



  parent reply	other threads:[~2003-05-09 15:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-08 23:39 ALSA busted in 2.5.69 Torrey Hoffman
2003-05-09  8:09 ` Giuliano Pochini
2003-05-09  9:08   ` Jan Dittmer
2003-05-09 15:23   ` Torrey Hoffman [this message]
2003-05-09 19:37 ` Jose Luis Domingo Lopez
     [not found] <fa.j6n4o02.sl813a@ifi.uio.no>
     [not found] ` <fa.juutvqv.1inovpj@ifi.uio.no>
2003-05-09 18:14   ` walt
2003-05-09 19:12     ` 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:14         ` David van Hoose
2003-05-09 19:48 Downing, Thomas

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=1052493821.1209.6.camel@torrey.et.myrio.com \
    --to=thoffman@arnor.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pochini@shiny.it \
    /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).