From: Marcel Holtmann <marcel@holtmann.org>
To: sreevani medhahal <sreevani.medhahal@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Patching 2.6.24
Date: Tue, 20 Jan 2009 16:23:00 +0100 [thread overview]
Message-ID: <3AD63C7D-CB02-4F0A-99A2-C38C84607FE9@holtmann.org> (raw)
In-Reply-To: <c2a31c480901200525q59b1ab02q554b54ceb4515e47@mail.gmail.com>
Hi Sreevani,
>>>> Is it possible to pull in just the Bluetooth changes in kernel
>>>> 2.6.27 to 2.6.24? Does it have any other dependencies? I am
>>>> trying to use 2.6.24 with BlueZ 4.17.
>>
>>> I have 2.6.24 down as release in January 2008. In Linus years this
>>> is an
>>> ancient kernel. Please just try to forward port any patches you have
>>> with 2.6.24 to 2.6.28 and use just a recent kernel. In the long-term
>>> this is the only way to keep you sane. Backporting changes to older
>>> kernels are always tricky. Sure it can be done, but nobody with a
>>> sane
>>> mind is doing it for free.
>
> after attempting to patching the 2.6.27 bluetooth changes on to
> 2.6.24[ie., drivers/bluetooth & net/bluetooth] & used the latest BlueZ
> . Tested the same with headsets for music & voice(worked fine),but the
> HID device didnt not work. We need to work with bluetooth on 2.6.24 as
> there is a dependancy on the others drivers present in kernel 2.6.24.
> For HID over Bluetooth to work does it have a dependancy on other
> kernel drivers/modules(apart from drivers/bluetooth & net/bluetooth
> modules). Any clues in this regard will be helpful.
let me be just quite blunt here. The assumption that you have to stay
with 2.6.24 is something you put yourself onto. In many cases it is as
simple to forward other drivers than insisting on backporting changes.
If you blindly copy the directories over you will end up in trouble.
It might work, but in many cases it will not since the subystems
Bluetooth depends on changed quite a bit during the last two years.
For HID, we have introduced a full blown HID subsystem and HID bus
during the time and Bluetooth depends on it. No idea why it doesn't
work, but as I said, backports are painful and introduce the same
risks of breaking things than moving forward with a more recent kernel.
Nobody says you should use bleeding edge 2.6.28, but at least one
kernel where the -stable maintainers still bother to update it.
Regards
Marcel
prev parent reply other threads:[~2009-01-20 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 7:30 Patching 2.6.24 Krishnan R
2009-01-16 1:39 ` 卞磊
2009-01-18 15:22 ` Marcel Holtmann
2009-01-18 15:20 ` Marcel Holtmann
2009-01-20 13:25 ` sreevani medhahal
2009-01-20 15:23 ` 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=3AD63C7D-CB02-4F0A-99A2-C38C84607FE9@holtmann.org \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sreevani.medhahal@gmail.com \
/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