From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: (no subject) Date: Tue, 10 Jan 2006 18:07:36 +0100 Message-ID: References: <5C7B81E1-2824-427D-A874-A2504CE695EA@caiaq.de> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <5C7B81E1-2824-427D-A874-A2504CE695EA@caiaq.de> Sender: alsa-devel-admin@lists.sourceforge.net Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Daniel Mack Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Tue, 10 Jan 2006 14:24:52 +0100, Daniel Mack wrote: > > Dear ALSA people, > > I'm about to write an ALSA driver for a sound hardware we developed > and I'm wondering about how to tackle it. It's a USB2.0 hardware > which has sound input and output but also some controller elements > and MIDI jacks. I'd like to make the controllers accessible by linux' > input device interface. > > The audio part is - for good reasons - not USB class compliant, > and assuming that the usb folder in the driver tree only addresses > such devices, I pretty much guess this is not the point to start, > right? If it's not USB class compliant, you'll likely need to write a driver from scratch. But, unless the protocol detail is informed, I cannot tell what should be done... :) One troublesome stuff in USB audio is the data transfer. The usb-audio driver has a double-buffer to behave as a pseudo DMA. A similar trick would be required in your case, too. Takashi ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click