From: Takashi Iwai <tiwai@suse.de>
To: Osamu Tomita <tomita@cinet.co.jp>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHSET 22/25] add support for PC-9800 architecture (sound alsa)
Date: Mon, 04 Nov 2002 11:17:31 +0100 [thread overview]
Message-ID: <s5hlm49r64k.wl@alsa2.suse.de> (raw)
In-Reply-To: <3DC33BF8.272FD554@cinet.co.jp>
At Sat, 02 Nov 2002 11:44:08 +0900,
Osamu Tomita wrote:
>
> Takashi Iwai wrote:
> >
> > At Fri, 1 Nov 2002 22:02:18 +0900,
> > Osamu Tomita wrote:
> > > Now, PCM OPL3 and MPU401 all works fine.
> > > Would you please add option "pc98ii" into snd-mpu401?
> > > This is for Box that has MPU-PC98II only, with no other sound card.
> >
> > well, then i misunderstood the hardware configuration on PC98.
> >
> > doesn't MPU-PC98II need any specific hardware init code like in
> > pc98_mpu401_init()?
> MPU-PC98II doesn't need those init codes. Apologize for not enough
> explanations.
> On-board sound and sound cards made by NEC need those init codes.
> Perhaps, for backward compatibility, PC-9800's BIOS masks newer
> features like WSS PCM, OPL3 FM synth and MPU-401 compatible IF.
> After cold booting, they works as oldest sound card of NEC (PC-
> 9801-26). So I added some init codes to enable those features.
> Most sound cards made by third parties (MPU-98, Sound blaster16
> for PC9800...etc) don't need these init codes.
OK. thanks for clarification.
> > if yes, then we should create another module for PC98II rather than
> > including a magical init code into a generic mpu401 module.
> Init code for MPU-401 detects wheter NEC or not. If MPU-401 is
> not NEC's, skip magical initialization. So I think it's beter,
> your patch and adding option to mpu401.c
Agreed.
Now i put the patch into ALSA cvs tree.
I hope Jaroslav will submit the patchset soon.
--
Takashi Iwai <tiwai@suse.de> SuSE Linux AG - www.suse.de
ALSA Developer ALSA Project - www.alsa-project.org
next prev parent reply other threads:[~2002-11-04 10:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-26 2:54 Osamu Tomita
2002-10-28 17:57 ` Takashi Iwai
2002-10-29 10:08 ` Takashi Iwai
2002-10-29 17:43 ` Osamu Tomita
2002-10-30 17:52 ` Takashi Iwai
2002-11-01 13:02 ` Osamu Tomita
2002-11-01 13:44 ` Takashi Iwai
2002-11-02 2:44 ` Osamu Tomita
2002-11-04 10:17 ` Takashi Iwai [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-25 2:47 Osamu Tomita
2002-10-25 10:10 ` Takashi Iwai
2002-10-25 2:12 Osamu Tomita
2002-10-18 16:56 Osamu Tomita
2002-10-23 11:01 ` Takashi Iwai
2002-10-23 15:35 ` Osamu Tomita
2002-10-23 15:46 ` Takashi Iwai
2002-10-23 16:12 ` Osamu Tomita
2002-10-23 16:29 ` 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=s5hlm49r64k.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tomita@cinet.co.jp \
/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
Powered by JetHome