From: Mark Lord <liml@rtr.ca>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-ide@vger.kernel.org, torvalds@osdl.org
Subject: Re: [PATCH alt4 v3] libata resume fixes
Date: Sat, 27 May 2006 16:56:56 -0400 [thread overview]
Message-ID: <4478BD18.6010908@rtr.ca> (raw)
In-Reply-To: <20060527205213.GA30686@havoc.gtf.org>
I tried merging Linus's one-liner in front of alt4_v2,
and the screen came back right away (instead of stalling 30seconds),
and then the alt4_v2 code killed the interface as before. :)
Jeff Garzik wrote:
> Here's alt4 v3. Having the host_stat == 0x1 was suspicious.
> After digging through the hardware manual, it might be a good idea to
> configure BMDMA registers properly, in case that was done by BIOS but
> not by D3->D0 silicon reset values.
I'll try that. But does it make sense that Linus's one-liner
would also work, if this was really the problem? (dunno, just asking)
> One core problem with all of libata suspend/resume is that
> * we boot from a configuration set up by BIOS
> * but going D3->D0, we simply get silicon defaults
>
> Randy Dunlap's ACPI patches will probably help a bit.
The ACPI patches have indeed been working here for over a year now,
on all kernels up to 2.6.15 --> not needed for 2.6.16.
Cheers
next prev parent reply other threads:[~2006-05-27 20:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-27 19:58 [PATCH alt4] libata resume fixes Jeff Garzik
2006-05-27 20:10 ` [PATCH alt4 v2] " Jeff Garzik
2006-05-27 20:14 ` Jeff Garzik
2006-05-27 20:30 ` Mark Lord
[not found] ` <4478B611.2030201@rtr.ca>
2006-05-27 20:32 ` Jeff Garzik
2006-05-27 20:41 ` Mark Lord
2006-05-27 20:56 ` Jeff Garzik
2006-05-27 21:00 ` Mark Lord
2006-05-27 21:06 ` Jeff Garzik
2006-05-27 21:09 ` Mark Lord
2006-05-27 21:14 ` Jeff Garzik
2006-05-27 20:13 ` [PATCH alt4] " Mark Lord
2006-05-27 20:52 ` [PATCH alt4 v3] " Jeff Garzik
2006-05-27 20:56 ` Mark Lord [this message]
2006-05-27 21:11 ` Jeff Garzik
2006-05-27 21:15 ` Mark Lord
2006-05-27 21:25 ` Jeff Garzik
2006-05-27 21:12 ` Mark Lord
2006-05-27 21:21 ` Jeff Garzik
2006-05-29 3:53 ` zhao, forrest
2006-05-29 5:25 ` 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=4478BD18.6010908@rtr.ca \
--to=liml@rtr.ca \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.