linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jeff@garzik.org>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] pata_amd: remove contamination added during cable_detect conversion
Date: Mon, 23 Apr 2007 02:51:33 +0900	[thread overview]
Message-ID: <462BA0A5.2080900@gmail.com> (raw)
In-Reply-To: <20070422184037.537ae748@the-village.bc.nu>

Hello,

Alan Cox wrote:
> On Mon, 23 Apr 2007 02:04:38 +0900
> Tejun Heo <htejun@gmail.com> wrote:
> 
>> This is added by added by cff63dfceb52c564fe1ba5394d50ab7d599a11b9
>>  - pata: cable methods.
> 
> The Cable method fix for the Nvidia hardware if ACPI drivers are present
> and usable is to use the ACPI driver, so its not a "contamination" its a
> fix for the fact the Nvidia code can't do cable detect any other way

But pata_amd modifications should be merged together with pata_acpi not
separately.

Anyways, I've been testing pata_acpi and it doesn't work on my nforce
ultra machine.  Whether the cable is 40c or not, _STM happily sets UDMA
mode above 2 resulting in a series of transfer errors.  EH kicks in
eventually and drops transfer speed.

Also, ata_acpi_gtm() implementation was broken in that it skipped one
level of indirection (acpi_object, please take a look at the last patch
of just posted patchset), so it was basically returning garbage values.

I have patches to update pata_amd to use _STM/_GTM for cable detection
(a lot are taken from pata_acpi) but ACPI cable detection is just as
broken as PCI config one.

Thanks.

-- 
tejun

  reply	other threads:[~2007-04-22 17:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-22 17:04 [PATCH] pata_amd: remove contamination added during cable_detect conversion Tejun Heo
2007-04-22 17:40 ` Alan Cox
2007-04-22 17:51   ` Tejun Heo [this message]
2007-04-22 17:59     ` Alan Cox
2007-04-22 18:14       ` Tejun Heo
2007-04-22 18:20         ` Alan Cox
2007-04-28 18:46 ` Jeff Garzik

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=462BA0A5.2080900@gmail.com \
    --to=htejun@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jeff@garzik.org \
    --cc=linux-ide@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).