mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kyle Moffett <mrmacman_g4@mac.com>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: Steve Snyder <swsnyder@insightbb.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PCMCIA still advised as modules?
Date: Sat, 11 Jun 2005 17:08:08 -0400	[thread overview]
Message-ID: <73AF5410-0EF8-4F1B-BE13-DB1F22B875DD@mac.com> (raw)
In-Reply-To: <20050610122105.GA13931@isilmar.linta.de>

On Jun 10, 2005, at 08:21:05, Dominik Brodowski 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.

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


  reply	other threads:[~2005-06-11 21:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-10 12:11 Steve Snyder
2005-06-10 12:21 ` Dominik Brodowski
2005-06-11 21:08   ` Kyle Moffett [this message]
2005-06-12  7:41     ` Dominik Brodowski
2005-06-15 14:39   ` Dick Streefland

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=73AF5410-0EF8-4F1B-BE13-DB1F22B875DD@mac.com \
    --to=mrmacman_g4@mac.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    --cc=swsnyder@insightbb.com \
    /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

all inboxes | Powered by JetHome®