public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Travis B. Sawyer <tsawyer+u-boot@sandburst.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] mpc8xx, pcmcia to CF, ide
Date: Wed, 07 Sep 2005 10:30:29 -0400	[thread overview]
Message-ID: <431EF985.2040601@sandburst.com> (raw)

Greetings u-boot'ers:

I've had pretty good luck with my little rpx classic board.

I've gotten pcmcia to work (albeit not flawlessly, I toasted
one of my pcmcia flash cards).

I've run into an interesting problem:  When using a pcmcia to
CF adapter, I can access the CF on an older CF card (16mb).
However, with newer cards (ranging from 32mb to 512mb), the
pcmcia driver gets 00's for all of the tuples.

Scanning the attribute mem on the old card I can see the
the tuples (starting at 0xE000_0000).  New cards get 00's
at the same address.

Up until now, my only dealing with CF has been direct connect
to a 440GX peripheral bus in 'True IDE Mode'.

My best guess is that the new cards are CF+.  The CF spec
calls out the tuple arrangement, however, I can't find the
CIS tuples.

Anyone have any ideas where they may be?  Or do I need to
utilize some special cycles to make them show up?

Per the CF 3.0 spec (CIS Read):
	/CE2  /CE1 /REG /OE /WE A10 A9 A8-A1 A0
CF:	X     0    0    0   1   0   0   XX   0
CF+:	X     0    0    0   1   X   X   XX   0

So, I would assume, that the same cycle could occur for CIS Read?!?


Anyone using CF+ on 8xx pcmcia?

Thanx for any insight!

-Travis

             reply	other threads:[~2005-09-07 14:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-07 14:30 Travis B. Sawyer [this message]
2005-09-07 14:46 ` [U-Boot-Users] mpc8xx, pcmcia to CF, ide Travis B. Sawyer
2005-09-09 20:27   ` Travis B. Sawyer

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=431EF985.2040601@sandburst.com \
    --to=tsawyer+u-boot@sandburst.com \
    --cc=u-boot@lists.denx.de \
    /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