All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Rabe <raven@drehmoment.org>
To: Clemens Ladisch <clemens@ladisch.de>, alsa-devel@lists.sourceforge.net
Subject: Re: questions about usbmidi
Date: Thu, 10 Apr 2003 09:29:49 +0200	[thread overview]
Message-ID: <3E951D6D.2040304@drehmoment.org> (raw)
In-Reply-To: <Pine.HPX.4.33n.0304100837520.4179-100000@studcom.urz.uni-halle.de>

Clemens Ladisch wrote:
> Thomas Rabe wrote:
> 
>>Clemens Ladisch wrote:
>>
>>>If this is the only endpoint in the interface, you can omit the endpoint
>>>number and let the driver autodetect it.
>>
>>i don't really know if autodetection will work (for the lsusb see
>>below).
> 
> 
> All endpoints are in one interface, so it wouldn't work.

will i have more luck with snd_usbmidi_create_rawmidi? if yes, should i 
declare the relevant functions/structs needed for rawmidi in usbaudio.h 
or cut'n paste the stuff from usbmidi.c in my driver file?

>>the real problem are the kernel-oopses, the last message i get:
>>ports are created.
>>
>>8<------------------------------------------------------
>>Apr  9 17:57:05 konstruktor kernel: ALSA ../alsa-kernel/usb/usbmidi.c:782: created 2 output and 2 input ports
>>Apr  9 17:57:05 konstruktor kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000004
> 
> 
> Well, this may indicate that the MIDI part works and that the error is in
> some other part of the driver. Does the oops still happen when you don't
> call snd_usb_create_midi_interface?

the driver works fine without calling snd_usb_create_midi_interface (no 
errors, all audiochannels are available). i just wondering why there is 
no error return but the oops. it's very hard to try out hacks, because i 
have to reboot after the oops (can't rmmod the driver and other alsa 
modules).


> HTH
> Clemens


Greetings,

Thomas Rabe.



-- mail: raven at drehmoment dot org
-- home: http://hal9000.drehmoment.org
-- more: http://drehmoment.org



-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com

  reply	other threads:[~2003-04-10  7:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-09 13:01 questions about usbmidi Thomas Rabe
2003-04-09 14:34 ` Clemens Ladisch
2003-04-09 16:08   ` Thomas Rabe
2003-04-10  6:45     ` Clemens Ladisch
2003-04-10  7:29       ` Thomas Rabe [this message]
2003-04-10 10:47         ` Clemens Ladisch
  -- strict thread matches above, loose matches on Subject: below --
2003-04-10 14:38 Thomas Rabe
2003-04-10 15:38 ` Clemens Ladisch
2003-04-10 18:18   ` Thomas Rabe

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=3E951D6D.2040304@drehmoment.org \
    --to=raven@drehmoment.org \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=clemens@ladisch.de \
    /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.