From: Karol Kozimor <sziwan@hell.org.pl>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Len Brown <len.brown@intel.com>, Andi Kleen <ak@suse.de>,
"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 11:06:29 +0200 [thread overview]
Message-ID: <20041026090629.GA17454@hell.org.pl> (raw)
In-Reply-To: <1098780150.2789.19.camel@laptop.fenrus.org>
Thus wrote Arjan van de Ven:
> > 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.
That's not enough -- some devices with no drivers (think LPC bridges) might
need more (see http://bugme.osdl.org/show_bug.cgi?id=3609).
Best regards,
--
Karol 'sziwan' Kozimor
sziwan@hell.org.pl
next prev parent reply other threads:[~2004-10-26 9:06 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
2004-10-26 5:11 ` [ACPI] " Andi Kleen
2004-10-26 6:11 ` Len Brown
2004-10-26 8:42 ` Arjan van de Ven
2004-10-26 9:06 ` Karol Kozimor [this message]
2004-10-26 9:57 ` Matthew Garrett
2004-10-26 9:09 ` Li Shaohua
2004-10-26 9:21 ` Pavel Machek
2004-10-27 0:50 ` [ACPI] " Li Shaohua
2004-10-27 1:32 ` [ACPI] " Hiroshi 2 Itoh
2004-10-27 1:55 ` Li Shaohua
2004-10-27 2:26 ` 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=20041026090629.GA17454@hell.org.pl \
--to=sziwan@hell.org.pl \
--cc=acpi-devel@lists.sourceforge.net \
--cc=ak@suse.de \
--cc=arjan@infradead.org \
--cc=greg@kroah.com \
--cc=len.brown@intel.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