linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Ing.Gianfranco Morandi" <gianfranco.morandi@euro-studio.it>
To: <acurtis@onz.com>, "Omanakuttan" <omanakuttan@tataelxsi.co.in>,
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: mcc support on mpc8260
Date: Fri, 13 Dec 2002 17:04:40 +0100	[thread overview]
Message-ID: <015801c2a2c1$57fecf20$0700a8c0@pc005> (raw)
In-Reply-To: NCBBIINEHIPFGJPLBEIFAEBDEAAA.acurtis@onz.com


I mean that by using the revision A.1 You could have some troubles.
Main reason is related to the Global Underrun (GUN) that often occours when
many channels are active (we use continuosly 64 channels on one mcc). This
issue has been repored by Motorola in its document "mpc8260cesumm.pdf" and
finally soved in the revision C.2 (6K23A)
Second issue, is related to the possibility of having a bit rotation into a
time slot. This problem has never been reported by Motorola but it seems to
be any more present in revisione C.2.

Regards

Gianfranco

----- Original Message -----
From: "Allen Curtis" <acurtis@onz.com>
To: "Ing.Gianfranco Morandi" <gianfranco.morandi@euro-studio.it>;
"Omanakuttan" <omanakuttan@tataelxsi.co.in>;
<linuxppc-embedded@lists.linuxppc.org>
Sent: Friday, December 13, 2002 3:59 PM
Subject: RE: mcc support on mpc8260


>
> > Be aware do not use the mcc with the silicon revision older than B.1.
>
> Could you provide more information on this comment. There are lots of
> reasons not to use a rev A.1 chip. This is the first time that I heard
about
> using too new of a chip.
>
> THX
>
>
>


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

  reply	other threads:[~2002-12-13 16:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-12 16:42 mcc support on mpc8260 Omanakuttan
2002-12-13  9:47 ` Ing.Gianfranco Morandi
2002-12-13 14:59   ` Allen Curtis
2002-12-13 16:04     ` Ing.Gianfranco Morandi [this message]
2002-12-13 15:38   ` Omanakuttan

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='015801c2a2c1$57fecf20$0700a8c0@pc005' \
    --to=gianfranco.morandi@euro-studio.it \
    --cc=acurtis@onz.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=omanakuttan@tataelxsi.co.in \
    /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).