linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mark Hatle <fray@mvista.com>
To: Dmytro Bablinyuk <dmytro.bablinyuk@tait.co.nz>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Linux support for MPC859T processor
Date: Tue, 01 Apr 2003 20:45:53 -0600	[thread overview]
Message-ID: <3E8A4EE1.8090205@mvista.com> (raw)
In-Reply-To: <3E8A4B70.7090607@tait.co.nz>


On userspace basis.. the 860 and the 859 are fully compatable.. The need for
859T changes may be in the kernel.  So anyone who sells/supports an 860 based
system can support your needs for application level.  (That includes MontaVista.)

The linux kernel of course is a different level of complexity.

--Mark

Dmytro Bablinyuk wrote:
>
> We are trying to find a linux supplier who supports Motorola MPC859T
> processor (actually it will be processor from Motorola but our custom
> board).
> We have contacted MontaVista and we discovered that the nearest
> processor they support is MPC860.
> Also we discovered that:
>
> An MPC860 based board might be suitable for initial S/W development
> purposes as the chip is very similar to the MPC859T we intend to use.
> There are 7 variants of the '860 with different cache sizes and serial
> communications capabilities.
> The main differences between the '860 and the '859T that I am aware of are:
>
> 1.    The '860 runs at approximately half the speed of the '859T.
> 2.    The clocking generator for the 860 would require a different
> configuration to the the '859 as a consequence of above.
> 3.    The '860 has an internal RTC function whereas the '859T does not.
> 4.    The '859T has a dedicated 10/100Mbps ethernet MAC whereas the '860
> has to use the serial communication controllers for ethernet operations.
> The available ethernet speeds depend on the particular variant of the '860.
> Note some of the '860 variants include a dedicated 10/100Mbps ethernet MAC.
> 5.     The '859T core operates off a lower voltage (1.8V) for power
> saving whereas the '860 core runs off a 3.3V supply.
> Consequently the '860 draws approximately 2x the power of the '859T.
>
> Apart from the differing core voltages the '860 and '859T appear to be
> pin compatible
>
> * Could somebody please give me an advice on how much S/W work might be
> involved in the future to port linux from '860 to '859T based on 1-5
> (see above)
>
> * Can you suggest (based on above) any of 7 variants of the '860
>
> Thank you
>
>
>
>
>


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

  reply	other threads:[~2003-04-02  2:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-02  2:31 Linux support for MPC859T processor Dmytro Bablinyuk
2003-04-02  2:45 ` Mark Hatle [this message]
2003-04-02  3:05   ` Dmytro Bablinyuk
2003-04-02  3:13     ` Mark Hatle
2003-04-02  3:39       ` Dmytro Bablinyuk
2003-04-02 18:15         ` Conn Clark
2003-04-03  8:59           ` Frank Robbins
  -- strict thread matches above, loose matches on Subject: below --
2003-04-02 14:41 Jean-Denis Boyer

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=3E8A4EE1.8090205@mvista.com \
    --to=fray@mvista.com \
    --cc=dmytro.bablinyuk@tait.co.nz \
    --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).