From: David Brownell <david-b@pacbell.net>
To: Tobias Diedrich <ranma+kernel@tdiedrich.de>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Ayaz Abdulla <aabdulla@nvidia.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Stephen Hemminger <shemminger@linux-foundation.org>,
linux-acpi@vger.kernel.org, linux-pm@lists.linux-foundation.org
Subject: Re: [PATCH 0/4] Fix forcedeth hibernate/wake-on-lan problems
Date: Tue, 27 May 2008 14:32:12 -0700 [thread overview]
Message-ID: <200805271432.12881.david-b@pacbell.net> (raw)
In-Reply-To: <20080527062153.GA3651@yamamaya.is-a-geek.org>
On Monday 26 May 2008, Tobias Diedrich wrote:
> The platform_enable_wakeup() hook is still there, but unused.
The patches to support it (still) haven't been merged.
> AFAICS this patch should solve the "'ethtool -s eth0 wol g' doesn't
> suffice, I also have to write magic values into /proc/acpi/wakeup"
> issue.
Yeah; under ACPI, PCI does not act like it does everywhere else.
Nor does wakeup in general.
After sending patches to fix that for a couple years now, I'm
well past being tired of doing that. I suggest it's overdue for
the ACPI team to get this part of their act together.
That is: either start merging those patches, possibly with updates
to handle broken hardware better; or rewrite them; ... or just say
explicitly the message I've been receiving: "Linux ACPI will never
support wakeup the way the rest of Linux can and does". (And the
"why" should be something reasonable.)
next prev parent reply other threads:[~2008-05-27 21:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080518125715.GA19229@yamamaya.is-a-geek.org>
[not found] ` <20080518150908.GA4606@yamamaya.is-a-geek.org>
[not found] ` <20080525150444.GA29739@yamamaya.is-a-geek.org>
[not found] ` <20080525181329.GA5044@yamamaya.is-a-geek.org>
2008-05-27 6:21 ` [PATCH 0/4] Fix forcedeth hibernate/wake-on-lan problems Tobias Diedrich
[not found] ` <20080527062153.GA3651@yamamaya.is-a-geek.org>
2008-05-27 21:32 ` David Brownell [this message]
2008-05-31 7:20 ` Pavel Machek
2008-06-05 2:38 ` David Brownell
2008-05-31 22:12 ` Tobias Diedrich
2008-06-01 2:51 ` [linux-pm] " Alan Stern
2008-06-01 7:49 ` Tobias Diedrich
2008-06-02 21:09 ` Alan Stern
2008-06-03 6:16 ` Tobias Diedrich
2008-06-03 14:12 ` Alan Stern
2008-06-03 17:30 ` Tobias Diedrich
2008-06-03 20:06 ` Alan Stern
2008-05-31 23:20 ` [PATCH 6/4] " Tobias Diedrich
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=200805271432.12881.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=aabdulla@nvidia.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=ranma+kernel@tdiedrich.de \
--cc=rjw@sisk.pl \
--cc=shemminger@linux-foundation.org \
/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