All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Andy Isaacson <adi@hexapodia.org>
Cc: Henk <Henk.Vergonet@gmail.com>,
	Waldemar Brodkorb <wbx@openbsd-geek.de>,
	linux-mips@linux-mips.org
Subject: Re: Porting mips based routers
Date: Wed, 20 Apr 2005 11:27:24 +0100	[thread overview]
Message-ID: <20050420102724.GD5212@linux-mips.org> (raw)
In-Reply-To: <20050419183259.GA623@hexapodia.org>

On Tue, Apr 19, 2005 at 11:32:59AM -0700, Andy Isaacson wrote:

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

Broadcom's interpretation of these comments is that they don't contradict
the GPL.

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

OCP is basically ISA on steroids - no configuration space, no nothing so
there is not terribly much OCP code that could potencially be shared.
Right now we treat OCP devices such as on PMC-Sierra's RM9000 series as
platform devices.

I'm clearly less than impressed by OCP ...

  Ralf

  parent reply	other threads:[~2005-04-20 10:28 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
2005-04-19 21:35       ` Henk
2005-04-20 10:27       ` Ralf Baechle [this message]
  -- 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=20050420102724.GD5212@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=Henk.Vergonet@gmail.com \
    --cc=adi@hexapodia.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.