From: Jesse Barnes <jbarnes@sgi.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Jon Smirl <jonsmirl@gmail.com>,
fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH] Provide control of active VGA device on PCI systems
Date: Tue, 22 Feb 2005 13:02:59 -0800 [thread overview]
Message-ID: <200502221302.59803.jbarnes@sgi.com> (raw)
In-Reply-To: <1109105867.5411.128.camel@gaston>
On Tuesday, February 22, 2005 12:57 pm, Benjamin Herrenschmidt wrote:
> Well, that's something we need to figure out... While I do think the
> POSTing must be under driver control, as I explained, there is still
> that nasty notion of who has the stuff at 0xc0000 ... and if your
> firmware runs the x86 BIOS but doesn't keep the shadow around, then you
> are toast with a good deal of laptop chips.
Right, that's a big pain.
> The problem is that on some cards (ATIs for example), the BIOS will
> modify the image in RAM at c0000 and will put in there various infos,
> like panel type, PLL infos, etc... that can't always be obtained from
> the "hard" ROM (especially the panel infos). The driver (raeonfb or X,
> strace X and see it mmap'ing /dev/mem at c0000...) need those things.
Shouldn't the driver safe that stuff at suspend time for use at resume time?
Or do we expect to be able to resume with different hw attached?
Jesse
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-22 21:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 5:50 [PATCH] Provide control of active VGA device on PCI systems Jon Smirl
2005-02-20 7:07 ` Jon Smirl
2005-02-22 18:50 ` Jesse Barnes
2005-02-22 20:57 ` Benjamin Herrenschmidt
2005-02-22 21:02 ` Jesse Barnes [this message]
2005-02-22 21:27 ` Benjamin Herrenschmidt
2005-02-22 21:42 ` Jon Smirl
2005-02-20 8:23 ` Benjamin Herrenschmidt
2005-02-20 16:35 ` Jon Smirl
2005-02-22 4:07 ` James Simmons
2005-02-24 6:14 ` Jon Smirl
2005-02-22 4:13 ` James Simmons
2005-02-22 4:47 ` Jon Smirl
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=200502221302.59803.jbarnes@sgi.com \
--to=jbarnes@sgi.com \
--cc=benh@kernel.crashing.org \
--cc=jonsmirl@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).