From: Len Brown <len.brown@intel.com>
To: Andi Kleen <ak@suse.de>
Cc: "Li, Shaohua" <shaohua.li@intel.com>,
ACPI-DEV <acpi-devel@lists.sourceforge.net>,
lkml <linux-kernel@vger.kernel.org>,
greg@kroah.com, Pavel Machek <pavel@suse.cz>
Subject: Re: [ACPI] [Proposal]Another way to save/restore PCI config space for suspend/resume
Date: Tue, 26 Oct 2004 02:11:25 -0400 [thread overview]
Message-ID: <417DEA8D.4080307@intel.com> (raw)
In-Reply-To: <20041026051100.GA5844@wotan.suse.de>
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.
-Len
next prev parent reply other threads:[~2004-10-26 6:11 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 ` Len Brown [this message]
2004-10-26 8:42 ` [ACPI] " 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
[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=417DEA8D.4080307@intel.com \
--to=len.brown@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=ak@suse.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=shaohua.li@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