Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Patrick Shirkey <pshirkey@boosthardware.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Experimental USB audio support
Date: Fri, 31 May 2002 15:44:42 +0200	[thread overview]
Message-ID: <s5h8z60h1o5.wl@alsa2.suse.de> (raw)
In-Reply-To: <3CF75B1C.64F308D1@boosthardware.com>

At Fri, 31 May 2002 20:14:36 +0900,
Patrick Shirkey wrote:
> 
> Takashi Iwai wrote:
> > 
> > At Fri, 31 May 2002 11:41:46 +0200,
> > I wrote:
> > >
> > > > > > devfs: devfs_register(): device already registered: "unknown"
> > > > >
> > > > > this is a bug of sound_core.c.  you can fix it by replacing
> > > > > sound_core.c with the one in alsa-kernel tree.
> > > > >
> > > >
> > > > General question. Is the above likely to cause problems if I don't swap
> > > > them?
> > >
> > > no, it works fine on 2.4 kernel, too.  i'm using it.
> > 
> > err, my statement was not clear --
> > 
> 
> Yep :)
> 
> > original sound_core.c is ok as long as if you don't use devfs _and_
> > multiple cards.  the one in alsa-kernel is fixed for such a
> > condition.  but, generally, swapping to the fixed one will cause no
> > problem.  it's fully compatible.
> > 
> 
> So as long as I don't use devfs I don't need it. Currently I still use
> the /proc interface but I don't have concrete understanding of the
> difference between the two yet. fromwhat I gathered you have to specify
> devfs in the kernel for it to be used. Is that correct?

yes.  let me rephrase:

if you use devfs interface for /dev, you cannot use the 2nd or later
card with the original sound_core.c on 2.4 kernel.
if you use proc interface for /dev/snd, it works anyway.

also -

if you build the kernel with devfs support and use 2nd or later cards,
then you'll get annoying error messages, even if you use proc
interface.  (it's harmless, though.)


Takashi

_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

  reply	other threads:[~2002-05-31 13:44 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <s5hy9e2hk02.wl@alsa2.suse.de>
2002-05-30  4:12 ` Experimental USB audio support Patrick Shirkey
2002-05-30  4:16 ` Patrick Shirkey
2002-05-31  8:45   ` Takashi Iwai
2002-05-30  5:15 ` Patrick Shirkey
2002-05-31  8:03   ` Takashi Iwai
2002-05-31  9:23     ` Patrick Shirkey
2002-05-31  9:38       ` Takashi Iwai
2002-05-31 10:51         ` Takashi Iwai
2002-05-31 11:09           ` Patrick Shirkey
2002-05-31 11:55           ` Patrick Shirkey
2002-05-31 13:38             ` Takashi Iwai
2002-06-03  5:52               ` Patrick Shirkey
2002-06-03 15:35                 ` Takashi Iwai
2002-05-31 12:02           ` Patrick Shirkey
2002-05-31 12:07           ` Patrick Shirkey
2002-05-31  9:31     ` Patrick Shirkey
2002-05-31  9:41       ` Takashi Iwai
2002-05-31 10:48         ` Takashi Iwai
2002-05-31 11:14           ` Patrick Shirkey
2002-05-31 13:44             ` Takashi Iwai [this message]
2002-05-30  5:49 ` Patrick Shirkey
2002-05-30  8:17 ` tpeltone
     [not found] ` <001401c20747$642f5050$57c05c90@Witter>
2002-05-31  8:47   ` [Alsa-user] " Takashi Iwai
     [not found]     ` <1022849629.589.2.camel@coldpack>
2002-05-31 17:33       ` Takashi Iwai
2002-05-29 18:44 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=s5h8z60h1o5.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=pshirkey@boosthardware.com \
    /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