linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: Magnus Damm <damm@kieraypc01.p.y.ki.era.ericsson.se>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: pcmcia-cs for 8xx
Date: Wed, 29 Dec 1999 12:59:43 -0500	[thread overview]
Message-ID: <386A4C0F.712A4AAC@netx4.com> (raw)
In-Reply-To: 3869B35C.33986836@switchboard.ericsson.se


Magnus Damm wrote:

> What's the status about the 8xx pcmcia controller?

The hardware seems to work (mostly...).


> Wouldn't it be nice to use the pcmcia-cs package?


Maybe.  I have discussed this with several people over the
past year.  None of the product requirements I have seen
for 8xx PCMCIA need the capabilities of the pcmcia-cs.  They
didn't require hot swap or a variety of cards supported.  They
all fit a card before power up and it never changed.  All of
the projects I have done were "need it yesterday", so I just
used minimal functions to map the PCMCIA and get on with life.
I never had the time to port the pcmcia-cs package.  In the
embedded system, they didn't want the overhead of module
support programs, so these are also compiled kernel drivers.
The whole of pcmcia-cs assumes modules.

One difficulty with the PCMCIA on the 8xx is all board designs
I have seen use different power control methods, so the modifications
would include board specfic functions for this.

> Anyone done that already?

Not that I am aware.


> I saw some messages floating around about RPXLite 823.

Mark Mathews has wireless PCMCIA cards working, with some
weird hardware difficulty.

I have done several types of Flash card and some things I
can't talk about yet on the RPX-Lite PCMCIA.

> Is there anything I should know before I start digging?

There are lots of hardware variations.  The 860 has two PCMCIA
ports, sometimes boards use both or only one.  The 823/850 have
only PCMCIA B.  There are the pin multiplexing issues for the
8xx and the PCMCIA.  Some board designs intend to use PCMCIA,
but failed because they used the pins in a way that precludes
mapping them to the PCMCIA.

If you intend to do this, make sure you post your intentions
and progress.  I may make some of my time available to help out,
I just can't take on the whole project.


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      parent reply	other threads:[~1999-12-29 17:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-29  7:08 pcmcia-cs for 8xx Magnus Damm
1999-12-29 15:04 ` Mark S. Mathews
1999-12-29 18:10   ` Dan Malek
1999-12-29 17:59 ` Dan Malek [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=386A4C0F.712A4AAC@netx4.com \
    --to=dan@netx4.com \
    --cc=damm@kieraypc01.p.y.ki.era.ericsson.se \
    --cc=linuxppc-embedded@lists.linuxppc.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).