From: Jeff Garzik <jgarzik@pobox.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
Christoph Hellwig <hch@infradead.org>,
randy_d_dunlap@linux.intel.com, linux-ide@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
acpi-devel@lists.sourceforge.net
Subject: Re: [ACPI] Re: RFC: ACPI/scsi/libata integration and hotswap
Date: Fri, 09 Dec 2005 06:42:12 -0500 [thread overview]
Message-ID: <43996D94.5080108@pobox.com> (raw)
In-Reply-To: <1134052257.17102.13.camel@localhost.localdomain>
Alan Cox wrote:
> On Iau, 2005-12-08 at 09:14 -0500, Jeff Garzik wrote:
>
>>These are only for PATA. We don't care about _GTM/_STM on SATA.
>
>
> Even your piix driver supports PATA. Put the foaming (justified ;))
> hatred for ACPI aside for a moment and take a look at the real world as
> it unfortunately is right now.
First, I clearly said "except on ata_piix ... or PATA"
Second, don't put words in my mouth. I don't hate ACPI, and libata's
direction for hotswap and suspend/resume has zero to do with "foaming
hatred."
Right now, the top priority is getting SATA suspend/resume correct, and
_hopefully_ doing it in a way that's friendly to PATA. And as I said,
we don't care about _GTM/_STM on SATA.
Further, all current ACPI proposed code is completely half-assed. It's
"hope and pray", because libata configures the device and does resets --
which is bound to CONFLICT WITH ACPI.
Even further, I want to support both ACPI cases (x86[-64]) and non-ACPI
cases (other arches). Some platforms want ACPI for passwords or other
settings. Some platforms don't have ACPI at all. Locking libata into
ACPI _only_ for suspend/resume is completely unacceptable.
I'm not a hope-n-pray kind of guy. I want to get it right. People are
more than welcome to use unapplied patches floating around the 'net
until we get there.
Jeff
next prev parent reply other threads:[~2005-12-09 11:42 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 3:02 RFC: ACPI/scsi/libata integration and hotswap Matthew Garrett
2005-12-08 9:15 ` Christoph Hellwig
2005-12-08 13:26 ` Matthew Garrett
2005-12-08 13:33 ` Christoph Hellwig
2005-12-08 13:39 ` Matthew Garrett
2005-12-08 13:44 ` Christoph Hellwig
2005-12-08 17:18 ` Erik Slagter
2005-12-08 20:43 ` Jeff Garzik
2005-12-08 21:03 ` Dominic Ijichi
2005-12-08 21:09 ` Jeff Garzik
2005-12-08 21:34 ` Dominic Ijichi
2005-12-08 21:31 ` Randy Dunlap
2005-12-09 9:45 ` Erik Slagter
2005-12-09 10:39 ` Jens Axboe
2005-12-09 10:45 ` Erik Slagter
2005-12-09 11:27 ` Jeff Garzik
2005-12-09 11:35 ` Erik Slagter
2005-12-09 11:40 ` Christoph Hellwig
2005-12-09 11:46 ` Jens Axboe
2005-12-09 11:55 ` Matthew Garrett
2005-12-09 13:22 ` Bartlomiej Zolnierkiewicz
2005-12-09 12:01 ` Erik Slagter
2005-12-09 12:07 ` Jens Axboe
2005-12-10 2:19 ` Douglas Gilbert
2005-12-14 20:52 ` [ACPI] " Matthew Wilcox
2005-12-09 11:30 ` Jens Axboe
2005-12-09 3:28 ` Mark Lord
2005-12-09 11:29 ` Jeff Garzik
2005-12-10 4:01 ` Mark Lord
2005-12-08 13:52 ` Jeff Garzik
2005-12-08 14:07 ` [ACPI] " Alan Cox
2005-12-08 14:14 ` Jeff Garzik
2005-12-08 14:30 ` Alan Cox
2005-12-08 14:43 ` Matthew Garrett
2005-12-08 14:53 ` Alan Cox
2005-12-09 11:42 ` Jeff Garzik [this message]
2005-12-08 14:12 ` Matthew Garrett
2005-12-08 14:01 ` Alan Cox
2005-12-08 14:18 ` Matthew Garrett
2005-12-08 14:33 ` Alan Cox
2005-12-08 14:52 ` Matthew Garrett
2005-12-08 14:55 ` Alan Cox
2005-12-08 17:19 ` Matthew Garrett
2005-12-09 11:42 ` Christoph Hellwig
2005-12-09 11:49 ` Jeff Garzik
2005-12-09 11:52 ` Matthew Garrett
2005-12-09 11:58 ` Jeff Garzik
2005-12-09 12:11 ` Matthew Garrett
2005-12-09 12:16 ` Jeff Garzik
2005-12-09 12:24 ` Matthew Garrett
2005-12-10 0:40 ` Jeff Garzik
2005-12-10 2:34 ` Matthew Garrett
2005-12-10 2:39 ` Jeff Garzik
2005-12-10 2:47 ` Matthew Garrett
2005-12-10 2:41 ` Jeff Garzik
2005-12-10 2:50 ` Matthew Garrett
2005-12-10 2:57 ` Jeff Garzik
2005-12-10 3:47 ` [ACPI] " Andrew Grover
2005-12-12 0:38 ` Alan Cox
2005-12-09 11:50 ` Matthew Garrett
2005-12-09 11:55 ` Christoph Hellwig
2005-12-13 18:14 ` Randy Dunlap
2005-12-13 18:26 ` Matthew Garrett
2005-12-13 19:07 ` Randy Dunlap
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=43996D94.5080108@pobox.com \
--to=jgarzik@pobox.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hch@infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=randy_d_dunlap@linux.intel.com \
/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).