Skip to contentSkip to conversation

PCMCIA still advised as modules?

DISCUSSION Steve Snyder 4 participants 5 messages Jun 10, 2005 – Jun 15, 2005

lore
Share & tools
lore
#0 lore raw

Back in the 2.4.x kernel days I was advised to build the PCMCIA-related drivers (pcmcia_core, ds, yenta_socket) as modules. There were supposedly problem with them being staticly built into the kernel.

Is this still the case? Are there currently any drawbacks to having the PCMCIA modules built into the kernel?

Thanks.

#1 lore raw
Quoted 6 lines · Steve Snyder

Back in the 2.4.x kernel days I was advised to build the PCMCIA-related drivers (pcmcia_core, ds, yenta_socket) as modules. There were supposedly problem with them being staticly built into the kernel.

Is this still the case? Are there currently any drawbacks to having the PCMCIA modules built into the kernel?

At least from 2.6.13 on, it will be much easier if you have the PCMCIA "modules" built into the kernel, as you won't need userspace interaction any longer (except on old yenta_socket bridges during startup, but that's a different story). Therefore, I do not see any drawbacks to having the PCMCIA modules built into the kernel.

Dominik

#2 lore raw
Quoted 5 lines · Dominik Brodowski

At least from 2.6.13 on, it will be much easier if you have the PCMCIA "modules" built into the kernel, as you won't need userspace interaction any longer (except on old yenta_socket bridges during startup, but that's a different story). Therefore, I do not see any drawbacks to having the PCMCIA modules built into the kernel.

Under such a setup, what is the easiest method to shut down the bridge chip for power savings? On my Debian laptop where said drivers are modular, I can run "/etc/init.d/pcmcia stop" to unload the module and disable the PCMCIA chip, saving a noticeable amount of power. Is there some equivalent for compiled-in drivers? Thanks!

Cheers,
Kyle Moffett

Somone asked my why I work on this free (http://www.fsf.org/philosophy/)
software stuff and not get a real job. Charles Shultz had the best answer:

"Why do musicians compose symphonies and poets write poems? They do it because life wouldn't have any meaning for them if they didn't. That's why I draw cartoons. It's my life." -- Charles Shultz

#3 lore raw
Quoted 10 lines · Kyle Moffett
Quoted 8 lines · Dominik Brodowski

At least from 2.6.13 on, it will be much easier if you have the PCMCIA "modules" built into the kernel, as you won't need userspace interaction any
longer (except on old yenta_socket bridges during startup, but that's a
different story). Therefore, I do not see any drawbacks to having the PCMCIA
modules built into the kernel.

Quoted 9 lines

Under such a setup, what is the easiest method to shut down the bridge chip
for power savings? On my Debian laptop where said drivers are modular, I can
run "/etc/init.d/pcmcia stop" to unload the module and disable the PCMCIA chip,
saving a noticeable amount of power. Is there some equivalent for compiled-in
drivers? Thanks!

You can do "cardctl suspend" or (untested) echo "3" into the "power/state" file of the relevant device inside the sysfs device tree ("/sys/devices/").

Dominik

#4 lore raw
In reply to Dominik Brodowski

Dominik Brodowski <[email protected]> wrote:

| At least from 2.6.13 on, it will be much easier if you have the PCMCIA
| "modules" built into the kernel, as you won't need userspace interaction any
| longer (except on old yenta_socket bridges during startup, but that's a
| different story). Therefore, I do not see any drawbacks to having the PCMCIA
| modules built into the kernel.

At least the aha152x_cs module cannot be compiled into the kernel, the Kconfig file says: depends on m. Does anybody known what the problem with this driver is?

Signature · 3 lines
Dick Streefland                      ////                      Altium BV
[email protected]           (@ @)          http://www.altium.com
--------------------------------oOO--(_)--OOo---------------------------