From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: snd-usb-usx2y 0.8.7 hwdep pcm oopses! Date: Wed, 15 Dec 2004 15:38:52 +0100 Message-ID: References: <64648.195.245.190.93.1103017646.squirrel@195.245.190.93> <46792.195.245.190.94.1103119505.squirrel@195.245.190.94> <200412151532.35006.annabellesgarden@yahoo.de> Mime-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <200412151532.35006.annabellesgarden@yahoo.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: Karsten Wiese Cc: Rui Nuno Capela , alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Wed, 15 Dec 2004 15:32:34 +0100, Karsten Wiese wrote: > > > You can get the card number from ctl or pcm instance. > > Check snd_*_get_card() functions. > > > We haven't any of those yet, as hwdep device is the first one to be opened. hwdep has also one - snd_hwdep_info_get_card(). > So we could change jackd's usx2y driver's parameters a little: > $ jackd -dusx2y -c1 > or > $ jackd -dusx2y --card 1 > in the jackd usx2y driver we would sprintf the real alsa devicenames like this: > char hwdep_devicename[8]; > char pcm_devicename[8]; > int card; //holds card nr parameter > > sprintf(hwdep_devicename, "hw:%i,1", card); > sprintf(pcm_devicename, "hw:%i,2", card); > > thus we'd hide away the complications from the commandline. Yes, this looks much easier (also good for future changes of hwdep/pcm assignment). Takashi ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/