public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Alex Holland <ah160@student.cs.york.ac.uk>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Compile bluez-bluefw-1.0 fails
Date: Mon, 19 Apr 2004 18:12:29 +0200	[thread overview]
Message-ID: <1082391148.4403.57.camel@pegasus> (raw)
In-Reply-To: <200404191639.48612.ah160@student.cs.york.ac.uk>

Hi Alex,

> > check the path for the firmware files in the firmware.agent script.
> > Is the script is executable? Is /sys mounted? What are the
> > permissions of your firmware files?
> 
> firmware.agent is executable. The firmware permissions are as follows:
> 
> -rw-r--r--    1 root     root       114688 Apr 19 12:29 BCM2033-FW.bin
> -rw-r--r--    1 root     root         3245 Apr 19 12:29 BCM2033-MD.hex
> 
> This should be okay, I'd imagine - no need to execute or write to them. 
> For the other questions, I've attached firmware.agent, but everything 
> looks correct to me.
> 
> > You need CONFIG_FW_LOADER, but this should be done automaticly by the
> > bcm203x driver and lsmod must show you a firmware_class module.
> 
> Yup, this seems to be working; lsmod has the following:
> 
> firmware_class          7616  1 bcm203x

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.

Regards

Marcel




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

  reply	other threads:[~2004-04-19 16:12 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 [this message]
2004-04-19 17:22                   ` Alex Holland
2004-04-19 17:52                     ` Simone Gotti
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=1082391148.4403.57.camel@pegasus \
    --to=marcel@holtmann.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox