From: David Flater <vger@flaterco.com>
To: alsa-devel@alsa-project.org
Subject: Re: [bug] sbawe: the PnP won't stop
Date: Mon, 25 Mar 2013 21:04:56 -0400 [thread overview]
Message-ID: <5150F438.6090902@flaterco.com> (raw)
In-Reply-To: <514E640E.4060502@flaterco.com>
This problem now appears to be bigger than just sbawe or ALSA.
- The clone-and-reallocate behavior happened with the gameport too, even
though I didn't mess with that at all. The gameport is discovered by some
driver as a legacy port, then later rediscovered and reallocated with
different resources as a PnP gameport.
- The kernel parameter pnp_reserve_dma, which ought to be the right way to
avoid getting DMA 5, doesn't do anything.
The cleanest workaround seems to be to noisapnp the kernel, use the userspace
/sbin/isapnp tool, and provide ALSA module options as for a non-PnP card.
On 03/23/2013 10:25 PM, David Flater wrote:
> I've got an ISA PnP SB AWE type card in a system with a non-working DMA 5.
> Without intervention, the Sound Blaster always gets the broken DMA. I have
> no BIOS options to control the allocation of DMAs, and the PnP configuration
> done within ALSA ignores /etc/isapnp.conf [*]. DMA 6 works fine if I can get
> sbawe to stop re-initializing the PnP and just use it.
prev parent reply other threads:[~2013-03-26 1:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-24 2:25 [bug] sbawe: the PnP won't stop David Flater
2013-03-26 1:04 ` David Flater [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=5150F438.6090902@flaterco.com \
--to=vger@flaterco.com \
--cc=alsa-devel@alsa-project.org \
/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.