Re: Error: firmware not found

[Takashi Iwai <tiwai@suse.de>]

At Tue, 25 Jan 2005 16:35:46 +0100 (CET),
Giuliano Pochini wrote:
> 
> On Tue, 25 Jan 2005, Takashi Iwai wrote:
> 
> > > No, it isn't, because those devices use the same PCI card, that is
> > > the kernel reports the same PCI ID/subID's. The driver has to load
> > > the firmware and then it asks the DSP what (if any) external box is
> > > attached. If it is the wrong driver it exits with -ENODEV.
> >
> > Hmm, but having two drivers for the identical PCI ID/subID isn't
> > good.  Isn't it possible to determine in the driver level which model
> > it is?
> 
> Nope. They *are* the same card. Only the DSP knows what box is attached.
> 
> The generic driver by Echoaudio does:
> 
> Load the DSP loader
> Load the DSP code of the Layla3G
> Is the attached box a Layla3G ?
> 	no:
> 	reset DSP
> 	Load the DSP code of the Gina3G
> Load the ASIC code
> 
> 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.


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