linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Eric N. Johnson (ACD)" <ejohnson@acdstar.com>
To: linuxppc-embedded@ozlabs.org
Subject: New MPC5200 Eratta/ATA Bugs
Date: Mon, 25 Apr 2005 14:22:56 -0500	[thread overview]
Message-ID: <6.2.1.2.1.20050425130606.030aa288@mail.int.acdstar.com> (raw)

Freescale just realeased a new version of the eratta (hardware bugs) 
document for the MPC5200.  It was posted last week, and adds some pretty 
significant problems to the FEC Ethernet and IDE/ATA sections.

Specifically, I'm wonder if Eratta ID 485 may be the cause of some of the 
IDE issues we've been attributing to Bestcomm:

  "During the concurrent access of ATA DMA READ and PCI or LPC the
   ATA_ISOLATION signal can be incorrectly driven when ATA is paused."

Unfortunately, their proposed workaround isn't appropriate for many 
cases.  They suggest that you not use "ATA_ISOLATION" and connect the ATA 
device directly to the LP bus without any buffering.  This could lead to 
serious bus integrity issues, especially if the ATA device is connected by 
a ribbon cable.

Eric
------------------------------------
Eric Johnson, Electrical Engineer
Advanced Communication Design
   7901 12th Avenue South
   Bloomington, MN 55425
Ph: 952-854-4000  Fax: 952-854-5774

             reply	other threads:[~2005-04-25 19:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-25 19:22 Eric N. Johnson (ACD) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-25 19:35 New MPC5200 Eratta/ATA Bugs Stephen Warren
     [not found] ` <DBFABB80F7FD3143A911F9E6CFD477B00688411F@hqemmail02.nvidia .com>
2005-04-25 22:00   ` Eric N. Johnson (ACD)
2005-04-25 22:13 Stephen Warren

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=6.2.1.2.1.20050425130606.030aa288@mail.int.acdstar.com \
    --to=ejohnson@acdstar.com \
    --cc=linuxppc-embedded@ozlabs.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).