Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark J Roberts <mjr@znex.org>
To: Jaroslav Kysela <perex@perex.cz>
Cc: "alsa-devel@lists.sourceforge.net" <alsa-devel@lists.sourceforge.net>
Subject: Re: MIDI input broken with ECS P4S5A/DX+ motherboard and generic MPU-401 driver. (Output works fine, though.)
Date: Wed, 29 Jan 2003 15:27:58 -0600	[thread overview]
Message-ID: <20030129212758.GA205@znex> (raw)
In-Reply-To: <Pine.LNX.4.44.0301291115150.1402-100000@pnote.perex-int.cz>

Jaroslav Kysela:
> You've pointed to the reason: hardware does not generate input interrupts.
> Try to disable the IRQ (snd-mpu401=1,,,0x300,-1).

I had to set the index field there to "1" or "-1" in order to get
the MPU-401 recognized at bootup. (I have another sound card in
this box too, maybe that's why.)

As I said, I've already tried disabling the IRQ, and I get the same
behavior. I just did it again to make sure - this time I'm running
2.4.49 with merged-in 2.5.59 alsa code. (Matrox framebuffer...)

I boot up and see this:

Advanced Linux Sound Architecture Driver Version 0.9.0rc6 (Tue Dec 17 19:01:13 2002 UTC).
PCI: Found IRQ 5 for device 00:0c.0
PCI: Sharing IRQ 5 with 00:08.0
ALSA device list:
  #0: MPU-401 UART at 0x300, polled
  #1: Sound Blaster Audigy at 0xc800, irq 5
NET4: Linux TCP/IP 1.0 for NET4.0

But still no luck trying to read anything:

$ cat /dev/snd/midiC0D0 &

$ cat /proc/asound/UART/midi0
MPU-401 (UART)

Output 0
  Tx bytes     : 20
Input 0
  Rx bytes     : 0
  Buffer size  : 4096
  Avail        : 0
  Overruns     : 0



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

      reply	other threads:[~2003-01-29 21:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-28 20:39 MIDI input broken with ECS P4S5A/DX+ motherboard and generic MPU-401 driver. (Output works fine, though.) Mark J Roberts
2003-01-29 10:17 ` Jaroslav Kysela
2003-01-29 21:27   ` Mark J Roberts [this message]

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=20030129212758.GA205@znex \
    --to=mjr@znex.org \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=perex@perex.cz \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox