[ Next-in-Thread ]  [ Next Message ] 

Question: i82365 and wvlan_cs with 2.4.0-test5? 

Forum: PCMCIA Installation and Configuration Issues
Date: 2000, Jul 29
From: Peter pfolk

I must not understand something. When I try to build either 3.1.19 or the .20 beta against kernel 2.4.0-test5, it doesn't build most of the stuff. In particular, it doesn't build either of the i82365.o or wvlan_cs.o modules, or anything in the modules or wireless subdirectories.

In kernel test5's drivers/pcmcia/Config.in, the configure option for i82365 support is commented out so I can't enable it in that location, but if I do I get no problems. Similarly, I can manually build the wvlan_cs module. In- stalling it causes no problems that I can see, and this is not listed as a bug as far as I can tell...

So is this a relic, or am I doing something wrong, or does it only seem like it's working fine, or what?

Pete

[ Next-in-Thread ]  [ Next Message ] 

Messages Inline: [ 0 ]  [ 1 ] 

If you want those modules, then turn off PCMCIA in your kernel

Re: Question: i82365 and wvlan_cs with 2.4.0-test5? (Peter)
Date: 2000, Jul 30
From: David Hinds <dhinds@pcmcia.sourceforge.org>

In general, you either build the kernel-tree PCMCIA support, or you
build the standalone PCMCIA modules.  The Configure script checks to
see if CONFIG_PCMCIA is turned on in your kernel; if it is, then it
will only build cardmgr and the other user tools.  If CONFIG_PCMCIA is
off, then it will build all the kernel modules.

The reason for this is that there may be version skew between the
PCMCIA stuff in the kernel tree, and what is in the separate package.
If the kernel PCMCIA is on, then cardmgr etc are built against the
kernel PCMCIA headers, not the headers included in the PCMCIA
package.  Building the modules, when you've also built stuff into the
kernel, is messy: we don't want to build stuff that conflicts.

-- Dave

Ok: Cool, perhaps that could be made more clear in the HOWTO?

Re: If you want those modules, then turn off PCMCIA in your kernel (David Hinds)
Date: 2000, Jul 30
From: Peter pfolk

I know you say it for the individual devices and device types, but maybe before that section, make it clear that you can only use ONE of the two for the modules.

Pete

Question: Why ?

Re: Question: i82365 and wvlan_cs with 2.4.0-test5? (Peter)
Date: 2000, Aug 16
From: Serge Wagener Foxi

I have the same problem with test6 and 3.1.19. The i82365 doesn't show up in modules directory.

I now know why (reading this thread) but can someone tell me WHY the i82365 is turned off in test6 kernel tree ??

Is it safe to uncomment it in Config.in or is it safer to disable pcmcia support and completely use the pcmcia-cs package ?

Serge

You can't just uncomment the config option

Re: Question: Why ? (Serge Wagener)
Date: 2000, Aug 16
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You cannot use the i82365 module in test6 and later, because the way
the pcmcia_core module interacts with socket drivers was changed
drastically, and the i82365 and tcic modules were not fixed to use the
new system.  Only the yenta driver was updated.  I didn't make these
changes.

-- Dave
i82365 and wvlan_cs with 2.4.0-test5?


[ Add Message ]  to: "i82365 and wvlan_cs with 2.4.0-test5?"

[ Members ]  [ Subscribe ]  [ Admin Mode ] 
[ Show Frames ]  [ Help for HyperNews at pcmcia-cs.sourceforge.net 1.10 ]