From: Giuliano Pochini <pochini@shiny.it>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: Alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Error: firmware not found
Date: Mon, 24 Jan 2005 09:41:43 +0100 (CET) [thread overview]
Message-ID: <XFMail.20050124094143.pochini@shiny.it> (raw)
In-Reply-To: <1106447855.2368.29.camel@cmn37.stanford.edu>
On 23-Jan-2005 Fernando Lopez-Lezcano wrote:
>> - In /etc/hotplug/pci.agent:pci_map_modules() at line 123 I had to remove
>> the break, otherwise the loop stops as soon as it finds the first matching
>> PCI ID. This is not good because some cards (in my case the Layla3G and the
>> Gina3G) have the same PCI card, but different external module.
>
> Could you expand on this? What is the result of using an unmodified
> hotplug? Wrong firmware loaded? (fc3 ships with hotplug-2004_04_01-8.1
> which I presume would have the problem)
I don't know if there are other devices that have the same PCI card
and different "box" (not necessarily an audio device). The Gina3G
and Layla3G have different driver, but same PCI card. For example I
have a Gina3G. If in /lib/modules/x.x.x/modules.pcimap the Layla3G
module is listed before the Gina3G the original hotplug script loads
snd-layla3g *only* which, obviously, fails.
With that change pci_map_modules() return all matching modules, so
it fixes the problem. BUT, there is a comment before that function
that says it returns "ONE" (all uppercase) module only. It means
it was done on purpose, but I can't see why.
--
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
next prev parent reply other threads:[~2005-01-24 8:41 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 [this message]
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
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=XFMail.20050124094143.pochini@shiny.it \
--to=pochini@shiny.it \
--cc=alsa-devel@lists.sourceforge.net \
--cc=nando@ccrma.Stanford.EDU \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.