Bug#400318: include bluez patches in the kernel
On Mon, Nov 27, 2006 at 09:38:04AM +0100, Jordi Pujol wrote:
> Sorry, I was not correctly explained,
> I don't suggest a backport, I am talking about the latest version
> 2.6.18-3,
btw, please include the version of the package when talking about a
specific release - 2.6.18-3 is enough in this case because the only
released 2.6.18-3 ABI is 2.6.18-6. In general, the ABI name is
insufficient for narrowing down a version.
For more info, see: http://wiki.debian.org/DebianKernelABIChanges
You can use dpkg -l to see specific versions.
(not a big deal for this one, just fyi for next time)
> it
> is released a few days ago, and I wish to ask about including the bluez
> patches in the new released packages of 2.6.18 or later,
Its much easier to convince us to take patches that have already gone
into Linus' tree - if these have gone into Linus' tree, a pointer to
them would be useful. If they haven't gone into Linus' tree yet, the
reason might be that the developers believe they are too experimental
or that upstream has chosen not to accept them for some reason,
which are very good reasons for Debian to not pick them up yet.
> those patches contains important improvements for the bluetooth networking
> protocol and are a requisite to put in working order the bluetooth system
>
> I have tried to communicate with bluetooth devices without the patches and it
> is not practical, allways I should compile a new kernel with the patch
You'll have better luck if you provide pointers to upstream patches
and more precise details about what they do (add support for device
such-and-such, fix bug in networking driver that breaks foo, etc).
--
dann frazier
Reply to: