From: Jens Axboe <axboe@suse.de>
To: Randy Dunlap <randy_d_dunlap@linux.intel.com>
Cc: jhpark@tuhep.phys.tohoku.ac.jp, linux-ide@vger.kernel.org,
jgarzik@pobox.com, chris@powerblogs.com
Subject: Re: [PATCH 0/5] SATA/ACPI suspend/resume support
Date: Wed, 4 Jan 2006 08:36:55 +0100 [thread overview]
Message-ID: <20060104073655.GJ3472@suse.de> (raw)
In-Reply-To: <20060103140252.52ebd7d9.randy_d_dunlap@linux.intel.com>
On Tue, Jan 03 2006, Randy Dunlap wrote:
> On Tue, 3 Jan 2006 22:16:11 +0100
> Jens Axboe <axboe@suse.de> wrote:
>
> > > At least it shows that there is no _GTF at all for SATA devices,
> > > only for PATA (which my patch does not address).
> >
> > Aren't they the same thing? Any plans on checking that as well, I think
> > there's a fair share of pata-on-sata laptops out there.
>
> It certainly would be Good to have that supported.
> I'll take a look at the ACPI (3.0) spec to see what (more)
> is needed.
It's all very confusing. Is it just a questions of checking which _GTF's
to query? You can use ata_dev_knobble() to check whether this is an SATA
or PATA drive. The rest of the code should be the same.
> BTW, there's a different IDE-ACPI patch from
> Shaohua Li <shaohua.li@intel.com>. Have you seen it?
> Has anyone here tested it?
> http://marc.theaimsgroup.com/?l=linux-kernel&m=113390716128790&w=2
I hadn't seen it before. I have no real pata + acpi suspending machines,
though.
--
Jens Axboe
next prev parent reply other threads:[~2006-01-04 7:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-27 23:34 [PATCH 0/5] SATA/ACPI suspend/resume support Randy Dunlap
2005-12-30 8:36 ` Jae-hyeon Park
2006-01-03 17:08 ` Randy Dunlap
2006-01-03 17:26 ` Jens Axboe
2006-01-03 19:03 ` Jens Axboe
2006-01-03 19:06 ` Randy Dunlap
2006-01-03 19:57 ` Randy Dunlap
2006-01-03 20:06 ` Jens Axboe
2006-01-03 20:11 ` Randy Dunlap
2006-01-03 20:13 ` Jens Axboe
2006-01-03 21:00 ` Randy Dunlap
2006-01-03 21:16 ` Jens Axboe
2006-01-03 22:02 ` Randy Dunlap
2006-01-04 7:36 ` Jens Axboe [this message]
2006-01-03 22:40 ` Jae-hyeon Park
2006-01-04 0:40 ` Randy Dunlap
2006-01-04 1:31 ` Jae-hyeon Park
2006-01-04 18:13 ` Randy Dunlap
2006-01-04 18:57 ` Randy Dunlap
2006-01-04 19:42 ` Randy Dunlap
2006-01-05 14:08 ` Jae-hyeon Park
2006-01-05 18:36 ` Randy Dunlap
2006-01-06 1:02 ` Jae-hyeon Park
2006-01-06 1:10 ` Randy Dunlap
2006-01-06 20:43 ` Randy Dunlap
2006-01-07 13:11 ` Jae-hyeon Park
2006-01-07 16:55 ` Randy.Dunlap
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=20060104073655.GJ3472@suse.de \
--to=axboe@suse.de \
--cc=chris@powerblogs.com \
--cc=jgarzik@pobox.com \
--cc=jhpark@tuhep.phys.tohoku.ac.jp \
--cc=linux-ide@vger.kernel.org \
--cc=randy_d_dunlap@linux.intel.com \
/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).