public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Dösinger" <stefandoesinger-RbZlAiThDcE@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
Subject: Re: Questions about vbestate
Date: Sat, 22 Jan 2005 12:05:40 +0100	[thread overview]
Message-ID: <200501221205.40179.stefandoesinger@gmx.at> (raw)
In-Reply-To: <1106096142.7368.32.camel@tyrosine>

Am Mittwoch, 19. Januar 2005 01:55 schrieb Matthew Garrett:
> On Tue, 2005-01-18 at 19:12 +0100, Stefan Dösinger wrote:
> > *If I save the card's state with vbesate before calling the post-routine
> > and restoring the state afterwards makes switching back to X work again.
>
> I'd recommend saving the vbe state on boot, and not on every suspend.
> I'm not sure why, but there certainly seems to be some amount of
> information that's lost otherwise. Saving on suspend seems to make a
> large amount of hardware unhappy - I've only found one machine that
> complains about it on boot.

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.

Stefan


-------------------------------------------------------
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

  parent reply	other threads:[~2005-01-22 11:05 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 [this message]
     [not found]       ` <200501221205.40179.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2005-01-22 13:10         ` Matthew Garrett
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=200501221205.40179.stefandoesinger@gmx.at \
    --to=stefandoesinger-rbzlaithdce@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=mjg59-1xO5oi07KQx4cg9Nei1l7Q@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