From: Justin Madru <jdm64@gawab.com>
To: lkml <linux-kernel@vger.kernel.org>, Willy Tarreau <w@1wt.eu>
Subject: Forward porting 2.4 driver
Date: Fri, 29 Jan 2010 12:29:52 -0800 [thread overview]
Message-ID: <4B634540.9070306@gawab.com> (raw)
I have this Belkin router with the default firmware running 2.4.30.
Belkin provided the source code as specified by the GPL. I was wondering
how hard it would be to upgrade the kernel from 2.4.30 to 2.4.37.7. I
know that 2.6 would be extremely hard because the driver model has
changed so much. But, what changes happened between .30 and .37 that
would make it difficult to upgrade the code? Did the driver model or
other drastic changes happen? Could I just do a file diff; import the
new files Belkin added and update the make files and kconfig?
The CPU and wireless card are based on the Ralink 2880/2860 or something
like that.
Justin Madru
next reply other threads:[~2010-01-29 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 20:29 Justin Madru [this message]
2010-01-29 20:36 ` Forward porting 2.4 driver Willy Tarreau
2010-02-01 4:05 ` Justin Madru
2010-02-01 6:27 ` Willy Tarreau
2010-02-01 2:05 ` Felix Fietkau
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=4B634540.9070306@gawab.com \
--to=jdm64@gawab.com \
--cc=linux-kernel@vger.kernel.org \
--cc=w@1wt.eu \
/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