On Wed, 10 Apr 2002, Takashi Iwai 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.
Hmm ,I expected comments to driver quality and behavior, not to its
name :).
This is first public release of the driver. UDA1341TS specific part is
placed in "snd-uda1341" module and should be ARM-independent. The rest is
placed in snd-h3600-uda1341. There you could find H3x00 specific parts
same as a bit of SA1100 DMA code. The SA1100 DMA stuff could be moved into
independent module (like sa1100-audio in OSS), but it's just "few lines"
of code now.
The driver could be structuded better of course, but I don't have any
other ARM and/or UDA1341 device to be able to exactly select parts which
are common.
This first release is intended for basic functionality tests. I think,
there is enough time to discuss final names of modules.
Bye
--
Tomas Kasparek (sioux, xkaspa06)
tomas.kasparek@[seznam.cz,volny.cz]
[EMAIL PROTECTED]
student FIT VUT Brno
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
