All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@gmail.com>
To: Clemens Ladisch <cladisch@fastmail.net>
Cc: Krzysztof Helt <krzysztof.h1@gmail.com>,
	ALSA devel <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] opti931: additional check for OPL3 device
Date: Mon, 17 Sep 2007 12:10:12 +0200	[thread overview]
Message-ID: <46EE5284.9070202@gmail.com> (raw)
In-Reply-To: <1190016893.19336.1210994773@webmail.messagingengine.com>

[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]

On 09/17/2007 10:14 AM, Clemens Ladisch wrote:

> Krzysztof Helt wrote:

>> Should the OPL4 detection has the same fallback or just all Opti cards
>> should search the FM chip at the range + 8 address?
> 
> It appears a fallback shoudn't be needed because the chip always returns 
> a range suitable for an OPL4.
> 
> Since an OPL3 range is never larger than 8 bytes, and OPL4 needs 16 
> bytes, we could add 8 to get the FM address _if_ the range is at least 16
> bytes; thus we are safe even if a chip publishes an OPL3-only range.

At least 16 won't do -- the OPTi chip provides a 12-byte range. More than 8 
would work, but just +8 is fine. I have all OPTi ISA-PnP chips (924, 925, 
931, 933) and more aren't going to be produced. The 0x380 base is what it 
calls the OPL4Base and ALBase (AdLib) is at 0x388.

The chip can defer to external FM it seems, but even if there are OPTi/OPL4 
combo's out there in the wild (I sort of doubt it) the driver's just doing 
opl3 anyway. ie, still needs just the +8.

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

  reply	other threads:[~2007-09-17 10:11 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 [this message]
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

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=46EE5284.9070202@gmail.com \
    --to=rene.herman@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=cladisch@fastmail.net \
    --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.