From: Tejun Heo <htejun@gmail.com>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
ide <linux-ide@vger.kernel.org>,
l.genoni@oltrelinux.com, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: something strange in libata-core.c for kernel 2.6.22-rc3
Date: Mon, 21 May 2007 11:09:03 +0200 [thread overview]
Message-ID: <465161AF.6030002@gmail.com> (raw)
In-Reply-To: <46515983.6030206@shaw.ca>
Robert Hancock wrote:
>> Alan, did you have a chance to test the ACPI cable detection? It just
>> didn't work when I tried it. It always returned 80c on my machine.
>
> On a whim I started poking around in the disassembled ACPI DSDT code for
> my Asus A8N-SLI Deluxe board, which is one of these chipsets. The
> original thought was that the STM/GTM trick on these chipsets is
> supposed to allow us to determine what modes we should use based on what
> modes it sets up appropriately. Unfortunately, unless I'm missing
> something in the AML (which is possible) it doesn't seem like there is
> any validation being done on the settings passed in. The settings appear
> to essentially just get programmed into the controller when STM is
> called and read back on GTM.
Yeah, that's consistent to what I've seen on my machine which is a
variant of A8N. No matter what value I through at _STM, _GTM just
echoed the result thus always leading to 80c configuration.
> I guess this means that what we have to do is trust that the BIOS set up
> a reasonable mode and base the cable detect on that (either by reading
> back the boot-up controller registers, or by calling GTM). I imagine
> this is what the Windows default IDE driver is doing (just using the
> boot-up mode and feeding it back using GTM/STM on suspend/resume cycles).
Alan, what do you think?
--
tejun
next prev parent reply other threads:[~2007-05-21 9:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.MCe9nCgx+WnsHp+weZyM9LiDF0s@ifi.uio.no>
[not found] ` <fa.rv8/6n3uBnAIoUHHNUW3eR7cJd8@ifi.uio.no>
[not found] ` <fa.LXy58QwLlPXDhsfVUU9kEfA3QbI@ifi.uio.no>
2007-05-20 17:18 ` something strange in libata-core.c for kernel 2.6.22-rc3 Robert Hancock
[not found] ` <fa.Ldjy2OubeKomZD0OV2gRm/wpUFo@ifi.uio.no>
2007-05-20 22:27 ` Robert Hancock
2007-05-21 8:34 ` Robert Hancock
2007-05-21 9:09 ` Tejun Heo [this message]
2007-05-21 11:15 ` Alan Cox
2007-05-21 18:14 ` Robert Hancock
2007-05-21 9:41 ` Jeff Garzik
[not found] <Pine.LNX.4.64.0704181704270.1663@Phoenix.oltrelinux.com>
[not found] ` <20070418162525.423b2e7e@the-village.bc.nu>
2007-05-20 12:40 ` l.genoni
2007-05-20 17:31 ` Tejun Heo
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=465161AF.6030002@gmail.com \
--to=htejun@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hancockr@shaw.ca \
--cc=l.genoni@oltrelinux.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).