From: Martin Langer <martin-langer@gmx.de>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] miroSOUND PCM12 driver
Date: Thu, 17 Mar 2005 00:48:18 +0100 [thread overview]
Message-ID: <20050316234818.GA2777@tuba> (raw)
In-Reply-To: <Pine.HPX.4.33n.0503161138550.28424-100000@studcom.urz.uni-halle.de>
[-- Attachment #1: Type: text/plain, Size: 2585 bytes --]
On Wed, Mar 16, 2005 at 11:51:46AM +0100, Clemens Ladisch wrote:
> Martin Langer wrote:
> > The tenth birthday of this card is coming soon and now it's time to get
> > an ALSA driver for the miroSOUND PCM12 :)
The new miro driver patch version 0.6 is attached.
>
> > +++ alsa-driver/isa/opti9xx/Makefile Fri Mar 11 18:51:05 2005
> > +obj-$(CONFIG_SND_MIRO) += snd-miro.o snd-opti92x-cs4231.o
>
> Is there any reason for the dependency on the snd-opti92x-cs4231
> driver?
No, it's rubbish. I've removed it.
> > MODULE_SUPPORTED_DEVICE("{{miroSOUND,PCM1 pro}, "
> > "{miroSOUND,PCM12}, "
> > "{miroSOUND,PCM20 Radio}}");
>
> The first entry in each pair should be the vendor name.
fixed.
> > static int wss; /* unknown range */
> > static int ide; /* unknown range */
>
> "unknown"? :-)
"wss" is only for PCM1 which I can't test with my PCM12.
"ide" isn't documented and I haven't tried ide out - it's postponed to
later.
But perhaps 0 and 1 are the unknown values. Hmmm, there is still a
smell of uncertainty in the air...
> > int snd_miro_mixer(miro_t * miro)
> > ...
> > switch (miro->hardware) {
> > case OPTi9XX_HW_82C924:
> > strcpy(card->mixername, "ACI & OPTi924");
> > case OPTi9XX_HW_82C929:
> > strcpy(card->mixername, "ACI & OPTi929");
> > default:
> > strcpy(card->mixername, "ACI & OPTi9xx");
> > }
>
> The default case cannot happen (bwahaha!), so it might make sense to
> put a snd_BUG() in there.
good point. fixed.
> > - OPL4 support is still missing, because I'm still waiting for response
> > of my broken OPL4 chip. :(
>
> Is it broken with the snd-opti92x-cs4231 driver, too?
Yep, it's even broken with Win2000.
> > - I never saw any docs about the cards. All knowledge is taken from ACI
> > driver (OSS) and OPTi9xx (ALSA) drivers.
>
> There are OPTi manuals on the ALSA FTP server.
I wasn't precise here. I was looking for ACI or Miro specific documents.
E.g. the OSS driver has no real equalizer implementation. I hope it's
handled correct now, because it's still untested PCM20 stuff.
OTOH, I haven't had a hole of knowledge in the OPTi part. There was no
reason for looking into the OPTi specifications, the ALSA opti driver
had all things inside (at least for me).
BTW, I just asked google and I've found two other intersting documents
for addition to the ALSA ftp area:
Opti929:
http://ftp.cis.nctu.edu.tw/data/Multimedia/SoundCard/OPTi/82c929/db013_10.pdf
OPL4:
http://ftp.funet.fi/pub/msx/docs/datasheets/opl4.pdf
bye,
martin
[-- Attachment #2: miro-0.6.patch.bz2 --]
[-- Type: application/octet-stream, Size: 8911 bytes --]
next prev parent reply other threads:[~2005-03-16 23:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-13 10:33 [PATCH] miroSOUND PCM12 driver Martin Langer
2005-03-16 10:51 ` Clemens Ladisch
2005-03-16 23:48 ` Martin Langer [this message]
2005-03-18 8:51 ` Clemens Ladisch
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=20050316234818.GA2777@tuba \
--to=martin-langer@gmx.de \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
/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.