Re: PCMCIA

Re: PCMCIA

[Gerhard TAEUBL]

Hi!

Well this issue we discussed with our project developer...
They want to use 2 Ethernetports for a double ethernet network, for saftey issues. We know, that we never get the full 100MBit on a MPC860 however, the point is, that our hardware don't get much data, but other components (PCs) in the network needs this bandwidth. Beside this to use a SCC for Ethernet we need an hardware redesign with a lot of software adaptions....

We have only one PCMCIA Port realised in HW.

So the (your) DENX Kernel (2.4.4) has PCMCIA support implemented yet? So this is maybe a reason for us to switch over.. (Uhuhu I hope this will not too much work to adapt the configuration again.... :-)

So do you have a list which Ethernet cards work? Or is it only the Xircom card that works?

Gerhard

>>> Wolfgang Denk <wd@denx.de> 03/07/03 08:53pm >>>
In message <se68594f.071@mail.frequentis.com> you wrote:
>
> 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.

Why do you think you need a second 100MBit interface? The performance
of  a  MPC8xx  is  a  bit  limited,  so  don't  expect  too  much  of
throughput...

Probably a 10 Mbps interface on a SCC would be the easier solution.

> We are using MPC860T with one possible PCMCIA port and Montavista kernel 2.4.2.

I cannot speak about MV's 2.4.2 kernel, except that it's  pretty  old
and  I  doubt  it  has  full PCMCIA support. But the MPC860T supports
_two_ PCMCIA slots.

> So it is possible to use every PCMCIA card, which is supported by Linux?

You will not get any guarantees. Try it out. The (few!) network cards
we tested so far worked fine.

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
C++ was an interesting and valuable experiment, but we've learned its
lessons and it's time to move on.
                            - Peter Curran in <DCqM4z.BxB@isgtec.com>


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

Re: PCMCIA

[Wolfgang Denk]

In message <se6c5894.038@mail.frequentis.com> you wrote:
>
> So the (your) DENX Kernel (2.4.4) has PCMCIA support implemented yet?

Yes.

> So this is maybe a reason for us to switch over.. (Uhuhu I hope this
> will not too much work to adapt the configuration again.... :-)

I don't think so. It's just the  usual  files  where  board-dependend
configs have to be added.

> So do you have a list which Ethernet cards work? Or is it only the Xircom card that works?

We also tested with a 3com card, but I don't remember the exact  type
(sorry,  I  don't  have  this  card  any  more). In general my PCMCIA
experience is that all cards that work in a "normal" (x86) PC  worked
fine  on  the  8xx,  too.  Ideally  you  test  before  buying using a
PowerBook...

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Too many people are ready to carry the stool when the piano needs  to
be moved.

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

Re: PCMCIA

[Wolfgang Denk]

In message <se6c604d.015@mail.frequentis.com> you wrote:
> Thanks for help, with a powerbook, thats a nice hint, at the moment we
> have 'only' an imac. O.K.

An iMac is ok, too. Any native PPC system will  do  -  it's  just  to
verify  that  the  Linux  driver  is  working  in  general,  and on a
big-endian system, too.

> I can remember you have an own uart device driver, not the same like in
> the Montavista tree, and we have a 'special' feature to switch between
> RS232 and RS422/485.. but that is not your problem ... :-)

Our driver is highly configurable, maybe it's easier than you think.


Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
A stone was placed at a ford in a river with the inscription:
"When this stone is covered it is dangerous to ford here."

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

PCMCIA

[Gerhard TAEUBL]

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/

Re: PCMCIA

[Magnus Damm]

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/

Re: PCMCIA

[Wolfgang Denk]

In message <se68594f.071@mail.frequentis.com> you wrote:
>
> 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.

Why do you think you need a second 100MBit interface? The performance
of  a  MPC8xx  is  a  bit  limited,  so  don't  expect  too  much  of
throughput...

Probably a 10 Mbps interface on a SCC would be the easier solution.

> We are using MPC860T with one possible PCMCIA port and Montavista kernel 2.4.2.

I cannot speak about MV's 2.4.2 kernel, except that it's  pretty  old
and  I  doubt  it  has  full PCMCIA support. But the MPC860T supports
_two_ PCMCIA slots.

> So it is possible to use every PCMCIA card, which is supported by Linux?

You will not get any guarantees. Try it out. The (few!) network cards
we tested so far worked fine.

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
C++ was an interesting and valuable experiment, but we've learned its
lessons and it's time to move on.
                            - Peter Curran in <DCqM4z.BxB@isgtec.com>

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

PCMCIA

[Gerhard TAEUBL]

Hi!

Yet another PCMCIA question :-)

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 :-)

Thx in advance

Gerhard

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

RE: pcmcia

[Guillermo A. Loyola]

> The pcmcia variable ioaddr_t should be a 32 bit type for my socket
> driver.  Is there any harm to other mips pcmcia socket drivers if we
> apply the patch below?

We need the same here, how about doing this instead:

#ifdef __i386__
typedef u_short   ioaddr_t;
#else
typedef u_int	ioaddr_t;
#endif

Gmo.

RE: pcmcia

[Pete Popov]

On Fri, 2001-11-30 at 00:39, Guillermo A. Loyola wrote:
> > The pcmcia variable ioaddr_t should be a 32 bit type for my socket
> > driver.  Is there any harm to other mips pcmcia socket drivers if we
> > apply the patch below?
> 
> We need the same here, how about doing this instead:
> 
> #ifdef __i386__
> typedef u_short   ioaddr_t;
> #else
> typedef u_int	ioaddr_t;
> #endif

That probably makes more sense.  I wasn't sure if it's only x86 that
needs? ioaddr_t to be a 16 bit type.  

Pete

Re: pcmcia

[Alan Cox]

> > We need the same here, how about doing this instead:
> > 
> > #ifdef __i386__
> > typedef u_short   ioaddr_t;
> > #else
> > typedef u_int	ioaddr_t;
> > #endif
> 
> That probably makes more sense.  I wasn't sure if it's only x86 that
> needs? ioaddr_t to be a 16 bit type.  

Is there any platform where making it int actually -breaks-. At least for
2.5 it would seem a lot saner to just make it bigger and see

Alan

Re: pcmcia

[Alan Cox]

> > We need the same here, how about doing this instead:
> > 
> > #ifdef __i386__
> > typedef u_short   ioaddr_t;
> > #else
> > typedef u_int	ioaddr_t;
> > #endif
> 
> That probably makes more sense.  I wasn't sure if it's only x86 that
> needs? ioaddr_t to be a 16 bit type.  

Is there any platform where making it int actually -breaks-. At least for
2.5 it would seem a lot saner to just make it bigger and see

Alan

Re: pcmcia

[Pete Popov]

On Fri, 2001-11-30 at 09:54, Alan Cox wrote:
> > > We need the same here, how about doing this instead:
> > > 
> > > #ifdef __i386__
> > > typedef u_short   ioaddr_t;
> > > #else
> > > typedef u_int	ioaddr_t;
> > > #endif
> > 
> > That probably makes more sense.  I wasn't sure if it's only x86 that
> > needs? ioaddr_t to be a 16 bit type.  
> 
> Is there any platform where making it int actually -breaks-. 

I can't see how it would break anything ... but I've said that before. 
It's not a variable which maps a hardware register, a protocol field,
etc, so it should be safe to just make it an int.  

> At least for 2.5 it would seem a lot saner to just make it bigger and see

Pete

pcmcia

[Pete Popov]

The pcmcia variable ioaddr_t should be a 32 bit type for my socket
driver.  Is there any harm to other mips pcmcia socket drivers if we
apply the patch below?  If not, it would make it so much easier if I
don't have to debug this problem with each new kernel (having forgotten
about the need for this patch)...


--- linux-orig/include/pcmcia/cs_types.h	Mon Nov  5 16:55:31 2001
+++ linux/include/pcmcia/cs_types.h	Thu Nov 29 12:27:42 2001
@@ -36,7 +36,7 @@
 #include <sys/types.h>
 #endif
 
-#ifdef __arm__
+#if defined(__arm__) || defined(__mips__)
 typedef u_int   ioaddr_t;
 #else
 typedef u_short	ioaddr_t;

pcmcia

[David Feuer]

What is the current status of PC-card support?  I've seen ominous signs on 
this list about the state of support....  I have a laptop with a PCMCIA 
network card (a 3com thing). Will it work?

--
This message has been brought to you by the letter alpha and the number pi.
David Feuer
David_Feuer@brown.edu

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: pcmcia

[Jeff Garzik]

David Feuer wrote:
> 
> What is the current status of PC-card support?  I've seen ominous signs on
> this list about the state of support....  I have a laptop with a PCMCIA
> network card (a 3com thing). Will it work?

It should, yes.  Enable hotplug, cardbus, and 3com vortex/boomerang
support...

-- 
Jeff Garzik             | "When I do this, my computer freezes."
Building 1024           |          -user
MandrakeSoft            | "Don't do that."
                        |          -level 1
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: pcmcia

[David Ford]

[-- Attachment #1: Type: text/plain, Size: 445 bytes --]

With a few exceptions, it should work.  The problematic systems are few.

-d

David Feuer wrote:

> What is the current status of PC-card support?  I've seen ominous signs on
> this list about the state of support....  I have a laptop with a PCMCIA
> network card (a 3com thing). Will it work?

--
"The difference between 'involvement' and 'commitment' is like an
eggs-and-ham breakfast: the chicken was 'involved' - the pig was
'committed'."



[-- Attachment #2: Card for David Ford --]
[-- Type: text/x-vcard, Size: 176 bytes --]

begin:vcard 
n:Ford;David
x-mozilla-html:TRUE
adr:;;;;;;
version:2.1
email;internet:david@kalifornia.com
title:Blue Labs Developer
x-mozilla-cpt:;14688
fn:David Ford
end:vcard

Re: pcmcia

[Brett]

Hey,

I don't know if this counts as a _problem_, 
but I need to enable pci support to get pcmcia/cardbus activated.
Is this really necessary ?? My current kernels work fine without pci
support, and sure, enabling it won't hurt, just make the kernel bigger,
but why is the restriction there ?

Also, what has happened to the i82365 support that I need ? 
Its nicely commented out in drivers/net/pcmcia/Config.in

I remember everything working fine up until about test3/4, since then I've
had to revert to the pcmcia-cs package.

Just wondering whats going on ?

	/ Brett

On Wed, 8 Nov 2000, David Ford wrote:
>
> With a few exceptions, it should work.  The problematic systems are few.
> 
> -d
> 
> David Feuer wrote:
> 
> > What is the current status of PC-card support?  I've seen ominous signs on
> > this list about the state of support....  I have a laptop with a PCMCIA
> > network card (a 3com thing). Will it work?
> 
> --
> "The difference between 'involvement' and 'commitment' is like an
> eggs-and-ham breakfast: the chicken was 'involved' - the pig was
> 'committed'."
> 
> 
> 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: pcmcia

[David Ford]

[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]

You may be in the same boat I'm in then.  i82365 is what I used and it worked.
yenta doesn't.  Right now I'm stuck with using my USB nic because neither the
kernel's pcmcia or dh pcmcia work for me.

-d

Brett wrote:

> Hey,
>
> I don't know if this counts as a _problem_,
> but I need to enable pci support to get pcmcia/cardbus activated.
> Is this really necessary ?? My current kernels work fine without pci
> support, and sure, enabling it won't hurt, just make the kernel bigger,
> but why is the restriction there ?
>
> Also, what has happened to the i82365 support that I need ?
> Its nicely commented out in drivers/net/pcmcia/Config.in
>
> I remember everything working fine up until about test3/4, since then I've
> had to revert to the pcmcia-cs package.
>
> Just wondering whats going on ?
>
>         / Brett
>
> On Wed, 8 Nov 2000, David Ford wrote:
> >
> > With a few exceptions, it should work.  The problematic systems are few.
> >
> > -d
> >
> > David Feuer wrote:
> >
> > > What is the current status of PC-card support?  I've seen ominous signs on
> > > this list about the state of support....  I have a laptop with a PCMCIA
> > > network card (a 3com thing). Will it work?
> >
> > --
> > "The difference between 'involvement' and 'commitment' is like an
> > eggs-and-ham breakfast: the chicken was 'involved' - the pig was
> > 'committed'."
> >
> >
> >
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/

--
"The difference between 'involvement' and 'commitment' is like an
eggs-and-ham breakfast: the chicken was 'involved' - the pig was
'committed'."



[-- Attachment #2: Card for David Ford --]
[-- Type: text/x-vcard, Size: 176 bytes --]

begin:vcard 
n:Ford;David
x-mozilla-html:TRUE
adr:;;;;;;
version:2.1
email;internet:david@kalifornia.com
title:Blue Labs Developer
x-mozilla-cpt:;14688
fn:David Ford
end:vcard

Re: pcmcia

[FORT David]

David Ford wrote:

> You may be in the same boat I'm in then.  i82365 is what I used and it worked.
> yenta doesn't.  Right now I'm stuck with using my USB nic because neither the
> kernel's pcmcia or dh pcmcia work for me.
>
> -d
>
> Brett wrote:
>
> > Hey,
>

[....]

>
> > > "The difference between 'involvement' and 'commitment' is like an
> > > eggs-and-ham breakfast: the chicken was 'involved' - the pig was
> > > 'committed'."
> > >
> > >
> > >
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > Please read the FAQ at http://www.tux.org/lkml/
>
> --
> "The difference between 'involvement' and 'commitment' is like an
> eggs-and-ham breakfast: the chicken was 'involved' - the pig was
> 'committed'."

I got the same problem for an old 486 with no PCI, as yenta_socket doesn't work, i
have to add CONFIG_I82365
in order to have things work. 'till this is set and recompiled, everything works
perfectly. The controller is a
VLSI 82C146.
I'm problably missing something, but these's two things i don't understand:
-why PCMCIA depends on PCI at compilation time
-why yenta is activated for i82365, as it doesn't do the job i82365 did.


--
%-------------------------------------------------------------------------%
% FORT David,                                                             %
% 7 avenue de la morvandière                                   0240726275 %
% 44470 Thouare, France                                epopo@onetelnet.fr %
% ICU:78064991   AIM: enlighted popo             fort@irin.univ-nantes.fr %
%--LINUX-HTTPD-PIOGENE----------------------------------------------------%
%  -datamining <-/                        |   .~.                         %
%  -networking/flashed PHP3 coming soon   |   /V\        L  I  N  U  X    %
%  -opensource                            |  // \\     >Fear the Penguin< %
%  -GNOME/enlightenment/GIMP              | /(   )\                       %
%           feel enlighted....            |  ^^-^^                        %
%                           http://ibonneace.dnsalias.org/ when connected %
%-------------------------------------------------------------------------%



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: pcmcia

[Horst von Brand]

David Feuer <David_Feuer@brown.edu> said:
> What is the current status of PC-card support?  I've seen ominous signs on 
> this list about the state of support....  I have a laptop with a PCMCIA 
> network card (a 3com thing). Will it work?

I've got a Toshiba Satellite Pro 4280xdvd + 3com cardbus 10/100 card. Works
fine with Red Hat 7, and also with 2.2.18pre20 + latest pcmcia-cs tools (X
doesn't work out of the box, I had to grab an X server from somewhere for
the S3 Savage IX the machine has. The builtin Lucent winmodem is hopeless,
BTW: The Lucent drivers just crash the kernel once the call is answered.)
--
Horst von Brand                             vonbrand@sleipnir.valparaiso.cl
Casilla 9G, Vin~a del Mar, Chile                               +56 32 672616
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

PCMCIA

[Ryan Boder]

Does the rev-15 kernel from BenH's website support pcmcia flash memory
cards?

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

PCMCIA

[Nguyen Xuan Hoang]

Hi All,

I love this mail list, you are all very friendly... could anyone tell which PCMCIA device have worked with RPX Lite board I am interrest in Modem and HDD PCMCIA
where can I find the driver... Yes, I have gone though the mail list but as Dan said we seldom hear from the people who are happy...

Best regards
Hoang

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

Re: PCMCIA

[Jo-Ellen F. Mathews]

On Thu, 23 Dec 1999, Nguyen Xuan Hoang wrote:

>
> Hi All,
>
> I love this mail list, you are all very friendly... could anyone tell
> which PCMCIA device have worked with RPX Lite board I am interrest in
> Modem and HDD PCMCIA where can I find the driver... Yes, I have gone
> though the mail list but as Dan said we seldom hear from the people who
> are happy...

Greetings Hoang and list members,

I will certainly chime in with a happy story.  We do have our IEEE 802.11B
11Mbps wireless LAN PCMCIA device driver working on the RPX Lite (MPC823).
If anyone is attending the O'Reilly Open Source Software Convention (July
17-20, 2000), we'll be doing a wireless LAN tutorial based on our
linux-wlan Open Source project where we will demo the RPX Lite running as
a wireless device with an 11Mbps wireless LAN PCMCIA card in it.

This effort of successfully porting our linux-wlan driver to the RPX Lite
was because of the generous help of people on this list.  It wasn't easy,
and without the help of people on this list, we might still be banging our
heads against the wall.  :-)

I used Magnus Damm's PCMCIA code (that he so generously offered) and the
1.0 distribution of MontaVista's Hard Hat Linux.  I had to make two minor
changes to Magnus' code so it would work with 3.3 volt PCMCIA devices.
Additionally, there were a few edits to kernel source as directed by
Magnus. All of what I did is documented on our ftp site.

While I can't help you with device drivers for the PCMCIA devices you
mentioned, if you need a starting point for PCMCIA support, you're welcome
to download my notes and the files I used:

ftp://ftp.absoval.com/pub/rpxlite

We have moved our web site, and should anyone run into any trouble
accessing our web site or ftp site, e-mail me at 'jo-ellen@linux-wlan.com'
telling me which files you need.

>From someone who is VERY HAPPY (and may have 'accidentally' forgotten to
tell the list),
Jo-Ellen Mathews

---------------------------------------------------------
Jo-Ellen F. Mathews

AbsoluteValue Systems      Web:    http://www.linux-wlan.com
P.O. Box 941149            e-mail: jo-ellen@linux-wlan.com
Maitland, FL 32794-1149    Phone:  407.644.8582
USA                        Fax:    407.539.1294


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