From: Rene Herman <rene.herman@gmail.com>
To: Krzysztof Helt <krzysztof.h1@gmail.com>
Cc: ALSA devel <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] opti931: additional check for OPL3 device
Date: Fri, 14 Sep 2007 18:33:35 +0200 [thread overview]
Message-ID: <46EAB7DF.8010707@gmail.com> (raw)
In-Reply-To: <8c74410a0709140735j3903a11dp23f783d45bffc55c@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
On 09/14/2007 04:35 PM, Krzysztof Helt wrote:
> This patch adds additional check for OPL3 device. I found that PNP region
> returned by the card is 0x380 - 0x38f but the OPL3 device is located at
> 0x388 (standard FM device address). The driver checks start of the range
> (0x380) which is incorrect.
> The same problem appears on two cards I have with Opti chipset: opti931
> and opti933. If someone can test if the opti92x PnP has the same problem
> I would be grateful.
Yes, same for OPT0924/OPT0925 (928, 929 and 930 are Non-PnP).
I'd rather simply adjust the resource in snd_card_opti9xx_pnp though -- that
way, you don't go second guessing a user-specified value.
Untested, but looks as though this should do it:
Rene.
[-- Attachment #2: opti9xx-fm_port.diff --]
[-- Type: text/plain, Size: 652 bytes --]
diff --git a/sound/isa/opti9xx/opti92x-ad1848.c b/sound/isa/opti9xx/opti92x-ad1848.c
index 60c120f..8bda47a 100644
--- a/sound/isa/opti9xx/opti92x-ad1848.c
+++ b/sound/isa/opti9xx/opti92x-ad1848.c
@@ -1732,11 +1732,11 @@ static int __devinit snd_card_opti9xx_pnp(struct snd_opti9xx *chip,
#ifdef OPTi93X
port = pnp_port_start(pdev, 0) - 4;
- fm_port = pnp_port_start(pdev, 1);
+ fm_port = pnp_port_start(pdev, 1) + 8;
#else
if (pid->driver_data != 0x0924)
port = pnp_port_start(pdev, 1);
- fm_port = pnp_port_start(pdev, 2);
+ fm_port = pnp_port_start(pdev, 2) + 8;
#endif /* OPTi93X */
irq = pnp_irq(pdev, 0);
dma1 = pnp_dma(pdev, 0);
[-- Attachment #3: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2007-09-14 16:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 14:35 [PATCH] opti931: additional check for OPL3 device Krzysztof Helt
2007-09-14 14:52 ` Clemens Ladisch
2007-09-14 16:47 ` Krzysztof Helt
2007-09-17 8:14 ` Clemens Ladisch
2007-09-17 10:10 ` Rene Herman
2007-09-17 10:39 ` Clemens Ladisch
2007-09-17 12:26 ` Rene Herman
2007-09-17 12:26 ` Krzysztof Helt
2007-09-17 12:40 ` Rene Herman
2007-09-17 13:57 ` Rene Herman
2007-09-17 14:45 ` Krzysztof Helt
2007-09-17 15:09 ` Takashi Iwai
2007-09-17 23:04 ` Rene Herman
2007-09-14 16:33 ` Rene Herman [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=46EAB7DF.8010707@gmail.com \
--to=rene.herman@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=krzysztof.h1@gmail.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.