From: Mark Lord <liml@rtr.ca>
To: "zhao, forrest" <forrest.zhao@intel.com>
Cc: jgarzik@pobox.com, rdunlap@xenotime.net, htejun@gmail.com,
linux-ide@vger.kernel.org
Subject: Re: [PATCH 0/2]ACPI support for SATA/PATA
Date: Thu, 27 Jul 2006 14:03:48 -0400 [thread overview]
Message-ID: <44C90004.4030400@rtr.ca> (raw)
In-Reply-To: <1153964697.4957.67.camel@forrest26.sh.intel.com>
zhao, forrest wrote:
> On Wed, 2006-07-26 at 11:14 -0400, Mark Lord wrote:
>> zhao, forrest wrote:
>>> Hello, all
>>>
>>> In ACPI spec 3.0, section 9.9 defines 4 objects for PATA/SATA:
>>>
>>> _GTF is for both PATA and SATA, which is used to return ATA task file
>>> needed to re-init the drive;
>>> _SDD is SATA-only object, which is used to inform the platform of the
>>> type of device attached to a port;
>>> _GTM and _STM are PATA-only objects, which are used to get/set PATA
>>> timing information(i.e. PIO and DMA speed).
>> It seems to be quite common for ICH*M notebooks to use the SATA ports
>> to attach PATA drives with PATA->SATA bridge chips in the middle.
>>
>> In this case, one would expect the _GTM and _STM objects to be necessary,
>> even though Linux thinks it's a SATA situation.
>>
>
> Hi Mark,
>
> I re-read the section 9.9 of ACPI spec 3.0, but didn't find any
> description about how to deal with "PATA->SATA bridge". Is this version
> of APCI spec outdated?
> Would you please point me to spec(or document), which has the
> description of how to deal with "PATA->SATA bridge"?
I don't have any documents, just machines that implement it.
Cheers
next prev parent reply other threads:[~2006-07-27 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 7:35 [PATCH 0/2]ACPI support for SATA/PATA zhao, forrest
2006-07-26 15:14 ` Mark Lord
2006-07-27 1:44 ` zhao, forrest
2006-07-27 18:03 ` Mark Lord [this message]
2006-08-08 17:52 ` Randy.Dunlap
2006-08-08 19:14 ` 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=44C90004.4030400@rtr.ca \
--to=liml@rtr.ca \
--cc=forrest.zhao@intel.com \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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.