From: Mark Lord <liml@rtr.ca>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] libata resume improvements
Date: Sat, 27 May 2006 16:10:30 -0400 [thread overview]
Message-ID: <4478B236.7000007@rtr.ca> (raw)
In-Reply-To: <20060527055533.GA5159@havoc.gtf.org>
Jeff Garzik wrote:
> This is an example of how one might make sure the ATA bus reaches
> bus-idle, before attempting to talk to it.
>
> It compiles, but is completely untested...
>
> Other resume improvements should work at the pci_driver::resume level as
> this does, _not_ the SCSI->ATA->resume device level.
>
>
> diff --git a/drivers/scsi/ata_piix.c b/drivers/scsi/ata_piix.c
...
Sorry to say, but no user-visible difference from previous attempts.
Still fails the same way, after a 30-ish second timeout on resume.
Cheers
next prev parent reply other threads:[~2006-05-27 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-27 5:55 [PATCH] libata resume improvements Jeff Garzik
2006-05-27 20:10 ` Mark Lord [this message]
2006-05-27 20:11 ` Mark Lord
2006-05-27 20:12 ` 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=4478B236.7000007@rtr.ca \
--to=liml@rtr.ca \
--cc=jeff@garzik.org \
--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;
as well as URLs for NNTP newsgroup(s).