From: Takashi Iwai Subject: Re: Opening another audio driver from a driver Date: Tue, 09 Jan 2007 11:30:28 +0100 Message-ID: References: <45A3132B.8070608@gmail.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@lists.sourceforge.net Errors-To: alsa-devel-bounces@lists.sourceforge.net To: James Courtier-Dutton Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Tue, 9 Jan 2007 16:20:44 +1100, James Courtier-Dutton wrote: > > On 09/01/07, Himanshu Chauhan wrote: > > Hello all, > > > > I am working with the virtual device driver (dummy.c). Is it possible to > > route the audio data > > from the dummy driver to an actual hardware's device driver? For this, > > do I need to open the > > driver using syscalls? I don't want to make any changes on the other > > driver. I didn't see > > any exported functions in any of the actual drivers, so I cannot stack > > my driver on that. > > > > What should be done in this case? > > > > Thanks > > > > Regards > > --Himanshu > > > > I don't think you can do that. I also don't see why you would want to do it. > If you want to like the dummy one to the real one, why use the dummy > one in the first place. Just use the real one. In theory it's not impossible but very ugly and unrecommended at all. Anyway, user-space solution is more appropriate for such a virtual stuff, IMO. If apps require ALSA API, you can implement a plugin like jack or polypaudio. Takashi ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV