On Mon, 11 Dec 2006 17:26:01 +0100 Stefan Seyfried <[EMAIL PROTECTED]> wrote:
> On Mon, Dec 11, 2006 at 05:01:49PM +0100, Tim Dijkstra wrote: > > > You are right of course. This of course means that the matching as done know > > is broken. > > It is "incomplete" as i would put it :-) > > > I haven't tried to see some structure in the whitelist, but isn't there a > > pattern that matches with the video cards? > > No. We only match for DMI info, not for PCI IDs. Yes, I know. This has probably been discussed ages ago, but I meant to ask if we can't distill something like - machines with graphics chipset X from nvidia need FOO|BAR - those with chipset Y from ATI need BAR > > Stefan, do you remember if hal was going the same route in matching? > > HAL can match on almost anything in its FDI files IIUC. I think you even could > match on "X driver version foo.bar installed" or maybe "X is running"/"console > is active". > > Because HAL already has all these matching capabilities, i think it is the > way to go, means: let HAL determine the needed options, pass them down > to pm-utils and pm-utils then call s2ram/s2both with the appropriate command > line to specify the workaround. Yes. Only that it is a bit annoying that you need hal for something as lowlevel as putting your machine to sleep. grs TIm ------------------------------------------------------------------------- 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
