From: Takashi Iwai <tiwai@suse.de>
To: Giuliano Pochini <pochini@shiny.it>
Cc: Alsa-devel <alsa-devel@lists.sourceforge.net>,
Thierry Vignaud <tvignaud@mandrakesoft.com>
Subject: Re: Error: firmware not found
Date: Thu, 27 Jan 2005 11:10:24 +0100 [thread overview]
Message-ID: <s5hpszrrxm7.wl@alsa2.suse.de> (raw)
In-Reply-To: <XFMail.20050126182942.pochini@shiny.it>
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
next prev parent reply other threads:[~2005-01-27 10:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-22 10:37 Error: firmware not found Giuliano Pochini
2005-01-23 2:37 ` Fernando Lopez-Lezcano
2005-01-24 8:41 ` Giuliano Pochini
2005-01-24 10:06 ` Takashi Iwai
2005-01-24 21:55 ` Fernando Lopez-Lezcano
2005-01-24 11:43 ` Thierry Vignaud
2005-01-24 11:44 ` Thierry Vignaud
2005-01-25 8:15 ` Giuliano Pochini
2005-01-25 8:22 ` Giuliano Pochini
2005-01-24 11:52 ` Thierry Vignaud
2005-01-25 8:32 ` Giuliano Pochini
2005-01-25 13:19 ` Thierry Vignaud
2005-01-25 13:57 ` Giuliano Pochini
2005-01-25 15:06 ` Takashi Iwai
2005-01-25 15:35 ` Giuliano Pochini
2005-01-25 15:39 ` Takashi Iwai
2005-01-26 17:29 ` Giuliano Pochini
2005-01-27 10:10 ` Takashi Iwai [this message]
2005-01-28 16:34 ` Giuliano Pochini
2005-01-28 16:41 ` Thierry Vignaud
2005-01-28 16:43 ` Giuliano Pochini
2005-01-29 15:46 ` Giuliano Pochini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5hpszrrxm7.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=pochini@shiny.it \
--cc=tvignaud@mandrakesoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox