From: Justin Madru <jdm64@gawab.com>
To: Willy Tarreau <w@1wt.eu>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Forward porting 2.4 driver
Date: Sun, 31 Jan 2010 20:05:54 -0800 [thread overview]
Message-ID: <4B665322.2060005@gawab.com> (raw)
In-Reply-To: <20100129203613.GF27907@1wt.eu>
On 01/29/2010 12:36 PM, Willy Tarreau wrote:
> Hello,
>
> On Fri, Jan 29, 2010 at 12:29:52PM -0800, Justin Madru wrote:
>
>> 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?
>>
> it will very likely work even without any change. I have some drivers
> in my private tree which were written for various versions between
> 2.4.23 and 2.4.33, most of which apply without problem. In general
> the only conflicts you can get are in Config.in or the makefiles
> where the patch wants to add one line to enable the driver, because
> the context might have changed. But that's really obvious to fix.
>
>
>> The CPU and wireless card are based on the Ralink 2880/2860 or something
>> like that.
>>
> Well, if you have the 2.4 driver and the hardware, it could also be
> a nice exercise to try to port it to 2.6. It's not necessarily that
> much complicated, as there are several drivers which are compatible
> with both 2.4 and 2.6. They generally rely on some #define to rename
> some struct members or use different macros depending on versions.
>
> Regards,
> Willy
>
>
>
Well, it's good that the driver might easily be updated to the latest 2.4.
I did a diff of the source code that was provided against 2.6.30.
Unfortunately, it looks like there's been more changes to the code than
simply adding drivers. Updates all across the tree have been made, some
minor that would be an easy merge. But some seem to be more involved
changes. Any suggestions on merging the code?
Justin
next prev parent reply other threads:[~2010-02-01 4:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 20:29 Forward porting 2.4 driver Justin Madru
2010-01-29 20:36 ` Willy Tarreau
2010-02-01 4:05 ` Justin Madru [this message]
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=4B665322.2060005@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