Hi!
> > > I believe we should start the "let the whitelist live in HAL" era :-)
> >
> > Okay, can you try to write parser with libxml?
>
> Well, we'd first need to have the infrastructure to match against. We
> have a (very primitive) pci-bus-scanner in the radeontool source. I
> wrote (well, c&p'ed from pcilib example) this one, and i did not like
> it. Then we have to get something to give us installed package versions
> (we will have machines working with one X server version but not with
> another), and we have to actually determine if an X server was running
> on the terminal that activated suspend (i have a very dirty script
> called "wttyhx", "which tty has X?", in the powersave sources which does
> this. Dont look at this one after having lunch...).
>
> I'd rather say "call s2ram with the correct options" and let HAL figure
> out the correct options.
I'd prefer HAL figure out the complex options, but still leave
"simple" whitelist inside s2ram.
> We can just limit the amount of machines supported by "plain" s2ram to
> those we can easily match against, but then we can probably also just
> stick to the current whitelist format.
Yep. Simple :).
> Distributions will, however, just use HAL to match the machines and call
> "s2ram -f $HAL_S2RAM_OPTIONS" from some HAL helper.
I guess that we can work with distros and keep "simple" whitelist
entries in s2ram...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Suspend-devel mailing list
Suspend-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/suspend-devel
