From: Mark Lord <liml@rtr.ca>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-ide@vger.kernel.org, torvalds@osdl.org
Subject: Re: [PATCH alt4 v3] libata resume fixes
Date: Sat, 27 May 2006 17:15:10 -0400 [thread overview]
Message-ID: <4478C15E.5030500@rtr.ca> (raw)
In-Reply-To: <4478C08B.60308@garzik.org>
Jeff Garzik wrote:
> Mark Lord wrote:
>
>> The ACPI patches have indeed been working here for over a year now,
>> on all kernels up to 2.6.15 --> not needed for 2.6.16.
>
> Long term they are definitely needed, if only for the case where a drive
> password has been set in BIOS. Otherwise when you resume, you won't be
> able to talk to your disk. Additionally the preferences (such drive
> acoustic settings) aren't reprogrammed, but that is of lesser importance.
>
> On laptops, the ACPI tables sometimes also hold special vendor-specific
> taskfiles to work around device-specific or drive-firmware-specific
> problems.
Agreed, 100%.
So why aren't they in yet? ;)
next prev parent reply other threads:[~2006-05-27 21:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-27 19:58 [PATCH alt4] libata resume fixes Jeff Garzik
2006-05-27 20:10 ` [PATCH alt4 v2] " Jeff Garzik
2006-05-27 20:14 ` Jeff Garzik
2006-05-27 20:30 ` Mark Lord
[not found] ` <4478B611.2030201@rtr.ca>
2006-05-27 20:32 ` Jeff Garzik
2006-05-27 20:41 ` Mark Lord
2006-05-27 20:56 ` Jeff Garzik
2006-05-27 21:00 ` Mark Lord
2006-05-27 21:06 ` Jeff Garzik
2006-05-27 21:09 ` Mark Lord
2006-05-27 21:14 ` Jeff Garzik
2006-05-27 20:13 ` [PATCH alt4] " Mark Lord
2006-05-27 20:52 ` [PATCH alt4 v3] " Jeff Garzik
2006-05-27 20:56 ` Mark Lord
2006-05-27 21:11 ` Jeff Garzik
2006-05-27 21:15 ` Mark Lord [this message]
2006-05-27 21:25 ` Jeff Garzik
2006-05-27 21:12 ` Mark Lord
2006-05-27 21:21 ` Jeff Garzik
2006-05-29 3:53 ` zhao, forrest
2006-05-29 5:25 ` Jeff Garzik
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=4478C15E.5030500@rtr.ca \
--to=liml@rtr.ca \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).