From: Simone Gotti <simone.gotti@email.it>
To: bluez-users@lists.sourceforge.net
Cc: Alex Holland <ah160@student.cs.york.ac.uk>
Subject: Re: [Bluez-users] Compile bluez-bluefw-1.0 fails
Date: Mon, 19 Apr 2004 19:52:11 +0200 [thread overview]
Message-ID: <200404191952.11018.simone.gotti@email.it> (raw)
In-Reply-To: <200404191822.46586.ah160@student.cs.york.ac.uk>
Hi,
On Monday 19 April 2004 19:22, Alex Holland wrote:
> On Monday 19 Apr 2004 17:12, Marcel Holtmann wrote:
> > so far so good. Everything seems to look fine, but actually the
> > bcm203x driver can't load the BCM2033-MD.hex firmware file from the
> > userspace. Add some debugging lines to firmware.agent to see if it
> > got really called by the hotplug system.
>
> I wasn't quite sure how to do this, but I tried adding this to the start
> of the firmware.agent file (after the header, before the code):
>
> echo "Now in firmware.agent"
>
> This didn't appear during the boot sequence, and doesn't appear in
> dmesg, so I assume the firmware.agent isn't being called.
>
> Any suggestions, or is this now a Hotplug problem? If it is, could you
> tell me how to phrase it as a question for the Hotplug mailing list?
>
> Alex Holland
In /etc/hotplug/firmware.agent there's a commented line like this
# DEBUG=yes export DEBUG
remove the # and you'll see a lot of debug informations.
Bye!
--
Simone Gotti
<simone.gotti@email.it>
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-04-19 17:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-18 21:21 [Bluez-users] Compile bluez-bluefw-1.0 fails Dirk Vornheder
2004-04-18 21:55 ` Marcel Holtmann
2004-04-19 8:35 ` Alex Holland
2004-04-19 10:23 ` Marcel Holtmann
2004-04-19 13:19 ` Alex Holland
2004-04-19 13:30 ` Marcel Holtmann
2004-04-19 13:41 ` Alex Holland
2004-04-19 13:54 ` Marcel Holtmann
2004-04-19 15:39 ` Alex Holland
2004-04-19 16:12 ` Marcel Holtmann
2004-04-19 17:22 ` Alex Holland
2004-04-19 17:52 ` Simone Gotti [this message]
2004-04-19 20:21 ` Alex Holland
2004-04-20 9:28 ` Alex Holland
2004-04-20 11:56 ` Marcel Holtmann
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=200404191952.11018.simone.gotti@email.it \
--to=simone.gotti@email.it \
--cc=ah160@student.cs.york.ac.uk \
--cc=bluez-users@lists.sourceforge.net \
/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.