Re: Re: Resume -> higher power drain?

[Carl-Daniel Hailfinger <c-d.hailfinger.devel.2005-hi6Y0CQ0nG0@public.gmane.org>]

Stefan Seyfried schrieb:
> On Mon, May 09, 2005 at 02:38:06PM +0100, Matthew Garrett wrote:
> 
>>On Mon, 2005-05-09 at 11:07 +0200, Stefan Seyfried wrote:
>>
>>
>>>according to some X guys, vbetool vbestate save/restore is "problematic"
>>>at least and should only be used as a measure of last resort, if everything
>>>else fails.
> 
> 
> Again, to be clear: this is not my wisdom but from people who know the radeon
> chips prettty good (Matthias Hopf, among others)
> 
> 
>>The main advantage of saving/restoring the VBE state is that the code to
>>do so is likely to actually be there, which is something that you can't
>>say about POSTing. As far as I can tell, there shouldn't be any issue in
> 
> 
> The radeon X driver apparently knows enough about the chips to re-post them.
> Excerpt from my X log:
> (WW) RADEON(0): zero MEMSIZE, probably at D3cold. Re-POSTing via int10.
> (II) RADEON(0): Primary V_BIOS segment is: 0xc000

Can you please ask the gurus: What is the difference between POSTing with
the X driver and POSTing with vbetool, if both versions use int10? And can
I have the "better int10" of the X driver as an isolated piece of code so
that resume will eventually work even if X is not running?

Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click