linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Steven A. Falco" <sfalco@harris.com>
To: Lixin Yao <Lixin.Yao@HSTX.com>
Cc: linuxppc-dev@ozlabs.org, Aaron Pace <kodiakuppercut@gmail.com>
Subject: Re: Can not get PATA to work for Compact Flash with 2.6.28 kernel
Date: Wed, 04 Feb 2009 09:26:25 -0500	[thread overview]
Message-ID: <4989A591.8090807@harris.com> (raw)
In-Reply-To: <03D77CA4AC7F4D48A6AB5DA3F1001B3F10A4BC@exchtxus2.HSTX.global.vpn>

Lixin Yao wrote:
> I redefined io functions in libata-sff.c, byte operations are converted
> to 16bit word operations. Maybe I should ask for HW changes in new
> revisions of the board.
> 

I do recommend that.  We got it wrong on our first board too. :-)  It
is much better to get the hardware right than to carry your endian SW
patch forever.

Two other potential issues: 1) making sure the "most significant
byte enable" is used, so that byte writes work correctly.  You most
likely have this correct already, or you would not have gotten this
far.

And 2) make sure you allow for the hold time / turn-off time of the
CF.  We use a 440EPx, and cannot set up the external bus controller
to generate valid cycles in all cases.  So, we added some flip-flops
to stretch the rising edge of the chip select, which guarantees proper
timing.  (I'm going a bit far afield from the purpose of this mailing
list, so if you want more details, please contact me directly.)

	Steve

  reply	other threads:[~2009-02-04 14:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30 22:23 Can not get PATA to work for Compact Flash with 2.6.28 kernel Lixin Yao
2009-02-02 14:59 ` Steven A. Falco
2009-02-02 15:52   ` Lixin Yao
2009-02-02 16:37     ` Steven A. Falco
2009-02-02 20:39       ` Lixin Yao
2009-02-02 21:51         ` Steven A. Falco
2009-02-02 22:00           ` Lixin Yao
2009-02-04 14:26             ` Steven A. Falco [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-02-02 20:14 Aaron Pace

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=4989A591.8090807@harris.com \
    --to=sfalco@harris.com \
    --cc=Lixin.Yao@HSTX.com \
    --cc=kodiakuppercut@gmail.com \
    --cc=linuxppc-dev@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).