From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Youngwhan Kim <cs010101@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hi.. I want to change some part of kernel to other version
Date: Wed, 11 Feb 2009 11:39:35 -0500 [thread overview]
Message-ID: <20090211163935.GC15809@csclub.uwaterloo.ca> (raw)
In-Reply-To: <42AC222208AB49EE94C300A7AE597492@jamesnotebook>
On Wed, Feb 11, 2009 at 02:07:38PM +0900, Youngwhan Kim wrote:
> Hi~
> I'm doing some works. That I want to do is to move only two parts of kernel
> source. The version I'm working is kernel 2.6.10 and requested functions are
> included in kernel 2.6.27.x(or latest version).
> Example:
> I want to change "./net" and "./driver" from kernel 2.6.27.x to 2.6.10. Is
> that possible or not?
> And To do this, how do I do this?
Almost certainly the answer is no.
The drivers depend on the framework of the kernel, and you are look at
about 5 years of changes there.
Using 2.6.27 drivers with 2.6.10 kernel does not mean you are using a
2.6.10 kernel and hence get the benefit of any previous testing done on
that kernel.
You might be able backport some of the 2.6.27 drivers to work with
2.6.10 in a few cases, but many will be just too different, or will
depend on some subsystem that doesn't even exist in 2.6.10.
You are much better off porting whatever is keeping you at 2.6.10 to
2.6.27 and continuing from there. Just think of all the security
problems 2.6.10 has that has been fixed in newer kernels which no one is
likely to ever fix for 2.6.10 since nobody (except a few people) even
cares about 2.6.10 anymore. It is ancient history.
--
Len Sorensen
prev parent reply other threads:[~2009-02-11 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 5:07 Youngwhan Kim
2009-02-11 16:39 ` Lennart Sorensen [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=20090211163935.GC15809@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=cs010101@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®