Re: [Bluez-devel] Patch mh3

Mats Erik Andersson
2007-10-01T16:55:52Z

m=E5n 2007-10-01 klockan 16:12 +0200 skrev Olivier Le Pogam:
> Hello,
> =

> I have a 2.6.22.12 kernel (ubuntu gutsy gibbon) and when I want to apply =
the =

> mh3 kernel patch (dry run for now) it seems there are some modifications =

> which have already been applied (partially ?) in hci_core.h, rfcomm.h, sc=
o.h
> =

Do a manual auditing of those patch bits that fail: read the
corresponding source in your kernel-source-2.6.22.12 and cross check
aginst the suggested amending from the patch file. Remove from the
patch file those parts that the Ubuntu maintainer already applied,
and keep the new additions. Then perform a final (or intermediary)
dry-runs with the patch command to check that things apply cleanly.
Of course, you have to use your own wit to go with the Bluez maintainers
suggestion against the decision of the Ubuntu crew, but the time will
be well invested. I used this technique to patch my own kernel
sources for Debian Etch 2.6.18 and I did eliminate some suboptimal
behaviour of Bluez in doing so.

In your case, disect the following contributions:

> patching file linux-source-2.6.22/include/net/bluetooth/rfcomm.h
> patching file linux-source-2.6.22/Makefile
> patching file linux-source-2.6.22/net/bluetooth/hci_conn.c
> patching file linux-source-2.6.22/net/bluetooth/hci_core.c
> patching file linux-source-2.6.22/net/bluetooth/hci_event.c

since they only produced rejects.

Good luck on your venture

Mats Erik Andersson

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.