> Apparently, snd_usb_audio_disconnect is called recursively, caused by
> the call to usb_driver_release_interface, and then deadlocks.
>
> The USB core will release all interfaces automatically, so we don't
> need this call. Please remove the usb_driver_release_interface line.
Sorry, in case of
Clemens Ladisch wrote:
> Apparently, snd_usb_audio_disconnect hangs before returning. Please
> try to insert printk's in snd_usbmidi_disconnect as Takashi suggestes.
>
I removed the quick hack from Mathieu and inserted snd_printk's in
snd_usbmidi_disconnect.
The new function:
void snd_usbmidi
Salut Mathieu,
that fixes the issue with the 4x4 as well.
Let's see what Takashi is thinking about to comment his code. ;-)
Regards, Hartmut
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel
I've the same symptom. Even with kernel 2.6.4 and the patch provided by Clemens.
I own a Midisport 4x4. So it seems not to be model specific.
Initialzing is fine. But unplugin/replugin will request a reboot with sysrq
intervention.
First I've had enabled the USB 2.0 features on my motherboard wi
e DSP-cards.
- an user-space application to manage the different cards, devices and
uploadable plugins
As I understood Willie, the drivers aren't a subject of the NDA.
The NDA covers only the details of the user-space application.
Hartmut
--
Hartmut Geissbauer <[EMAIL PROTECTED]>
r. That's done by my one Windows machine. Ok, that doesn't
happen that much. But it would be fine, to manage the CF-Card and other
settings via the attached computer.
The architecture that I'm able to provide is x86.
Regards, Hartmut
--
Hartmut Geissbauer <[EMAIL PROTECTED]>
Salut Clemens,
Clemens Ladisch wrote:
> Hartmut Geissbauer wrote:
> > > The descriptors look OK.
>
> But only at first sight.
>
> Please try this patch.
>
>
> HTH
> Clemens
That _has_ helped. Now the device is fully functional. Thank you very
much for you
Clemens Ladisch wrote:
> Hartmut Geissbauer wrote:
> > > > The only thing that's missing now are the two playback ports.
> > >
> > > Please show the output of "lsusb -v".
> >
> > bInterfaceNumber2
> > iInterface
Clemens Ladisch wrote:
> Hartmut Geissbauer wrote:
> > > > The only thing that's missing now are the two playback ports.
> > >
> > > Please show the output of "lsusb -v".
> >
> > bInterfaceNumber2
> > iInterface
Hi again,
Clemens Ladisch wrote:
> > > No. Please remove the patch.
> >
> > Done, except of the entries in usbquirks.h. Is it still needed?
>
> No. The quirk entry causes the driver to be loaded even for the first
> configuration, which isn't needed anymore.
>
Ok, it is removed and the device i
ting to this state of
a working device.
Kindly regards, Hartmut
--
Hartmut Geissbauer <[EMAIL PROTECTED]>
---
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software
te program is handled by hotplug?
Might the patch(the code in it) for usbaudio.c you posted before be
helpfull for the program?
BTW: How many devices/"cards" is the snd-usb-audio driver able to
handle?
Regards, Hartmut
--
Hartmut Geissbauer <[EMAIL PROTECTED]>
--
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
>
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
>
s
> alias sound-service-0-12 snd-pcm-oss
>
>
sorry for the question. Do you know, that the new module-init-tools
(former modutils) are using modprobe.conf instead of modules.conf? (for
kernel 2.6.x)
HTH, Hartmut
--
Hartmut Geissbauer <[EMAIL PROTECTED]>
--
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 ls
.org/developers/devclass_docs/midi10.pdf
thank you for the link. A lot of other interesting documents are there
as well.
While one of my favourite interests is to getting deep in technical
details, I'll diving in the specifications and report any success to the
list.
Hartmut
--
Hartmut Geissbau
>
> ciao
reading the different entries in usbquirks.h it looks like they are
taken from the usb-infos like lsusb provides. Is it very difficult to
take the infos from lsusb and translate it to an quirk?
I only need some quick advice and will try it by myself. A good
(
Hello devels,
just a "short" question.
I own a piece of hardware called Noah EX. It's a "tactive instrument
modeller". Wich means, that it calculates the behaviour and sound of
instruments with help of loadable software plugins.
This is well done by the device so far.Because that works without a
19 matches
Mail list logo
