From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Debian testing required: bcm203x firmware
Date: Fri, 12 Nov 2004 15:17:18 +0100 [thread overview]
Message-ID: <1100269038.7215.6.camel@pegasus> (raw)
In-Reply-To: <1100267525.8785.39.camel@saag>
Hi Edd,
> > the firmware files are in the wrong place. You are using the old
> > directory. They must be under /lib/firmware/.
>
> Ah yes, I see that now.
>
> I still tend to think it'd be better to have everything
> under /usr/lib/hotplug/firmware, but I understand your reasons, so I'll
> change this back.
we agreed on this change some time ago. It is official now and Fedora
Core 3 allows only this path while Debian and SuSE also accepts firmware
files in the old one.
> > Actually I would prefer to have bluez-bcm203x and bluez-firmware,
> > because I try to get the AVM and 3Com firmware also into this package.
> > This also avoids that people install bluez-bcm203x for their 2.6 kernel
> > even if they don't need it. The naming leads to that.
>
> OK, I didn't know you planned other firmwares. I have no problem with
> doing that rename.
I must resolve the legal issues first, but my plan is to keep all
firmwares in one place.
> > And btw what does it take to get a virtual packages called bluez that
> > installs all the needed BlueZ packages?
>
> I can do that too. Should it include the bcm203x firmware loader or
> not?
Please don't and also please don't suggest the installation of it. This
bcm203x tool is a relict for some people that are stuck to 2.4 and the
old Broadcom chips. Actually it seems that Broadcom gave up this chips
and the newer ones are storing the firmware in flash. Maybe you can pop
up a warning message when they install bluez-bcm203x like the lm-sensors
packages do.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users/listinfo/bluez-users
prev parent reply other threads:[~2004-11-12 14:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-12 11:57 [Bluez-users] Debian testing required: bcm203x firmware Edd Dumbill
2004-11-12 12:13 ` Marcel Holtmann
2004-11-12 13:52 ` Edd Dumbill
2004-11-12 14:10 ` Edd Dumbill
2004-11-12 17:55 ` Marcel Holtmann
2004-11-12 18:52 ` Edd Dumbill
2004-11-12 19:01 ` Marcel Holtmann
2004-11-12 22:52 ` Edd Dumbill
2004-11-13 0:37 ` Marcel Holtmann
2004-11-12 14:17 ` Marcel Holtmann [this message]
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=1100269038.7215.6.camel@pegasus \
--to=marcel@holtmann.org \
--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