From: Takashi Iwai <tiwai@suse.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Domen Puncer <domen@coderock.org>,
alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Re: snd_mpu401_uart: hang when trying to play .mid
Date: Mon, 06 Sep 2004 22:45:04 +0200 [thread overview]
Message-ID: <s5hwtz7unxr.wl@alsa2.suse.de> (raw)
In-Reply-To: <1094501904.29921.56.camel@krustophenia.net>
At Mon, 06 Sep 2004 16:18:25 -0400,
Lee Revell wrote:
>
> On Mon, 2004-09-06 at 14:58, Domen Puncer wrote:
> > On 06/09/04 18:25 +0200, Takashi Iwai wrote:
> > > At Mon, 6 Sep 2004 17:48:19 +0200,
> > > Domen Puncer wrote:
> > > > On 06/09/04 17:18 +0200, Takashi Iwai wrote:
> > > > > At Sun, 5 Sep 2004 11:22:35 +0200,
> > > > > Domen Puncer wrote:
> > > > > Does your hardware really a MPU401 device?
> > > >
> > > > I don't know, probably not.
> > > >
> > > > > If not, you can remove the call of snd_mpu401_uart_new() in
> > > > > snd_trident_probe().
> > > >
> > > > Or just never start kmid again :-)
> > > > My point is: user can hang the computer; this is a bug.
> > >
> > > Sure. Removing the unneeded creation of mpu401 interface is _the_
> > > solution if you really don't have mpu401.
> >
> > Umm... you mean removing this for linus tree? Then why it was there
> > in the first place?
>
> No, Takashi-san is telling you to try commenting this out and recompile
> and see if the problem goes away. If so then we can figure out how to
> detect this MPU-less device and fix it in ALSA CVS. He probably does
> not have access to the hardware to test it himself.
Exactly. Thanks for interpretation ;)
> This is a pretty common issue with ALSA because a lot of cards that
> purport to be the same as another have small differences, and the alsa
> devs can't possibly test every single device.
Yes, indeed, the trident code is shared among several different chips
(trident 4D DX, 4D NX and SI7018), and MPU401 handling seems hitting
on SI7018 only. I guess SI7018 is equipped mostly on laptops, which
unlikely have MPU401 connectors. So, removing the mpu401 support for
SI7018 may be the simplest and safest solution.
Of course, we can track down the hang-up point (perhaps in the
interrupt handler, snd_mpu401_uart_interrupt()) and fix it, too.
Takashi
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
next prev parent reply other threads:[~2004-09-06 20:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-05 9:22 snd_mpu401_uart: hang when trying to play .mid Domen Puncer
2004-09-06 15:18 ` Takashi Iwai
2004-09-06 15:48 ` Domen Puncer
2004-09-06 16:25 ` Takashi Iwai
2004-09-06 18:58 ` Domen Puncer
2004-09-06 20:18 ` Lee Revell
2004-09-06 20:45 ` Takashi Iwai [this message]
2004-09-07 6:18 ` Domen Puncer
2004-09-10 13:22 ` Domen Puncer
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=s5hwtz7unxr.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=domen@coderock.org \
--cc=rlrevell@joe-job.com \
/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.