From: Magnus Damm <damm@opensource.se>
To: "Gerhard TAEUBL" <Gerhard.TAEUBL@frequentis.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: PCMCIA
Date: Fri, 7 Mar 2003 17:18:30 +0000 [thread overview]
Message-ID: <20030307171830.1dca14f1.damm@opensource.se> (raw)
In-Reply-To: <se68594f.071@mail.frequentis.com>
Hi,
> We are using MPC860T with one possible PCMCIA port and Montavista kernel 2.4.2.
> So it is possible to use every PCMCIA card, which is supported by Linux?
Not all cards worked "right out of the box" when I wrote the socket driver.
And I don't think that all of them will work today either.
There are many things that might cause problems - endian unawareness, timing stuff etc.
So you will not be able to install a set of RPMs on your hardware and then just
insert any PCMCIA card and hear bleep-bleep and everything works. No.
But with some hacking and some knowledge of Linux and PCMCIA you will probably
find out a collection of PCMCIA cards that will work ok.
I don't know how many PCMCIA cards that Linux/pcmcia-cs supports, but I guess
that everyone uses CARDBUS today instead of PCMCIA. 32 bits are much more fun.
I think that I read that someone was planning on writing a list, but I don't
remeber seeing any actual output. Or maybe I missed that.
There are (were anyhow) many things that differs between a common PC and
the Linux implementation on a embedded powerpc box. The IDE stuff, serial
ports and other things are treated different. And it all depends on the
variant and version of your kernel. What fun.
And the status of your Montavista kernel - I have no idea.
Have you modified the socket driver to fit your hardware?
You will not be able to use any PCMCIA card without correct configuration.
Hope this leads you in the right direction.
/ magnus
On Fri, 07 Mar 2003 08:32:47 +0100
"Gerhard TAEUBL" <Gerhard.TAEUBL@frequentis.com> wrote:
>
> Hi again!
>
> Maybe I frogot some information:
>
> We need for a project a second 100MBit interface, so our soloution will be to use a PCMCIA card. Does there exists an actual compatibility list which cards works, which not? I only found a list from 2000 or 2001.
>
> Please help :-)
>
>
> We are using MPC860T with one possible PCMCIA port and Montavista kernel 2.4.2.
> So it is possible to use every PCMCIA card, which is supported by Linux?
>
> Again, please help...
>
> best regards
> Gerhard
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-03-07 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 7:32 PCMCIA Gerhard TAEUBL
2003-03-07 17:18 ` Magnus Damm [this message]
2003-03-07 19:53 ` PCMCIA Wolfgang Denk
[not found] <se6c604d.015@mail.frequentis.com>
2003-03-10 9:01 ` PCMCIA Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2003-03-10 8:18 PCMCIA Gerhard TAEUBL
2003-03-10 8:45 ` PCMCIA Wolfgang Denk
2003-03-04 10:36 PCMCIA Gerhard TAEUBL
2000-02-05 19:21 PCMCIA Ryan Boder
1999-12-23 3:28 PCMCIA Nguyen Xuan Hoang
2000-06-23 7:55 ` PCMCIA Jo-Ellen F. Mathews
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=20030307171830.1dca14f1.damm@opensource.se \
--to=damm@opensource.se \
--cc=Gerhard.TAEUBL@frequentis.com \
--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).