From: Michael Corlett <ad@corlett.plus.com>
To: alsa-devel@lists.sourceforge.net
Subject: ISA pnp & kernel 2.6
Date: Wed, 11 Feb 2004 21:57:35 +0000 [thread overview]
Message-ID: <402AA54F.3050705@gremlin> (raw)
I have an ISA pnp card (opti931) which stopped working when I
installed kernel 2.6 and the problem is as follows:
The kernel function that sets and activates the card is
isapnp_set_resources (in drivers/pnp/isapnp/core.c) and for
each resource, it is checking that the correct flag is set
before writing to the port (i.e. IORESOURCE_IO, IORESOURCE_IRQ,
IORESOURCE_DMA, IORESOURCE_MEM) however, these flags are never
being set because the driver code is just using
pnp_init_resource_table followed by pnp_resource_change for each
setting and so the configuration is never written to the card.
(I believe that the equivalent code in 2.4 just checked for
flags != 0).
As I see it, there are four options:
1) Manually set the flags in the driver code (this is what I have
done temporarily to get the card working).
2) Change the test in isapnp_set_resources to
((flags & IORESOURCE_xx) | (~flags & IORESOURCE_AUTO))
as anything that has been auto-allocated should have the
appropriate flag set.
3) Change pnp_resource_change to clear IORESOURCE_UNSET and change
the test in isapnp_set_resources to
(~flags & IORESOURCE_UNSET)
4) In the driver, use something else apart from pnp_resource_change
(i.e. is there now a preferred method for filling in the
settings).
I prefer 3) or else 2) but are there any reasons not to do this?
Any advice welcome.
Michael.
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
next reply other threads:[~2004-02-11 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 21:57 Michael Corlett [this message]
2004-02-12 10:35 ` ISA pnp & kernel 2.6 Takashi Iwai
2004-02-12 17:19 ` Michael Corlett
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=402AA54F.3050705@gremlin \
--to=ad@corlett.plus.com \
--cc=alsa-devel@lists.sourceforge.net \
/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