public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrea Acquaviva <aacquaviva@deis.unibo.it>
To: "ecos-discuss@sources.redhat.com" <ecos-discuss@sources.redhat.com>
Subject: [ECOS] CF driver
Date: Mon, 21 May 2001 03:53:00 -0000	[thread overview]
Message-ID: <3B08F3A7.7E578316@deis.unibo.it> (raw)

Hi all,

I'm writing an eCos driver for the CF interface on my Strongarm 1100
based board. I'm modifing the same driver written for the assabet board.
The main difference is that the assabet driver uses the SA1110 to
program the pcmcia interface, while on my board there is not the SA1110
companion chip.

In the assabet driver the CF is programmed also by writing on the BCR
register of the SA1110, in particular the interesting instruction is:

 assabet_BCR(SA1110_BCR_CF_POWER |
                        SA1110_BCR_CF_RESET |
                        SA1110_BCR_CF_BUS,
                        SA1110_BCR_CF_POWER_ON |
                        SA1110_BCR_CF_RESET_ENABLE |
                        SA1110_BCR_CF_BUS_ON);

My question is: what's the mean of the SA1110_BCR_CF_BUS flag? Is it a
particular assabet feature or do it perform some actions on the
PCMCIA interface pins that I must be aware?

Thanks for your help,
Andrea.



--
Ing. Andrea Acquaviva
D.E.I.S. - Universita' di Bologna
V.le Risorgimento, 2    40136 BOLOGNA (ITALY)
Tel: (+39) 051 20 93787 Fax: (+39) 051 2093786



             reply	other threads:[~2001-05-21  3:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-21  3:53 Andrea Acquaviva [this message]
2001-05-21  7:03 ` Gary Thomas
2001-05-21  9:02   ` Andrea Acquaviva
2001-05-21  9:13     ` Gary Thomas
2001-05-21  9:42       ` Andrea Acquaviva
     [not found] <XFMail.20010523084332.gthomas@cambridge.redhat.com>
2001-05-23  8:22 ` Andrea Acquaviva

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=3B08F3A7.7E578316@deis.unibo.it \
    --to=aacquaviva@deis.unibo.it \
    --cc=ecos-discuss@sources.redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).