From: Russell King <rmk@arm.linux.org.uk>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Patrick Mochel <mochel@transmeta.com>,
linux-power@phobos.fachschaften.tu-muenchen.de
Subject: Re: PCI power management
Date: Sat, 21 Apr 2001 10:09:13 +0100 [thread overview]
Message-ID: <20010421100913.A7433@flint.arm.linux.org.uk> (raw)
In-Reply-To: <3AE02E45.57D7BA9D@mandrakesoft.com> <20010420125615.23599@mailhost.mipsys.com>
In-Reply-To: <20010420125615.23599@mailhost.mipsys.com>; from benh@kernel.crashing.org on Fri, Apr 20, 2001 at 02:56:15PM +0200
On Fri, Apr 20, 2001 at 02:56:15PM +0200, Benjamin Herrenschmidt wrote:
> It's not so complicated to have the minimum flexibility for the driver
> to tell it's maximum supported power level, and I don't see why it would
> be a problem to use D2 instead of D3 when we don't support D3 for a given
> device (either because the HW is broken, undocumented, or because our
> driver just don't know how to bring back the chip to life).
Umm, isn't it true that most VGA cards will have this problem? Are we
going to put an x86 emulator into the kernel so we can run the BIOS on
non-x86 hardware, just so that we can re-initialise the chip? ;|
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-04-21 9:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10104181150530.7690-100000@nobelium.transmeta.com>
2001-04-19 8:25 ` PCI power management Jeff Garzik
2001-04-19 10:08 ` Benjamin Herrenschmidt
2001-04-19 10:38 ` CaT
2001-04-19 12:10 ` Benjamin Herrenschmidt
2001-04-19 12:57 ` Alan Cox
2001-04-19 13:14 ` Benjamin Herrenschmidt
2001-04-19 13:33 ` Alan Cox
2001-04-19 13:43 ` Benjamin Herrenschmidt
2001-04-20 0:05 ` Patrick Mochel
2001-04-20 12:06 ` Benjamin Herrenschmidt
2001-04-20 12:40 ` Jeff Garzik
2001-04-20 12:56 ` Benjamin Herrenschmidt
2001-04-21 9:09 ` Russell King [this message]
2001-04-19 10:18 ` Benjamin Herrenschmidt
2001-04-19 13:24 ` Jeff Garzik
2001-04-20 0:11 ` [Linux-pm-devel] " Patrick Mochel
2001-04-19 23:03 ` Patrick Mochel
2004-08-02 21:33 pci " Erik Rigtorp
2004-08-02 23:45 ` Brian Gerst
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=20010421100913.A7433@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=benh@kernel.crashing.org \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-power@phobos.fachschaften.tu-muenchen.de \
--cc=mochel@transmeta.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