From: "Hicks, Jamey" <Jamey.Hicks@compaq.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
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: UDA1341TS (iPAQ H3X00) sound driver for ALSA
Date: Fri, 12 Apr 2002 13:39:30 -0400 [thread overview]
Message-ID: <a9766p$ja1$2@main.gmane.org> (raw)
> -----Original Message-----
> From: Russell King - ARM Linux [mailto:linux@arm.linux.org.uk]
> Sent: Friday, April 12, 2002 1:36 PM
> To: Hicks, Jamey
> Cc: Nicolas Pitre; 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, Apr 10, 2002 at 09:55:43AM -0400, Hicks, Jamey wrote:
> > > -----Original Message-----
> > > From: Nicolas Pitre [mailto:nico@cam.org]
> > >
> > > 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.
>
> I agree with Nico. Nico is objecting to it being called
> *h3600* when it
> is for all iPAQs, ie, H3600, H3100, H3800.
>
If that is the case, I am open to suggestions for the name should be, bearing in mind that not all iPAQ devices from Compaq are handheld devices. h3xxx seems like a good choice at the moment, but I have a feeling we'll be sharing some of the same drivers with h4xxx in the near future.
Jamey
next reply other threads:[~2002-04-12 17:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-12 17:39 Hicks, Jamey [this message]
[not found] <D99C1FB421989A40818B6370E31870940283AE36@tayexc19.americas.cpqcorp.net>
2002-04-12 18:39 ` UDA1341TS (iPAQ H3X00) sound driver for ALSA Kasparek Tomas
[not found] ` <Pine.BSF.4.44.0204122027100.10809-100000@fest.stud.fee.vutbr.cz>
2002-04-12 18:56 ` Russell King - ARM Linux
[not found] <D99C1FB421989A40818B6370E31870940283ADF3@tayexc19.americas.cpqcorp.net>
2002-04-12 17:35 ` Russell King - ARM Linux
-- strict thread matches above, loose matches on Subject: below --
2002-04-10 13:55 Hicks, Jamey
[not found] <D99C1FB421989A40818B6370E31870940283ADF0@tayexc19.americas.cpqcorp.net>
2002-04-10 13:47 ` Nicolas Pitre
2002-04-10 13:39 Hicks, Jamey
2002-04-10 10:32 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='a9766p$ja1$2@main.gmane.org' \
--to=jamey.hicks@compaq.com \
--cc=Linux-arm-kernel@lists.arm.linux.org.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=linux@arm.linux.org.uk \
--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.