From: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
To: Arjan van de Ven <arjan-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: Andi Kleen <ak-l3A5Bk7waGM@public.gmane.org>,
ACPI-DEV
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
lkml <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org,
Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
Subject: Re: [Proposal]Another way to save/restore PCI config space for suspend/resume
Date: Tue, 26 Oct 2004 10:57:54 +0100 [thread overview]
Message-ID: <1098784674.3996.85.camel@tyrosine> (raw)
In-Reply-To: <1098780150.2789.19.camel-PDvaWZGbcxh0dKo7RnIATNi2O/JbrIOy@public.gmane.org>
On Tue, 2004-10-26 at 10:42 +0200, Arjan van de Ven wrote:
> On Tue, 2004-10-26 at 02:11 -0400, Len Brown wrote:
> > What this comes down to is that extended config space is device-specific.
> > Generic solutions will fail. Only device drivers will work.
> >
> > If there are no drivers for PCI bridges to properly save/restore
> > their config space, then should create them, even if this is all the
> > drivers do.
>
> note that by default, if there is no driver, the first 64 bytes of
> config space are saved/restored.
On one of my machines, doing this causes the cardbus bridge to explode
on resume (every other character of printks suddenly starts getting left
out, and then the machine hangs). This happens even if I've never loaded
the yenta driver. The naive approach certainly doesn't seem to be safe
on all hardware.
--
Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next prev parent reply other threads:[~2004-10-26 9:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 4:50 [Proposal]Another way to save/restore PCI config space for suspend/resume Li Shaohua
[not found] ` <1098766257.8433.7.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2004-10-26 5:11 ` Andi Kleen
2004-10-26 6:11 ` [ACPI] " Len Brown
2004-10-26 8:42 ` Arjan van de Ven
[not found] ` <1098780150.2789.19.camel-PDvaWZGbcxh0dKo7RnIATNi2O/JbrIOy@public.gmane.org>
2004-10-26 9:06 ` Karol Kozimor
2004-10-26 9:57 ` Matthew Garrett [this message]
[not found] ` <20041026051100.GA5844-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
2004-10-26 9:09 ` Li Shaohua
2004-10-26 9:21 ` Pavel Machek
[not found] ` <20041026092106.GC28897-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-10-27 0:50 ` Li Shaohua
2004-10-27 1:32 ` Hiroshi 2 Itoh
[not found] ` <OF7E38C2D0.FC23B846-ON49256F3A.000672D1-49256F3A.0007BB88-JE5g2YyFxFHQT0dZR+AlfA@public.gmane.org>
2004-10-27 1:55 ` Li Shaohua
2004-10-27 2:26 ` [ACPI] " Hiroshi 2 Itoh
2004-10-27 20:14 ` Rajesh Shah
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=1098784674.3996.85.camel@tyrosine \
--to=mjg59-1xo5oi07kqx4cg9nei1l7q@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ak-l3A5Bk7waGM@public.gmane.org \
--cc=arjan-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pavel-AlSwsSmVLrQ@public.gmane.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