All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hartmut Geissbauer <nwgbh@swissonline.ch>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Creamware Noah, snd-usb-audio capable?
Date: Mon, 16 Feb 2004 19:18:10 +0100	[thread overview]
Message-ID: <1076955490.2515.11.camel@chief.local> (raw)
In-Reply-To: <Pine.HPX.4.33n.0402161110040.4733-100000@studcom.urz.uni-halle.de>

Hi Clemens,

Clemens Ladisch wrote:
> Hartmut Geissbauer wrote:
> > Clemens Ladisch wrote:
> > > The problem is that the kernel automatically selects the first
> > > configuration.  Please try the patch below.
> >
> > drivers/usb/core/usb.c: usb_hotplug
> > usb 1-2.4: configuration #1 chosen from 2 choices
> > usb 1-2.4: registering 1-2.4:1.0 (config #1, interface 0)
> > drivers/usb/core/usb.c: usb_hotplug
> > snd-usb-audio 1-2.4:1.0: usb_probe_interface
> > snd-usb-audio 1-2.4:1.0: usb_probe_interface - got id
> >
> > The device is not appearing in /proc/asound.
> 
> Does the new configuration (the audio interfaces) show up in
> /proc/bus/usb/devices?  

No.

> What happens when you re-load snd-usb-audio
> after that?
> 

'rmmod snd-usb-audio' does not return to the command prompt. A 'modprobe
snd-usb-audio'  on another xterm after the rmmod as well.

dmesg shows me:
drivers/usb/core/usb.c: deregistering driver snd-usb-audio

I tried to connect the device via a hub and direct. No difference.

> 
> Regards,
> Clemens
> 

Thank you for your answer, Hartmut

-- 
Hartmut Geissbauer <nwgbh@swissonline.ch>



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click

  reply	other threads:[~2004-02-16 18:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-06 19:06 Creamware Noah, snd-usb-audio capable? Hartmut Geissbauer
2004-02-07  2:20 ` Paul Davis
2004-02-10 16:56   ` Frank Barknecht
2004-02-10 18:36     ` Hartmut Geissbauer
2004-02-10 21:36       ` Frank Barknecht
2004-02-10 22:08         ` Hartmut Geissbauer
2004-02-12 11:02           ` Clemens Ladisch
2004-02-14 20:14             ` Hartmut Geissbauer
2004-02-16 10:12               ` Clemens Ladisch
2004-02-16 18:18                 ` Hartmut Geissbauer [this message]
2004-02-16 18:36                 ` Hartmut Geissbauer
2004-02-17 12:43                   ` Clemens Ladisch
2004-02-17 17:04                     ` Hartmut Geissbauer
2004-02-18  8:03                       ` Clemens Ladisch
2004-02-18 18:59                         ` [partialy fixed] " Hartmut Geissbauer
2004-02-19  8:21                           ` Clemens Ladisch
2004-02-19 22:04                             ` Hartmut Geissbauer
2004-02-20 11:10                               ` Clemens Ladisch
2004-02-23 17:46                                 ` Hartmut Geissbauer
2004-02-26 10:39                                   ` Clemens Ladisch
2004-02-26 18:15                                     ` [fixed] " Hartmut Geissbauer
2004-02-24 19:07                                 ` [partialy fixed] " Hartmut Geissbauer
2004-02-11  9:46         ` Clemens Ladisch
2004-02-11 18:00           ` Frank Barknecht
2004-02-12 10:03             ` Clemens Ladisch
2004-02-12 17:52               ` Frank Barknecht

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=1076955490.2515.11.camel@chief.local \
    --to=nwgbh@swissonline.ch \
    --cc=alsa-devel@lists.sourceforge.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 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.