From: Andy Isaacson <adi@hexapodia.org>
To: Henk <Henk.Vergonet@gmail.com>
Cc: Waldemar Brodkorb <wbx@openbsd-geek.de>, linux-mips@linux-mips.org
Subject: Re: Porting mips based routers
Date: Tue, 19 Apr 2005 11:32:59 -0700 [thread overview]
Message-ID: <20050419183259.GA623@hexapodia.org> (raw)
In-Reply-To: <20050418124809.GA27967@god.dyndns.org>
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
next prev parent reply other threads:[~2005-04-19 18:33 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
2005-04-19 18:32 ` Andy Isaacson [this message]
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=20050419183259.GA623@hexapodia.org \
--to=adi@hexapodia.org \
--cc=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