From: Robert Hancock <hancockr@shaw.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
Dave Jones <davej@codemonkey.org.uk>,
linux-ide@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Remove Asus EEE UDMA/33 limitation.
Date: Sat, 03 May 2008 13:34:14 -0600 [thread overview]
Message-ID: <481CBE36.6040007@shaw.ca> (raw)
In-Reply-To: <fa.ulFofhLJhFFkP/xiWxdfjwM8XDA@ifi.uio.no>
Alan Cox wrote:
> On Sat, 3 May 2008 10:58:17 +0100
> Matthew Garrett <mjg59@srcf.ucam.org> wrote:
>
>> On Fri, May 02, 2008 at 11:44:58AM -0400, Dave Jones wrote:
>>
>>> static const struct ich_laptop ich_laptop[] = {
>>> /* devid, subvendor, subdev */
>>> + { 0x2653, 0x1043, 0x82d8 }, /* ICH6M on Asus Eee PC */
>>> { 0x27DF, 0x0005, 0x0280 }, /* ICH7 on Acer 5602WLMi */
>>> { 0x27DF, 0x1025, 0x0102 }, /* ICH7 on Acer 5602aWLMi */
>>> { 0x27DF, 0x1025, 0x0110 }, /* ICH7 on Acer 3682WLMi */
>> Don't the ACPI timing methods let us work this out without requiring
>> machine specific knowledge?
>
> We don't currently sniff the ACPI timing data on Intel boxes - we can do
> so and there is a library routine but I'd be worried about the usual
> standard of BIOS code. Right now we only do it for chipsets which are so
> braindamaged we have no other choice or where the vendor specifically
> implemented and intended the ACPI data to be used for this (eg Nvidia)
Given that the bootup ACPI _GTM results will be used by Windows to
determine the DMA mode setting with the standard Microsoft atapi.sys
driver which PATA controllers would typically use, and Windows is what
the majority of this hardware was designed to run, I think it should be
quite trustworthy..
next parent reply other threads:[~2008-05-03 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.tsKjLRZd5ILFUSCwKgwjuJUvN+Y@ifi.uio.no>
[not found] ` <fa.l6LkASoBXPmhrri16ok+xTRwEUY@ifi.uio.no>
[not found] ` <fa.ulFofhLJhFFkP/xiWxdfjwM8XDA@ifi.uio.no>
2008-05-03 19:34 ` Robert Hancock [this message]
2008-05-02 15:44 Remove Asus EEE UDMA/33 limitation Dave Jones
2008-05-02 16:44 ` Dave Jones
2008-05-03 9:58 ` Matthew Garrett
2008-05-03 14:51 ` Alan Cox
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=481CBE36.6040007@shaw.ca \
--to=hancockr@shaw.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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).