From: Alan Cox <alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>
To: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Resuming IDE devices with ACPI
Date: Mon, 09 May 2005 17:01:33 +0100 [thread overview]
Message-ID: <1115654492.1448.37.camel@localhost.localdomain> (raw)
In-Reply-To: <1115646660.27559.16.camel-Xmbc1Sz64/5pghhO6/9/sx2eb7JE58TQ@public.gmane.org>
On Llu, 2005-05-09 at 14:51, Matthew Garrett wrote:
> which makes it unsurprising that hardware without working IDE on resume
> is continuing to appear. In order to resume it, we need to be able to
> make the appropriate taskfile calls with the output of the _GTF method.
> For this to be possible, we need to call each IDE controller's _GTF
> method on resume. How can we associate each IDE controller with a given
> piece of ACPI namespace?
We do know the resource allocations of each controller.
You also then have to retune the drives etc and resume operations having
checked various things like drive model/id to spot cold plugs (otherwise
if you get the BIOS numbering wrong or something moves you'll do serious
damage to the
users data)
Alan
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
next prev parent reply other threads:[~2005-05-09 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 13:51 Resuming IDE devices with ACPI Matthew Garrett
[not found] ` <1115646660.27559.16.camel-Xmbc1Sz64/5pghhO6/9/sx2eb7JE58TQ@public.gmane.org>
2005-05-09 16:01 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-10 0:55 Li, Shaohua
[not found] ` <16A54BF5D6E14E4D916CE26C9AD3057501E5F857-4yWAQGcml66iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2005-05-10 8:17 ` Matthew Garrett
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=1115654492.1448.37.camel@localhost.localdomain \
--to=alan-qbu/x9rampvanceybjwyrvxrex20p6io@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.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