From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: Error: firmware not found Date: Thu, 27 Jan 2005 11:10:24 +0100 Message-ID: References: Mime-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: 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: Giuliano Pochini Cc: Alsa-devel , Thierry Vignaud List-Id: alsa-devel@alsa-project.org At Wed, 26 Jan 2005 18:29:42 +0100 (CET), Giuliano Pochini wrote: > > > On 25-Jan-2005 Takashi Iwai wrote: > > >> The ALSA driver exits if the box is wrong. The obvious solution is to do > >> that same procedure in the ALSA driver, but it implies I have to replace > >> all references to card capabilites (# of channels, etc...) with variables. > >> Those vars never change their values after init. Furthermore a few > >> functions are different. I worked a lot to do as much choices as possible > >> at compile time. Currently they're all constants. > > > > Well, but if it's the only method to initialize the stuff > > automatically, the procedure above seems to be the only to go. > > > > This is no urgent issue, but should be fixed before submitting to > > linux kernel. > > *sigh* I'll do some tests in the weekend to see how much > is the impact of making all that stuff variable in terms > of binary size and mess in the sources. Maybe I can fix > it with some not very nice #define... [Looks like my last post didn't come out due to system problems, so I rewriting again the same thing] You don't have to use variables (although it's better for a long term). The problem is that you have two modules. Combining them to a single module wouldn't be too hard. For example, compile layla and gina separately, but without module_init and module_exit. Create a skeleton PCI entry which calls layla's and gina's driver callback functions. The reference to module options should be fixed, too. > > Btw, I don't see what is the problem of having two drivers > for the same ID. Does it break some rule ? We may have, but we can't load them at the same time. It's a tacit understanding that the drivers with the same id conflict. Takashi ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl