From: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Questions about vbestate
Date: Sat, 22 Jan 2005 13:10:47 +0000 [thread overview]
Message-ID: <1106399447.30227.26.camel@tyrosine> (raw)
In-Reply-To: <200501221205.40179.stefandoesinger-RbZlAiThDcE@public.gmane.org>
On Sat, 2005-01-22 at 12:05 +0100, Stefan Dösinger wrote:
> Is it possible to reset the whole video memory with vbetool? I mean, if we
> reset the graphics processor when posting the card, we should also clean up
> the garbage in the video memory. The content in my card's memory survives a
> card reboot, a suspend-to-ram cycle and even a system reboot. Under certain
> circumstances this crashes both fglrx and the open source radeon driver.
That's likely to be caused by held-over internal chip state, rather than
video memory. Whether or not vbetool can do anything about that depends
on the video BIOS, really - the state saving/restore /ought/ to deal
with that, but there's no guarantee.
--
Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-01-22 13:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 18:12 Questions about vbestate Stefan Dösinger
[not found] ` <200501181912.19644.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2005-01-19 0:55 ` Matthew Garrett
2005-01-19 10:18 ` Stefan Dösinger
2005-01-22 11:05 ` Stefan Dösinger
[not found] ` <200501221205.40179.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2005-01-22 13:10 ` Matthew Garrett [this message]
2005-01-22 15:11 ` Stefan Dösinger
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=1106399447.30227.26.camel@tyrosine \
--to=mjg59-1xo5oi07kqx4cg9nei1l7q@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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