Video PM methods
Richard Hughes
hughsient at gmail.com
Fri Apr 28 02:00:06 PDT 2006
On Fri, 2006-04-28 at 10:53 +0200, Danny Kukawka wrote:
> On Friday 28 April 2006 00:19, Richard Hughes wrote:
> > Patch against HEAD attached.
> >
> > I've only allowed access from the root user (checked in the script and
> > dbus permissions) and it's now trivial to add new card vid/pid's in the
> > fdi file.
> >
> > Scripts support intel, nvidia and ati, but I'll add more if ppl with the
> > hardware send me details of what's needed.
>
> I would do this for all kind of intel 855GM or any other of the intel cards.
> This is not needed for all of them. This base on the machine (and also the
> bios version) and not on the graphic chip. I have seen several machines where
> this is not needed. In fact you need this only on some special machines. If
> this go in HAL we need to list this special effected machines (as you e.g.
> can find in s2ram) and not the graphic card.
Yes, I think this needs to be very specific, hence why I think this
belongs in an FDI file where we can match on pretty much anything.
I think we can use the s2ram whitelist as a good basis, although maybe
just writing a tutorial online for users to say I've got machine xyz and
I have to use this resume method...
> Not complete shure what happen on machines, where this workaround is not
> needed and if it maybe break something on this machines, but we should not
> add unneeded and untested methodes to machines where it is not needed.
Yes, agreed. using vbetool on my sytem actually *breaks* the resume from
video, the kernel seems to do better on it's own.
Richard.
More information about the hal
mailing list