From: Pete Zaitcev <zaitcev@metabyte.com>
To: proski@gnu.org (Pavel Roskin)
Cc: linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
zaitcev@metabyte.com (Pete Zaitcev),
perex@suse.cz (Jaroslav Kysela)
Subject: Re: [PATCH] for YMF PCI sound cards
Date: Fri, 8 Dec 2000 10:31:10 -0800 (PST) [thread overview]
Message-ID: <200012081831.KAA06813@ns1.metabyte.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0012081128330.5353-100000@fonzie.nine.com> from "Pavel Roskin" at Dec 08, 2000 11:41:07 AM
> Date: Fri, 8 Dec 2000 11:41:07 -0500 (EST)
> From: Pavel Roskin <proski@gnu.org>
> To: <linux-kernel@vger.kernel.org>
> cc: <linux-sound@vger.kernel.org>, Pete Zaitcev <zaitcev@metabyte.com>,
> Jaroslav Kysela <perex@suse.cz>
> --- ./drivers/sound/Config.in Thu Dec 7 10:59:06 2000
> +++ ./drivers/sound/Config.in Fri Dec 8 11:25:08 2000
No problem here.
> --- ./drivers/sound/ymfpci.c Thu Dec 7 10:59:06 2000
> +++ ./drivers/sound/ymfpci.c Fri Dec 8 11:33:51 2000
The idea of the patch looks good but there is a small problem.
I have an open/close fix queued with Alan for post-2.2.18,
which changes the enumeration scheme for ymfcpi to make it
more friendly to other sound cards (Bug from Abhijit Menon-Sen).
This is a conflict because you use instance number to find
what card goes in first. In fact I plan to send the same
thing to Linus for 2.4 (if he have not fixed that already).
Would you please to hold on to your patch for couple of weeks
and then resync and redo it? Alternatively, I'll keep your
patch and will reapply it in the way I see sane, but you will
have to retest it before I issue it.
> --- ./drivers/sound/ac97_codec.c Thu Dec 7 10:59:06 2000
> +++ ./drivers/sound/ac97_codec.c Thu Dec 7 11:00:44 2000
> @@ -61,6 +61,7 @@
> } ac97_codec_ids[] = {
> {0x414B4D00, "Asahi Kasei AK4540 rev 0", NULL},
> {0x414B4D01, "Asahi Kasei AK4540 rev 1", NULL},
> + {0x41445303, "Yamaha YMF????" , NULL},
Are you sure it's correct? I am almost certain that no YMFxxx
has on-chip AC97. I'd like to see a document that allows you
the change quoted above.
--Pete
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-08 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-08 16:41 Pavel Roskin
2000-12-08 18:31 ` Pete Zaitcev [this message]
2000-12-08 18:46 ` Jaroslav Kysela
2000-12-08 18:56 ` Pavel Roskin
2000-12-08 23:57 ` Alan Cox
2000-12-08 17:55 Adam J. Richter
2000-12-08 23:51 ` Alan Cox
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=200012081831.KAA06813@ns1.metabyte.com \
--to=zaitcev@metabyte.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@suse.cz \
--cc=proski@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®