From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Grozdan <neutrino8@gmail.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
Tejun Heo <tj@kernel.org>
Subject: Re: Kernel 2.6.30rc7 limits IDE to UDMA33
Date: Sat, 6 Jun 2009 23:08:52 +0100 [thread overview]
Message-ID: <20090606230852.200d1432@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <4A2AB298.7020603@gmail.com>
> > Drive side detection doesn't work for many VIA boards, the neccessary
> > components are not included.
>
> Ugh, seems they messed this stuff up as bad as NVIDIA did..
Nvidia seem to have gotten it close to right. The Nvidia chipsets use
ACPI for reporting and only ACPI. The ACPI parts are pretty reliable, its
just if your ACPI is busted....
> Well, that's pretty much the same thing that GTM does (it generally just
> reads the configured mode out of the controller registers). So it really
> wouldn't be much worse than what we're doing now.
>
> Thing is somehow the GTM detection isn't working now and it apparently
> was in 2.6.27.1. I'm not seeing any patches to pata_via or libata-acpi
> that seem like they would affect this offhand. Grozdan, would you be
> able to try git bisect to try to figure out what changed the behavior?
Could be power management. Something is putting devices into D3 that
didn't use to happen. That was what broke the ALi ATA driver and I could
believe a D3 transition of the IDE controller broke the BIOS
configuration.
next prev parent reply other threads:[~2009-06-06 22:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c5bd819b0906021525l13ee9282j1fb270e141985f66@mail.gmail.com>
2009-06-03 4:05 ` Kernel 2.6.30rc7 limits IDE to UDMA33 Robert Hancock
2009-06-03 11:35 ` Grozdan
2009-06-03 12:14 ` Alan Cox
2009-06-03 12:52 ` Grozdan
2009-06-03 13:01 ` Alan Cox
2009-06-03 13:15 ` Grozdan
2009-06-03 13:39 ` Grozdan
2009-06-04 14:50 ` Grozdan
2009-06-05 9:05 ` Alan Cox
2009-06-05 10:35 ` Grozdan
2009-06-05 10:42 ` Alan Cox
2009-06-05 12:43 ` Grozdan
2009-06-05 13:21 ` Alan Cox
2009-06-05 14:02 ` Grozdan
2009-06-06 1:07 ` Robert Hancock
2009-06-06 14:56 ` Alan Cox
2009-06-06 18:16 ` Robert Hancock
2009-06-06 22:08 ` Alan Cox [this message]
2009-06-07 4:39 ` Grozdan
[not found] ` <4A2BF785.3020402@gmail.com>
2009-06-07 18:24 ` Grozdan
2009-06-07 18:46 ` Michael S. Zick
2009-06-07 19:54 ` 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=20090606230852.200d1432@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=hancockrwd@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neutrino8@gmail.com \
--cc=tj@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