From: "Bartlomiej Zolnierkiewicz" <bzolnier@gmail.com>
To: "Tejun Heo" <htejun@gmail.com>
Cc: Alan <alan@lxorguk.ukuu.org.uk>,
"Allen Martin" <AMartin@nvidia.com>,
linux-ide@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Nvidia cable detection problems (was [PATCH] amd74xx: don't configure udma mode higher than BIOS did)
Date: Mon, 5 Feb 2007 22:27:59 +0100 [thread overview]
Message-ID: <58cb370e0702051327p7b253dafs439c937093ca837d@mail.gmail.com> (raw)
In-Reply-To: <58cb370e0702051055w3c7dcff3wd3e3b4935b910b41@mail.gmail.com>
On 2/5/07, Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
> > > Well we can certainly do some of that if ACPI is present and active. In
> > > particular since _GTM will give us current modes allowing for hotplug and
> > > post BIOS boot kexec etc it ought to be safe to do Tejun's hack that way.
> > > We could even probe UDMA3+ capable devices by doing _STM to a high mode
> > > and _GTM to determine the cable type 8)
>
> agreed
New look at the issue:
Since we are already using UDMA mode set by BIOS to determine if 80c cable
is present so why not also use it to determine if the 40c cable is present?
I mean just ignoring AMD_CABLE_DETECT register for NVIDIA devices.
2-lines change and we wouldn't have to deal with ACPI at ell.
What do you think?
Bart
next prev parent reply other threads:[~2007-02-05 21:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070205075836.GG1625@htj.dyndns.org>
[not found] ` <20070205112410.5a3c3182@localhost.localdomain>
[not found] ` <45C72012.7050605@gmail.com>
[not found] ` <20070205132247.6f611e3c@localhost.localdomain>
[not found] ` <45C73A3E.6080700@gmail.com>
2007-02-05 14:34 ` Alan
2007-02-05 14:50 ` Tejun Heo
2007-02-05 15:49 ` Alan
[not found] ` <58cb370e0702050709w1b7682dr5dff9e7ce69465a@mail.gmail.com>
2007-02-05 17:08 ` Allen Martin
2007-02-05 18:12 ` Alan
2007-02-05 18:36 ` Tejun Heo
2007-02-05 18:55 ` Bartlomiej Zolnierkiewicz
2007-02-05 19:15 ` Tejun Heo
2007-02-05 21:27 ` Bartlomiej Zolnierkiewicz [this message]
2007-02-05 22:02 ` Alan
2007-02-05 22:00 ` Bartlomiej Zolnierkiewicz
2007-02-05 19:13 ` Alan
2007-02-05 21:43 ` Jeff Garzik
2007-02-05 21:11 ` Nvidia cable detection problems & ACPI (beware, slight off-top) Oleg Verych
2007-02-05 22:04 ` Alan
2007-02-05 21:55 ` Jeff Garzik
2007-02-05 22:42 ` Oleg Verych
2007-02-05 22:51 ` 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=58cb370e0702051327p7b253dafs439c937093ca837d@mail.gmail.com \
--to=bzolnier@gmail.com \
--cc=AMartin@nvidia.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.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
all inboxes | Powered by JetHome®