ALSA driver architecture documentation?
Recently I started to collect some info on how to make a ALSA driver for the Digigram VXpocket V2. Digigram decided to provide information this PCMCIA card, on condition that a moderator is the single point of contact with Digigram.
A driver for the VXpocket should interface with the PCMCIA module and (most likely) the ALSA package. Info on how to make a PCMCIA driver easy to find. Description of layers and a well documented dummy driver. Alas I did not find much info in the ALSA structure. There is lots of source code and even a dummy driver, but completely uncommented. What seems to be documented is how to interface with ALSA, not how to write a ALSA driver. So is there more than "use the source"? :-)
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
Quoted 12 lines · Fred Jan Kraan
Recently I started to collect some info on how to make a ALSA driver for the Digigram VXpocket V2. Digigram decided to provide information this PCMCIA card, on condition that a moderator is the single point of contact with Digigram.
A driver for the VXpocket should interface with the PCMCIA module and (most likely) the ALSA package. Info on how to make a PCMCIA driver easy to find. Description of layers and a well documented dummy driver. Alas I did not find much info in the ALSA structure. There is lots of source code and even a dummy driver, but completely uncommented. What seems to be documented is how to interface with ALSA, not how to write a ALSA driver. So is there more than "use the source"? :-)
As far as I know, no.
If you find any more information, please add it to:
http://alsa.opensrc.org/index.php?page=WritingAnAlsaDriver
You can subscribe to alsa-devel for a year like I did, and pick up enough information to write a driver that works every second time it's loaded, with xruns when you even *think* about moving the mouse...
Mark
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
Quoted 4 lines
Recently I started to collect some info on how to make a ALSA driver for the Digigram VXpocket V2. Digigram decided to provide information this PCMCIA card, on condition that a moderator is the single point of contact with Digigram.
glad they came to their senses. the existence of the RME Hammerfall DSP driver for linux had nothing to do with it, i'm sure :)
Quoted 1 line
A driver for the VXpocket should interface with the PCMCIA module and
actuall, no. see below.
Quoted 6 lines
(most likely) the ALSA package. Info on how to make a PCMCIA driver easy to find. Description of layers and a well documented dummy driver. Alas I did not find much info in the ALSA structure. There is lots of source code and even a dummy driver, but completely uncommented. What seems to be documented is how to interface with ALSA, not how to write a ALSA driver. So is there more than "use the source"? :-)
the linux kernel makes pcmcia devices appear to be regular pci devices. there is no difference between writing a driver for a pcmcia device or a regular pci one. there are pcmcia utilities, its true, but the driver doesn't need to know about them. they can be used, for example, to autoload the driver when the device is inserted, etc.
because of this, "use the source for a similar-featured audio interface" is the best advice.
--p
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390