Skip to contentSkip to conversation

UDA1341TS (iPAQ H3X00) sound driver for ALSA

DISCUSSION Kasparek Tomas 1 participant 2 messages Apr 10, 2002 – Apr 11, 2002 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 11 lines · Takashi Iwai
Quoted 10 lines
Quoted 8 lines
Quoted 1 line

I would prefer that the ALSA driver for the iPAQ have a

different name

Quoted 1 line

than the OSS driver for the iPAQ, since they have different

interfaces.

Quoted 1 line

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.

Quoted 7 lines

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