From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Li Shaohua <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Pavel Machek <pavel-+ZI9xUNit7I@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
Subject: Re: Re: [Proposal]Another way to save/restore PCI config space for suspend/resume
Date: Wed, 27 Oct 2004 02:30:50 -0400 [thread overview]
Message-ID: <417F409A.5060409@intel.com> (raw)
In-Reply-To: <fa.ivj042g.g5qnoo-6miFZF/5cTBuMpJDpNschA@public.gmane.org>
Li Shaohua wrote:
> On Tue, 2004-10-26 at 17:21, Pavel Machek wrote:
>>>Here is a another idea:
>>>Record all PCI writes in Linux kernel...
>>
>>That looks extremely ugly to me. If you want to do something special
>>in resume function, just do it there. It will probably share a lot of
>>code with your init function, anyway.
>
> How can you handle devices without driver? And how to save/restore
> config space for special devices, such as LPC bridge and host bridge?
Say that writing the missing drivers is the only workable solution.
Does anybody have an estimate of how many there are and how big
a task that would be?
-Len
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
next parent reply other threads:[~2004-10-27 6:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.fvou17m.1f5oa9u@ifi.uio.no>
[not found] ` <fa.ivj042g.g5qnoo@ifi.uio.no>
[not found] ` <fa.ivj042g.g5qnoo-6miFZF/5cTBuMpJDpNschA@public.gmane.org>
2004-10-27 6:30 ` Len Brown [this message]
[not found] ` <417F409A.5060409-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2004-10-27 9:57 ` Re: [Proposal]Another way to save/restore PCI config space for suspend/resume Benjamin Herrenschmidt
2004-10-26 4:50 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
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=417F409A.5060409@intel.com \
--to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pavel-+ZI9xUNit7I@public.gmane.org \
--cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@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