Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Clemens Ladisch" <cladisch@fastmail.net>
To: Krzysztof Helt <krzysztof.h1@gmail.com>,
	ALSA devel <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] opti931: additional check for OPL3 device
Date: Fri, 14 Sep 2007 16:52:47 +0200	[thread overview]
Message-ID: <1189781567.3648.1210664373@webmail.messagingengine.com> (raw)
In-Reply-To: <8c74410a0709140735j3903a11dp23f783d45bffc55c@mail.gmail.com>

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).

On cards with an OPL4, it would use the entire range, where that last
eight bytes are the OPL3-compatible registers.

AFAIK the opti93x chips have an integrated OPL3 and cannot be used
with an OPL4.

> If someone can test if the opti92x PnP has the same problem I would be
> grateful.

My card doesn't have PnP, but I guess the OPL4 detection wouldn't work
on 92x either for the same reason.


Regards,
Clemens

  reply	other threads:[~2007-09-14 14:52 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 [this message]
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

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=1189781567.3648.1210664373@webmail.messagingengine.com \
    --to=cladisch@fastmail.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox