All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Vacca <svacca@valcom.com>
To: "LinuxEmbeddedMailList (E-mail)" <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: mpc860 vs. mpc860T
Date: Tue, 15 Jan 2002 09:25:39 -0500	[thread overview]
Message-ID: <01C19DA6.994D3370.svacca@valcom.com> (raw)


I did a complete search for CONFIG_8xx_CPU6, and
truncated variations, in my mpc8xx-2.2.13 kernel, and
could not find it.  It doesn't show up as a cfg option either.
Even a grep on CONFIG_8xx doesn't show anything
resembling that.  Could it be in there and accessible
in an alternative way?

Steven

-----Original Message-----
From:	Wolfgang Denk [SMTP:wd@denx.de]
Sent:	Tuesday, January 15, 2002 9:01 AM
To:	svacca@valcom.com
Subject:	Re: mpc860 vs. mpc860T

Dear Steven,

in message <01C19DA2.0031A1C0.svacca@valcom.com> you wrote:
>
> My 860T rev is:  duht-duhduh-duuuuuhh: XPC860TZP50B3  :>(
>
> I guess that means I'll need some workarounds.

Right.

> My embedded linux kernel is Redhat's mpc8xx-2.2.13, so
> maybe porting in some workarounds might not be too painful.
> Could I please get access to your workarounds, Magnus?

Ummm... the CONFIG_8xx_CPU6 kernel  configuation  option  (workaround
for  CPU6  Silicon  Errata  (860  Pre  Rev.  C  et  al.)) was already
available with 2.2.13 kernels;  you  may  check  it  RH  bothered  to
include it. If so, just enable it.

Hope that helps,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Lead me not into temptation... I can find it myself.

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

             reply	other threads:[~2002-01-15 14:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-15 14:25 Steven Vacca [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-15 17:55 mpc860 vs. mpc860T Steven Vacca
2002-01-15 13:52 Steven Vacca
2002-01-14 19:02 Steven Vacca

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=01C19DA6.994D3370.svacca@valcom.com \
    --to=svacca@valcom.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.