From: Len Brown <len.brown@intel.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: "Arjan van de Ven" <arjan@infradead.org>,
"Pavel Machek" <pavel@ucw.cz>,
"Frédéric Riss" <frederic.riss@gmail.com>,
"Linux Kernel list" <linux-kernel@vger.kernel.org>,
"Linus Torvalds" <torvalds@osdl.org>
Subject: Re: 2.6.18 suspend regression on Intel Macs
Date: Wed, 11 Oct 2006 02:37:54 -0400 [thread overview]
Message-ID: <200610110237.54906.len.brown@intel.com> (raw)
In-Reply-To: <20061010212853.GC31972@srcf.ucam.org>
On Tuesday 10 October 2006 17:28, Matthew Garrett wrote:
> On Tue, Oct 10, 2006 at 12:41:28PM +0200, Arjan van de Ven wrote:
>
> > "fix" for some value of the word.
> > The problem is that this is very much against the spec, and also quite
> > likely breaks a bunch of machines...
>
> It works fine under Windows, which suggests that the Windows behaviour
> is to reenable the bit.
To me it suggests that both Windows and MacOS provoke the firmware
to re-enable this bit -- it doesn't suggest that the OS is doing it.
> I wouldn't really expect any existing hardware
> to expect any other sort of behaviour.
I would. In the known universe, the Mac-mini is the only machine that
seems to need us to explicitly set SCI_EN.
-Len
prev parent reply other threads:[~2006-10-11 6:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 18:19 2.6.18 suspend regression on Intel Macs Frédéric Riss
2006-10-10 10:39 ` Pavel Machek
2006-10-10 10:41 ` Arjan van de Ven
2006-10-10 10:49 ` Pavel Machek
2006-10-10 15:33 ` Linus Torvalds
2006-10-10 19:08 ` Frédéric Riss
2006-10-10 19:38 ` Arjan van de Ven
2006-10-10 19:46 ` Frédéric Riss
2006-10-10 19:50 ` Pavel Machek
2006-10-10 21:49 ` Linus Torvalds
2006-10-10 22:09 ` Frédéric Riss
2006-10-10 23:53 ` Linus Torvalds
2006-10-11 6:09 ` Frédéric Riss
2006-10-11 13:16 ` suspend debugging " Pavel Machek
2006-10-11 6:35 ` Len Brown
2006-10-11 14:35 ` Linus Torvalds
2006-10-10 21:28 ` Matthew Garrett
2006-10-11 6:37 ` Len Brown [this message]
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=200610110237.54906.len.brown@intel.com \
--to=len.brown@intel.com \
--cc=arjan@infradead.org \
--cc=frederic.riss@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=pavel@ucw.cz \
--cc=torvalds@osdl.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 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.