From: Adam Belay <ambx1@neo.rr.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: matthieu castet <castet.matthieu@free.fr>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: PNP parallel&serial ports: module reload fails (2.6.11)?
Date: Tue, 14 Jun 2005 15:40:16 -0400 [thread overview]
Message-ID: <20050614194016.GA5351@neo.rr.com> (raw)
In-Reply-To: <42A8AFA5.3090703@tls.msk.ru>
On Fri, Jun 10, 2005 at 01:07:49AM +0400, Michael Tokarev wrote:
>
> First of all, why disable the device on module unload?
> If it was enabled initially, before any module has been
> loaded, why it needs to be disabled, why not leave it
> enabled and all, just like it has been before?
The original idea here was to free up resources for allocation
to other devices. The ACPI spec claims we should call _DIS
when powering down the device to _D3. So, I'm considering not
disabling the device when the driver is unbound, especially with
PNPACPI. I need to think about it more.
Thanks,
Adam
next prev parent reply other threads:[~2005-06-14 19:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 22:24 Re:PNP parallel&serial ports: module reload fails (2.6.11)? castet.matthieu
2005-06-03 0:18 ` PNP " Michael Tokarev
2005-06-03 5:58 ` matthieu castet
2005-06-05 10:14 ` matthieu castet
2005-06-05 10:27 ` matthieu castet
2005-06-06 15:01 ` Michael Tokarev
2005-06-06 15:43 ` castet.matthieu
2005-06-06 21:18 ` Adam Belay
2005-06-06 22:43 ` Michael Tokarev
2005-06-08 9:52 ` Adam Belay
2005-06-08 20:29 ` Michael Tokarev
2005-06-08 23:52 ` Adam Belay
2005-06-09 21:07 ` Michael Tokarev
2005-06-09 21:16 ` Russell King
2005-06-10 16:01 ` Bjorn Helgaas
2005-06-10 16:20 ` Dmitry Torokhov
2005-06-10 16:26 ` Bjorn Helgaas
2005-06-10 16:30 ` Russell King
2005-06-14 19:40 ` Adam Belay [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-31 23:01 Michael Tokarev
2005-06-01 5:04 ` Andrew Morton
2005-06-01 15:20 ` Michael Tokarev
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=20050614194016.GA5351@neo.rr.com \
--to=ambx1@neo.rr.com \
--cc=akpm@osdl.org \
--cc=castet.matthieu@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.