linux-mips
[Top] [All Lists]

Re: Porting mips based routers

To: Henk <Henk.Vergonet@gmail.com>
Subject: Re: Porting mips based routers
From: Andy Isaacson <adi@hexapodia.org>
Date: Tue, 19 Apr 2005 11:32:59 -0700
Cc: Waldemar Brodkorb <wbx@openbsd-geek.de>, linux-mips@linux-mips.org
In-reply-to: <20050418124809.GA27967@god.dyndns.org>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20050414210645.GB30585@god.dyndns.org> <20050415065558.GD25962@openbsd-geek.de> <20050418124809.GA27967@god.dyndns.org>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4.1i
On Mon, Apr 18, 2005 at 02:48:09PM +0200, Henk wrote:
> 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.

One comment:

# - Migrate: Should we cluster this with the sibyte stuf? Probably
# there's some shared code....

SiByte and the 47xx don't share anything significant beyond both being
MIPS, and both running CFE.  And people (including Ralf) actually have
SiByte hardware that they test on.  So not breaking SiByte would be a
good thing.

Because there's no technical connection between SiByte and 47xx I'd lean
towards leaving the SiByte stuff alone, and clean up the 47xx code on
its own.

> General comments on the WRT code:

The code is full of "Broadcom Proprietary" and "All Rights Reserved"
notices.  Does anyone have a clear written statement from Broadcom that
it's redistributable?  (If you're depending on the GPL release
requirements to justify relicensing, clear documentation of the chain of
release would be helpful.)

>  - 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.

The Silicon Backplane bus actually came from another company, it wasn't
defined by Broadcom; google knows all:
http://www.ocpip.org/socket/adoption/sonics

I think there are other OCP busses supported in the kernel; ISTR seeing
some PPC SoC from IBM that uses OCP... so perhaps this should be brought
up on l-k for general discussion.

But it's challenging to come up with a useful abstraction that covers
both the b44 scenario and the SoC scenario.

 - for b44, OCP is on the far side of the PCI bus, and is used only to
   access a single core (ethernet MAC).

 - for bcm947xx (and ppc SoC, I guess), OCP is the system bus, and is
   used to access everything from PCI to DRAM.

grep grep grep... Take a look at include/asm-ppc/ocp.h and
arch/ppc/platforms/*.c, it looks like the PowerPC people have already
done a bunch of work here.

-andy

<Prev in Thread] Current Thread [Next in Thread>