From: Hartmut Geissbauer <nwgbh@swissonline.ch>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Creamware Noah, snd-usb-audio capable?
Date: Sat, 14 Feb 2004 21:14:07 +0100 [thread overview]
Message-ID: <1076789647.2475.5.camel@chief.local> (raw)
In-Reply-To: <Pine.HPX.4.33n.0402111431430.12076-100000@studcom.urz.uni-halle.de>
Hi Clemens
Clemens Ladisch wrote:
> Hartmut Geissbauer wrote:
> > I own a piece of hardware called Noah EX. It's a "tactive
> > instrument modeller".
> > My goal is to get this device working with the alsa usb driver,
> > because the output of lsusb -v leads me to the hope, that it has a
> > standard usb audio interface.
> > ...
> > Interface Descriptor:
> > bInterfaceClass 1 Audio
> > bInterfaceSubClass 1 Control Device
> > ...
> > bInterfaceSubClass 2 Streaming (= PCM)
> > ...
> > bInterfaceSubClass 3 Non Streaming (= MIDI)
>
> Well, this device indeed has standard descriptors.
>
> > What I discoverd yet, is that the device is offering two
> > configurations. And the second is the audio and midi related one.
> > The first seems to be the configuration "channel".
>
> > Feb 5 00:28:33 chief kernel: usb 1-2.4: configuration #1 chosen from 2 choices
>
> The problem is that the kernel automatically selects the first
> configuration. Please try the patch below.
>
>
> HTH
> Clemens
sorry for responding that late. I've been out for skiing for a few days.
I tried the patch applying it at last to kernel 2.6.3-rc-2 to get away
from the unresolved symbol "usb_get_device_descriptor".
So now the dmesg command shows me:
hub 1-2:1.0: port 4, status 101, change 1, 12 Mb/s
hub 1-2:1.0: debounce: port 4: delay 100ms stable 4 status 0x101
hub 1-2:1.0: port 4 not reset yet, waiting 10ms
usb 1-2.4: new full speed USB device using address 3
usb 1-2.4: new device strings: Mfr=1, Product=2, SerialNumber=0
drivers/usb/core/message.c: USB device number 3 default language ID
0x409
usb 1-2.4: Product: CreamWare Noah Synthesizer
usb 1-2.4: Manufacturer: CreamWare GmbH
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.
After that action, the usb-stack is stuck. Not recognizing any new
connects or disconnects. I tried to compile the kernel with ohci (that's
my controller type) as a module and built in.
The same behaviour appears after removing a M-Audio Midisport4x4 from
the usb port. It works only one time. (Plugging it in, it is working,
plug it out, the usb stack is dead)
So it seems, that there is something wrong with the usb stack in 2.6.x
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
next prev parent reply other threads:[~2004-02-14 20:14 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 [this message]
2004-02-16 10:12 ` Clemens Ladisch
2004-02-16 18:18 ` Hartmut Geissbauer
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=1076789647.2475.5.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.