From: Alex Holland <ah160@student.cs.york.ac.uk>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Compile bluez-bluefw-1.0 fails
References: <200404182321.55431.dvornheder@t-online.de> <200404191639.48612.ah160@student.cs.york.ac.uk> <1082391148.4403.57.camel@pegasus>
In-Reply-To: <1082391148.4403.57.camel@pegasus>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Message-Id: <200404191822.46586.ah160@student.cs.york.ac.uk>
Sender: bluez-users-admin@lists.sourceforge.net
Errors-To: bluez-users-admin@lists.sourceforge.net
Date: Mon, 19 Apr 2004 18:22:46 +0100

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


-------------------------------------------------------
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