From: Michael Buesch <mb@bu3sch.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Porting uboot to Broadcom 47xx (MIPS)
Date: Wed, 8 Apr 2009 01:07:25 +0200 [thread overview]
Message-ID: <200904080107.25997.mb@bu3sch.de> (raw)
In-Reply-To: <Pine.LNX.4.64ksi.0904071543360.12953@home-gw.koi8.net>
On Wednesday 08 April 2009 00:52:07 ksi at koi8.net wrote:
> On Wed, 8 Apr 2009, Michael Buesch wrote:
>
> > Hi,
> >
> > I'm the author of the Linux SSB subsystem, which implements 95% of the
> > system
> > bootup code for the Broadcom 47xx MIPS architecture.
> >
> > I'd like to start porting u-boot to the bcm47xx. (I guess nobody started
> > with this already?)
>
> Did I miss something or Broadcom (or Marvell) already started giving out
> their datasheets, less for something more useful without 37 NDAs per each
> BGA pin?
Well, there's full sourcecode available for CFE [1] (their crappy bootloader)
and there's a datasheet for the CPU and SDRAM controller (and some more).
I think that's enough to get a proper uboot port.
> I don't understand why we accept any code for all those closed platforms
> that no one can even get a rudimentary data without all those NDAs into a
> GPL-licensed U-Boot? Especially for those companies that make helluva secret
> even of mere PHYs, less something more complex...
>
> If it had been up to me I wouldn't've accepted any of such code into U-Boot.
I don't think 47xx really is a "closed platform".
Yeah, it's not a fully open platform, because there's little active support
from Broadcom. But there's lots of code and even some documentation around
for this platform.
Don't confuse bcm47xx with bcm43xx.
[1] Modified unofficial fork of CFE: http://bu3sch.de/gitweb?p=cfe.git;a=summary
--
Greetings, Michael.
next prev parent reply other threads:[~2009-04-07 23:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 22:10 [U-Boot] Porting uboot to Broadcom 47xx (MIPS) Michael Buesch
2009-04-07 22:52 ` ksi at koi8.net
2009-04-07 23:07 ` Michael Buesch [this message]
2009-04-07 23:48 ` Shinya Kuribayashi
2009-04-08 0:22 ` Michael Buesch
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=200904080107.25997.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=u-boot@lists.denx.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