public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Bradley A. Bosch <bbosch@iphase.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Round 2 : Any MV64360 u-boot work in progress?
Date: Wed, 12 Mar 2003 22:44:10 -0600	[thread overview]
Message-ID: <15984.3226.890931.674681@lachman.com> (raw)
In-Reply-To: <20030312211432.GA629@hobag.internal.zumanetworks.com>

Nye,

I'm not sure from your message if the code you have in code freeze
also supports the Discovery II or just the Discovery I?  If it
supports the Discovery II, I would love to have a copy as I do still
need to port or write support for this chip for U-Boot.

Brian and all,

I do have some code for Ppcboot that Ingo Assmus was kind enough to
send, but I was delayed by a rather spectacular failure of the DC-DC
power supply card on the Marvell evaluation board the first time we
powered it up.  It has taken them over a month to send a replacement
so I'm still at the starting gate.  The new board is actually due here
late this week, so I should be picking up this work again by Friday.

Ingo,

If you have made improvements since you sent it, could you send me an
update please?

Thanks everyone,

--Brad Bosch

Nye Liu writes:
 > Bradley:
 > 
 > I was the one of the last people actively maintaining the ppcboot ev64260
 > port.
 > 
 > No current u-boot work is being done here, our ppcboot port is in code
 > freeze for production.
 > 
 > Hope there are others working on porting to u-boot...
 > 
 > Regards,
 > Nye

      reply	other threads:[~2003-03-13  4:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12 20:52 [U-Boot-Users] Round 2 : Any MV64360 u-boot work in progress? Brian Waite
2003-03-12 21:09 ` Wolfgang Denk
2003-03-12 21:14 ` Nye Liu
2003-03-13  4:44   ` Bradley A. Bosch [this message]

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=15984.3226.890931.674681@lachman.com \
    --to=bbosch@iphase.com \
    --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