From: Robert Hancock <hancockr@shaw.ca>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jeff@garzik.org>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI driver support for pata
Date: Thu, 22 Feb 2007 18:15:03 -0600 [thread overview]
Message-ID: <45DE3207.6020707@shaw.ca> (raw)
In-Reply-To: <20070222182939.56d43a68@lxorguk.ukuu.org.uk>
Alan wrote:
> On Thu, 22 Feb 2007 12:11:32 -0500
> Jeff Garzik <jeff@garzik.org> wrote:
>
>> Alan wrote:
>>> ACPI is the only way to do cable handling on the Nvidia PATA chipset. The
>> You failed to quote the salient part of the message. Disliking a
>> separate pata_acpi driver in no way invalidates your statement (quoted
>> above).
>
> If you drive a device by the ACPI interface you don't get to fiddle with
> it directly or you end up in a murky world of undefined and ungood
> behaviour. Testing and vendor information both say pata_acpi is the right
> way to drive Nvidia PATA ports.
Couldn't be do this generically inside libata core somehow, i.e. try to
use ACPI to set the proper mode and fall back to the driver-specific
mode setting code if that didn't work? I think if we could do that it
would solve a number of problems (i.e. we could prevent it from doing
this on SATA controllers which appear to be IDE based on the PCI ID,
like the NVIDIA SATA controllers, since the _GTM and _STM methods seem
to have undefined behavior on SATA). This would also eliminate the need
for mkinitrd, people, etc. to know that they're supposed to be loading
this other pata_acpi driver instead, since any PATA driver could take
advantage of this feature.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next prev parent reply other threads:[~2007-02-23 0:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.IjFXvdcBtWXV65pRZipPd0NVTOA@ifi.uio.no>
2007-02-22 5:45 ` [PATCH] ACPI driver support for pata Robert Hancock
2007-02-22 6:58 ` Jeff Garzik
2007-02-22 14:24 ` Alan
2007-02-22 17:11 ` Jeff Garzik
2007-02-22 18:29 ` Alan
2007-02-23 0:15 ` Robert Hancock [this message]
2007-02-23 9:36 ` Allen Martin
2007-02-23 12:50 ` Alan
2007-02-23 14:38 ` Robert Hancock
2007-02-23 15:53 ` Alan
2007-02-20 18:12 Alan
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=45DE3207.6020707@shaw.ca \
--to=hancockr@shaw.ca \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.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