linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Travis B. Sawyer" <tsawyer@broadcom.com>
To: Andriy Korud <a.korud@vector.com.pl>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: CF card connection to PPC CPUs
Date: Tue, 18 Apr 2006 08:48:31 -0400	[thread overview]
Message-ID: <4444E01F.5000100@broadcom.com> (raw)
In-Reply-To: <60E856FD577CC04BA3727AF4122D3F160106FDDB@3bit.vector.com.pl>

Andriy Korud wrote:

>Hi,
>Does anybody has experience in connecting CF card to PPC (especially
>44x) CPU directly via EBC bus?
>I see how this can be done in TrueIDE mode, but unfortunately our
>application requires hot swap capability.
>
>  
>
Andriy:

We've done the direct connect route on a couple of our platforms 
(formerly Sandburst Metrobox).
Unfortunately, as you state, you lose HS caps.

We used two chip selects, and connected the bus as follows:

EBC Addr 28:30 <-> CF Addr 2:0

EBC Data   CF Data
8                    15
9                    14
10                  13
11                  12
12                  11
13                  10
14                  9
15                  8
0                    7
1                    6
2                    5
3                    4
4                    3
5                    2
6                    1
7                    0

/OE  & /CSEL are pulled down
/REG & /WE are pulled up.

Check out Das U-Boot Sandburst Metrobox (include/configs/METROBOX.h) for 
usage info.
We essentially used a technote/appnote from Toshiba (that I can't find 
right now).

Good luck,

travis

      reply	other threads:[~2006-04-18 13:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-18 10:35 CF card connection to PPC CPUs Andriy Korud
2006-04-18 12:48 ` Travis B. Sawyer [this message]

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=4444E01F.5000100@broadcom.com \
    --to=tsawyer@broadcom.com \
    --cc=a.korud@vector.com.pl \
    --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).