public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
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
Date: Mon, 19 Apr 2004 16:39:48 +0100	[thread overview]
Message-ID: <200404191639.48612.ah160@student.cs.york.ac.uk> (raw)
In-Reply-To: <1082382899.4403.46.camel@pegasus>

[-- Attachment #1: Type: text/plain, Size: 863 bytes --]

On Monday 19 Apr 2004 14:54, Marcel Holtmann wrote:

> 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

Thanks,

Alex Holland

[-- Attachment #2: firmware.agent --]
[-- Type: application/x-shellscript, Size: 1129 bytes --]

  reply	other threads:[~2004-04-19 15:39 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 [this message]
2004-04-19 16:12                 ` Marcel Holtmann
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=200404191639.48612.ah160@student.cs.york.ac.uk \
    --to=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