All of lore.kernel.org
 help / color / mirror / Atom feed
From: "mjander " <mjander@embedded.cl>
To: alsa-devel@alsa-project.org
Subject: devfs OSS /dev/sound/* problem.
Date: Mon, 10 Mar 2003 10:57:43 -0400	[thread overview]
Message-ID: <200303101057.AA55640994@embedded.cl> (raw)

Hello,

I noticed the  following bug:

If i load more than one soundcard driver  (example ens1371 and
intel8x0),
with OSS support i  get a error message  from "devfs", that it 
"could not append
to /dev/sound", and the second  soundcard is  unable to create its
OSS /dev/sound/*
file nodes.

I noticed similar bugs in other OSS sound drivers before, but it
semes that very few people  use devfs. Yesterday i checked with
0.9rc8d (previous tests with 0.9rc7) and the problem is  still there.

I semes to me that the file node index passes to the corresponding
devfs_register() calls is static rather incremental or -1 for
automatic allocation as it should be.

Does this behave the same with any 2.5 kernel? I'm to much a
coward to try 2.5, last time i did, i lost very important data.

Kernel 2.4.20  + xfs
Dist: Debian SID
ALSA: 0.9rc8d
ARCH: i386


Best Regards

Manuel Jander.
.
__________________________________________________
Enviado via NewPlanet WebMail en embedded.cl


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

             reply	other threads:[~2003-03-10 13:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-10 14:57 mjander  [this message]
2003-03-10 14:08 ` devfs OSS /dev/sound/* problem Jaroslav Kysela
2003-03-10 14:12 ` Takashi Iwai

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=200303101057.AA55640994@embedded.cl \
    --to=mjander@embedded.cl \
    --cc=alsa-devel@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.