linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <kumar.gala@motorola.com>
To: Matevz Langus <matevy@arhitektova-delavnica.com>
Cc: "Dan Malek" <dan@embeddededge.com>,
	"Jon Loeliger" <jdl@motorola.com>,
	"linuxppc-embedded" <linuxppc-embedded@lists.linuxppc.org>,
	"Gerrit Van de Velde" <gvd@denayer.wenk.be>
Subject: Re: MPC85xx support
Date: Thu, 15 Apr 2004 10:35:15 -0500	[thread overview]
Message-ID: <7E4506ED-8EF2-11D8-8550-000393DBC2E8@motorola.com> (raw)
In-Reply-To: <49705.193.77.24.1.1082042532.squirrel@www.arhitektova-delavnica.com>


We have been keeping the linuxppc-2.4 bitkeeper in sync with our work
for 85xx.  See http://penguinppc.org/dev/kernel.shtml on how to get
access.

 From the kernel point of view, SPE applications should be enabled
(context switching and debug support).

- kumar

On Apr 15, 2004, at 10:22 AM, Matevz Langus wrote:

>
> Hi,
>
> I also use U-Boot and Linux 2.4 on 8560 quite successfully.
> Has anyone tried to use SPE unit of e500?
>
> I would also be interested in dev versions of 85xx kernels? Is it
> possible
> to get access to the cvs?
>
> thanks,
>   Matevz
>
>>
>> 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.
>>
>>> .....  An updated Linux release
>>> is close as well, but I'll let my partner in crime speak there. :-)
>>
>> Those of us working on 85xx support have our own local versions of
>> Linux 2.4.  Due to the amount of change and the desire to keep 2.4
>> stable, we are negotiating some clever ways to get this checked into
>> the public trees.  I have the U-boot and kernel available for the
>> RPC/STx GP3 boards on my server, if that is useful to get you started.
>>
>> Thanks.
>>
>>
>> 	-- Dan
>>
>>
>>
>
>


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

  reply	other threads:[~2004-04-15 15:35 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 [this message]
2004-04-15 17:21         ` Jason McMullan
2004-04-19 11:23           ` Stefan Nickl
2004-04-15 15:29     ` Jon Loeliger
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=7E4506ED-8EF2-11D8-8550-000393DBC2E8@motorola.com \
    --to=kumar.gala@motorola.com \
    --cc=dan@embeddededge.com \
    --cc=gvd@denayer.wenk.be \
    --cc=jdl@motorola.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=matevy@arhitektova-delavnica.com \
    /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).