Re: Error: firmware not found

[Giuliano Pochini <pochini@shiny.it>]

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...

Btw, I don't see what is the problem of having two drivers
for the same ID. Does it break some rule ?  Actually, the
problem is there are two different (though similar) devices
with the same IDs :-/


--
Giuliano.


-------------------------------------------------------
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