public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Lee Revell <rlrevell@joe-job.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [ALSA - driver 0002219]: snd-mpu401 don't load
Date: Wed, 21 Jun 2006 01:46:34 +0200	[thread overview]
Message-ID: <449888DA.3090009@keyaccess.nl> (raw)
In-Reply-To: <1150846540.2754.195.camel@mindpipe>

Lee Revell wrote:

>>> ----------------------------------------------------------------------
>>>  rlrevell - 06-21-06 00:18 
>>> ----------------------------------------------------------------------
>>> It must be a kernel bug if the port does not appear in /proc/ioports.

>> Lee, please note that legacy (ISA/LPC, even PnP/ACPI controlled) hw does 
>> not ever appear in /proc/ioports without the driver loaded and having 
>> done a request_region().
>>
>> By the way, the missing IRQ is not necesarily a problem. An MPU401 can 
>> output MIDI fine without using an IRQ and if his BIOS does not let him 
>> assign an IRQ (and Windows does not use one) I guess no IRQ is available 
>> for it.
> 
> So where's the bug?

Dunno -- but the snd-mpu401 thing is irrelevant; he said snd-mpu401-uart 
_was_ being loaded, and it should then just take care of the port. As to 
why it's not doing so...

Maybe it's under an unknown PnP ID and not being enabled or something 
like that. Dunno again.

Rene.

  reply	other threads:[~2006-06-20 23:45 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-20 22:36 [ALSA - driver 0002219]: snd-mpu401 don't load bugtrack
2006-06-20 23:30 ` Rene Herman
2006-06-20 23:35   ` Lee Revell
2006-06-20 23:46     ` Rene Herman [this message]
2006-06-20 23:54       ` Lee Revell
2006-06-20 23:57       ` Rene Herman
  -- strict thread matches above, loose matches on Subject: below --
2006-06-27  6:41 bugtrack
2006-06-26 17:25 bugtrack
2006-06-26 17:14 bugtrack
2006-06-26 16:51 bugtrack
2006-06-26 16:44 bugtrack
2006-06-26  4:52 bugtrack
2006-06-25 20:02 bugtrack
2006-06-24  7:43 bugtrack
2006-06-22 12:30 bugtrack
2006-06-22  1:29 bugtrack
2006-06-22  1:19 bugtrack
2006-06-21 16:00 bugtrack
2006-06-21  2:51 bugtrack
2006-06-21  0:02 bugtrack
2006-06-20 22:56 bugtrack
2006-06-20 22:52 bugtrack
2006-06-20 22:18 bugtrack
2006-06-20 22:12 bugtrack
2006-06-20 22:04 bugtrack
2006-06-20 22:00 bugtrack
2006-06-20 21:54 bugtrack
2006-06-20 21:39 bugtrack
2006-06-20 21:30 bugtrack
2006-06-20 17:49 bugtrack
2006-06-19  1:45 bugtrack
2006-06-18 15:41 bugtrack

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=449888DA.3090009@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=alsa-devel@alsa-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox