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

Clemens Ladisch wrote:

>>Clemens Ladisch wrote:
> 
> So the oops isn't related to USB at all.
> 
> The first thing after outputting "created ... ports" is the line:
> 
> 	list_add(&umidi->list, &umidi->chip->midi_list);
> 
> It may be possible that your US428 driver doesn't initialize
> chip->midi_list. This may indicate that you didn't merge all the changes
> made to usbaudio.c.

uh, sorry. i forgot the INIT_LIST_HEAD(&us428(card)->chip.midi_list) 
call. now midi works and everything is fine:) thanks!


> 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 18:18 UTC|newest]

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

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=3E95B581.3050605@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.