linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@motorola.com>
To: Dan Malek <dan@embeddededge.com>
Cc: Gerrit Van de Velde <gvd@denayer.wenk.be>,
	linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: MPC85xx support
Date: 15 Apr 2004 10:29:59 -0500	[thread overview]
Message-ID: <1082043000.20893.34.camel@baz.sps.mot.com> (raw)
In-Reply-To: <407EA4CA.4080208@embeddededge.com>


On Thu, 2004-04-15 at 10:05, Dan Malek wrote:
> Jon Loeliger wrote:
>
> > I am planning to release an updated version of the mpc85xx support
> > for U-Boot in just a few days.  It will be updated to Rev 1.1 and
> > has major improvements to the TSEC driver.
>
> Major improvements?  I recently posted a patch for the RPC/STx 8560
> board that included some TSEC updates, I don't know if they have made
> it into the CVS.  If not, please snag that from the mailing list so
> they are not lost.

Yesterday and today I have sync'ed up our internal tree to include
the delta up to the U-Boot 1.1.0 release.  Relative to what we had
in our tree before that (circa 2004_01_26), the only changes to the
TSEC code were a bunch of volatile declaration changes.  Those mods
are effectively captured in our update.  If there was more than that,
since the 1.1.0 release, I'll go searching...


> 	-- Dan

jdl


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2004-04-15 15:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-15 10:08 MPC85xx support Gerrit Van de Velde
2004-04-15 13:35 ` Jon Loeliger
2004-04-15 15:05   ` Dan Malek
2004-04-15 15:22     ` Matevz Langus
2004-04-15 15:35       ` Kumar Gala
2004-04-15 17:21         ` Jason McMullan
2004-04-19 11:23           ` Stefan Nickl
2004-04-15 15:29     ` Jon Loeliger [this message]
2004-04-15 15:37     ` Wolfgang Denk
2004-04-15 16:04       ` Dan Malek

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=1082043000.20893.34.camel@baz.sps.mot.com \
    --to=jdl@motorola.com \
    --cc=dan@embeddededge.com \
    --cc=gvd@denayer.wenk.be \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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;
as well as URLs for NNTP newsgroup(s).