Edd Dumbill <[EMAIL PROTECTED]> writes:
> My current thinking is to make two packages, bluez-bluefw and
> bluez-bluefw-firmware. The latter would have to go into non-free, and
> the former into contrib as it requires a non-free package to function.
>
> Does this sound OK?
It is most correct, ye
Edd Dumbill <[EMAIL PROTECTED]> writes:
> My current thinking is to make two packages, bluez-bluefw and
> bluez-bluefw-firmware. The latter would have to go into non-free, and
> the former into contrib as it requires a non-free package to function.
>
> Does this sound OK?
It is most correct, y
Hi Edd,
Edd Dumbill wrote:
> I'm looking at packaging bluez-bluefw, a firmware loader for USB
> Bluetooth devices using the Broadcom 2033 chipset. This consists of two
> components:
>
> (a) GPL'd software for loading the firmware
> (b) The binary-only firmware itself (Broadcom have approved its
Hi there
I'm looking at packaging bluez-bluefw, a firmware loader for USB
Bluetooth devices using the Broadcom 2033 chipset. This consists of two
components:
(a) GPL'd software for loading the firmware
(b) The binary-only firmware itself (Broadcom have approved its
distribution)
My current thin
Hi Edd,
Edd Dumbill wrote:
> I'm looking at packaging bluez-bluefw, a firmware loader for USB
> Bluetooth devices using the Broadcom 2033 chipset. This consists of two
> components:
>
> (a) GPL'd software for loading the firmware
> (b) The binary-only firmware itself (Broadcom have approved its
Hi there
I'm looking at packaging bluez-bluefw, a firmware loader for USB
Bluetooth devices using the Broadcom 2033 chipset. This consists of two
components:
(a) GPL'd software for loading the firmware
(b) The binary-only firmware itself (Broadcom have approved its
distribution)
My current thi
6 matches
Mail list logo
