From: Takashi Iwai <tiwai@suse.de>
To: "Hicks, Jamey" <Jamey.Hicks@compaq.com>
Cc: Nicolas Pitre <nico@cam.org>,
Kasparek Tomas <xkaspa06@stud.fee.vutbr.cz>,
alsa-devel@lists.sourceforge.net,
Linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: RE: UDA1341TS (iPAQ H3X00) sound driver for ALSA
Date: Wed, 10 Apr 2002 17:09:54 +0200 [thread overview]
Message-ID: <a91kvu$tr3$2@main.gmane.org> (raw)
In-Reply-To: <D99C1FB421989A40818B6370E31870940283ADF3@tayexc19.americas.cpqcorp.net>
At Wed, 10 Apr 2002 09:55:43 -0400,
Hicks, Jamey <Jamey.Hicks@compaq.com> wrote:
>
> > -----Original Message-----
> > From: Nicolas Pitre [mailto:nico@cam.org]
> > Sent: Wednesday, April 10, 2002 9:47 AM
> > To: Hicks, Jamey
> > Cc: Kasparek Tomas; alsa-devel@lists.sourceforge.net;
> > Linux-arm-kernel@lists.arm.linux.org.uk
> > Subject: RE: UDA1341TS (iPAQ H3X00) sound driver for ALSA
> >
> >
> > On Wed, 10 Apr 2002, Hicks, Jamey wrote:
> >
> > >
> > > I would prefer that the ALSA driver for the iPAQ have a
> > different name
> > > than the OSS driver for the iPAQ, since they have different
> > interfaces.
> > > How about h3600-alsa?
> >
> > No. Please pick a relevant name. H3600 is not the only
> > device with an UDA1341 out there.
>
> The alsa driver mentioned is iPAQ specific. It would be useful to restructure it in the way the other SA11x0/UDA134x driver is structured.
the alsa modules have "snd-" prefix, so they don't conflict with
others anyway.
IMO, if the driver is iPAQ specific, i prefer a simple name such as
snd-ipaq or snd-ipaq-h3x00. if a part of the driver will be shared by
others, then we can split it to a lowlevel module with a proper device
name.
just my $0.02.
ciao,
Takashi
next parent reply other threads:[~2002-04-10 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D99C1FB421989A40818B6370E31870940283ADF3@tayexc19.americas.cpqcorp.net>
2002-04-10 15:09 ` Takashi Iwai [this message]
2002-04-12 17:35 ` UDA1341TS (iPAQ H3X00) sound driver for ALSA Russell King - ARM Linux
[not found] <s5hhemjlhdp.wl@alsa2.suse.de>
2002-04-10 16:45 ` Kasparek Tomas
2002-04-11 9:21 ` Kasparek Tomas
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='a91kvu$tr3$2@main.gmane.org' \
--to=tiwai@suse.de \
--cc=Jamey.Hicks@compaq.com \
--cc=Linux-arm-kernel@lists.arm.linux.org.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=nico@cam.org \
--cc=xkaspa06@stud.fee.vutbr.cz \
/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.