RE: [Bluez-devel] Alignment issue

[David Woodhouse <dwmw2@infradead.org>]

On Thu, 2004-08-12 at 13:49 +0200, Marcel Holtmann wrote:
> is it worth to include such a patch and make it optional?

Yes, I suspect it would. I'll have a look at it when I get a spare
moment and offer you a patch.

> The loading of the firmware for the 3Com PCMCIA card and the BlueFRITZ!
> USB dongle are done through request_firmware(). The Broadcom based
> dongles are an exception. I personal prefer to use the bcm203x kernel
> driver for loading the firmware, but this is a 2.6 only feature.

2.6-only is _fine_. Isn't 2.4 dead yet? I'll make sure we build the
bcm203x driver and just drop bluez-bluefw.

> The bluez-firmware package only contains the Broadcom firmware files and
> it will install them by default under /lib/firmware. You need a modified
> firmware.agent script that also looks for firmware files in that place.
> We agreed on that path, but this change is not upstream at the moment.
> Check the Debian packages for an example of a modified script.

The standard place to put firmware files is /usr/lib/hotplug/firmware
isn't it? Is there a reason for using a different path? Can you
elaborate on the meaning of 'We' in the above context?

> I think it is too late for Debian Sarge and SuSE 9.2 and maybe even for
> Fedora Core 3, but actually we should really talk about it.

OK... well what I've done is split into four separate init scripts, each
of which can be separately enabled or disabled with chkconfig or
whichever pretty tool the user likes for selecting which services are
run in each runlevel. I have removed dund, hidd and pand into their own
scripts. As I said, I'd like to remove the need for running pand as a
daemon like that anyway -- it should be handled by the network
ifup/ifdown scripts like pppd is. I have never really looked at dund but
I suspect the same goes for that. 

-- 
dwmw2