linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim Gifford <maillist@jg555.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Prism54 -- error loading firmware
Date: Fri, 11 Mar 2005 16:04:04 +0000	[thread overview]
Message-ID: <4231C174.4000206@jg555.com> (raw)
In-Reply-To: <42313FDA.8050402@jg555.com>

Kay Sievers wrote:

>All three logs snippets seems to belong to a different driver loading
>sequence. :) Please make sure that they all fro the same events.
>
>You may try add some debug to the firmware loading script to see what
>the script is actually doing.
>
>And what does:
>  ls -l /lib/firmware/
>
>print?
>
>Kay
>
>  
>

(root@laptop)-(01:15 AM Fri Mar 11)-(/tmp)
# ls -l /lib/firmware
total 96
-rwxr-xr-x  1 root root 93996 2003-08-17 11:56 isl3890
(root@laptop)-(08:03 AM Fri Mar 11)-(/tmp)

-- 
----
Jim Gifford
maillist@jg555.com



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2005-03-11 16:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-11  6:51 Prism54 -- error loading firmware Jim Gifford
2005-03-11  7:38 ` Stefan Schweizer
2005-03-11  7:42 ` Jim Gifford
2005-03-11  8:12 ` Kay Sievers
2005-03-11  9:17 ` Jim Gifford
2005-03-11  9:40 ` Kay Sievers
2005-03-11 16:04 ` Jim Gifford [this message]
2005-03-11 18:36 ` Jim Gifford

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=4231C174.4000206@jg555.com \
    --to=maillist@jg555.com \
    --cc=linux-hotplug@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).