Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Henk <Henk.Vergonet@gmail.com>
To: Waldemar Brodkorb <wbx@openbsd-geek.de>
Cc: linux-mips@linux-mips.org
Subject: Re: Porting mips based routers
Date: Mon, 18 Apr 2005 14:48:09 +0200	[thread overview]
Message-ID: <20050418124809.GA27967@god.dyndns.org> (raw)
In-Reply-To: <20050415065558.GD25962@openbsd-geek.de>

On Fri, Apr 15, 2005 at 08:55:58AM +0200, Waldemar Brodkorb wrote:
> > I will try to see if I can get a list of 2.4 source files that need to
> > be contributed back to linux-mips.org, with a quick initial proposal on
> > how to migrate this to the 2.6 kernel tree.

See section 1.3 on the wiki page:
http://openwrt.org/Kernel26Firmware
Feel free to comment here on the list.

General comments on the WRT code:
 - There's some code bloat that enables the inclusion of code in other OS's
  this should probably be removed.
 - We should probably make some abstraction/API of the so called Silicon
  Backplane bus that broadcom defined. I see allot of drivers, even in
  the mainline kernel (b44 ethernet driver) that use this.

> If you like to help, I would be giving you detailed information
> about the needed source code changes/addons.

Yes! Do you have any objection to make these publicly available?

> But may be it is time to send some patches...

Again yes, it should be possible to get this train rolling with some colaborative effort.

Regards,

Henk

  reply	other threads:[~2005-04-18 12:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-14 21:06 Porting mips based routers Henk
2005-04-15  6:55 ` Waldemar Brodkorb
2005-04-18 12:48   ` Henk [this message]
2005-04-19 18:32     ` Andy Isaacson
2005-04-19 21:35       ` Henk
2005-04-20 10:27       ` Ralf Baechle
  -- strict thread matches above, loose matches on Subject: below --
2005-04-14 16:26 Henk
2005-04-14 18:05 ` Ralf Baechle

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=20050418124809.GA27967@god.dyndns.org \
    --to=henk.vergonet@gmail.com \
    --cc=linux-mips@linux-mips.org \
    --cc=wbx@openbsd-geek.de \
    /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