From: Felix Fietkau <nbd@openwrt.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Forward porting 2.4 driver
Date: Mon, 1 Feb 2010 02:05:33 +0000 (UTC) [thread overview]
Message-ID: <loom.20100201T025725-124@post.gmane.org> (raw)
In-Reply-To: 4B634540.9070306@gawab.com
Justin Madru <jdm64 <at> gawab.com> writes:
> 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.
Support for these chips is being worked on in the OpenWrt project.
We have some work in progress code based on Linux 2.6.32. It will be submitted
upstream when it's complete. Feel free to help us complete it, if you want to ;)
I know the code that Ralink provides for these chips, and I'd say any time spent
on changing it or using it for any purpose other than deriving hardware
information is a complete waste of time.
- Felix
prev parent reply other threads:[~2010-02-01 4:25 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
2010-02-01 6:27 ` Willy Tarreau
2010-02-01 2:05 ` Felix Fietkau [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=loom.20100201T025725-124@post.gmane.org \
--to=nbd@openwrt.org \
--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