All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: Giuliano Pochini <pochini@shiny.it>,
	Alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Error: firmware not found
Date: Mon, 24 Jan 2005 11:06:24 +0100	[thread overview]
Message-ID: <s5hbrbf2lb3.wl@alsa2.suse.de> (raw)
In-Reply-To: <1106447855.2368.29.camel@cmn37.stanford.edu>

At 22 Jan 2005 18:37:36 -0800,
Fernando Lopez-Lezcano wrote:
> 
> On Sat, 2005-01-22 at 02:37, Giuliano Pochini wrote:
> > Since my echoaudio driver is the first driver which is using the new
> > "standard" firmware loader, I can anticipate what you have to expect when
> > other drivers will be converted to that interface: people will not be able
> > to make them work.
> > 
> > I don't know what distributions are doing, but it is causing users (and, in
> > turn, to me) a lot of trouble. I located these main problems in the latest
> > hotplug scripts (hotplug-2004_09_23):
> > 
> > - /etc/hotplug/firmware.agent sets FIRMWARE_DIR=/lib/firmware, but
> > alsa-firmware install the files in /usr/lib/hotplug/firmware .
> 
> Yes, I noticed this and I'm packaging for fc3 / Planet CCRMA (which uses
> /lib/firmware) by setting that directory explicitly in the alsa-firmware
> configure step. I have at least two users that have successfully used
> echoaudio cards. 

IMO, it's a bug of hotplug if it doesn't look at the old path,
/usr/lib/hotplug/firmware.  Of course, passing the proper path to
configure script would be the best solution, though.


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

  parent reply	other threads:[~2005-01-24 10:06 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 [this message]
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=s5hbrbf2lb3.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=nando@ccrma.Stanford.EDU \
    --cc=pochini@shiny.it \
    /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.