| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <87ireowv7d.fsf@gmx.it> Date: Tue, 30 Jan 2007 13:33:10 +0100 From: Alessandro Di Marco <dmr@....it> To: Vojtech Pavlik <vojtech@...e.cz> Cc: Pavel Machek <pavel@....cz>, linux-kernel@...r.kernel.org Subject: Re: [ANNOUNCE] System Inactivity Monitor v1.0 Vojtech Pavlik <vojtech@...e.cz> writes: On Mon, Jan 29, 2007 at 11:42:08PM +0100, Alessandro Di Marco wrote: > OK, but what about the time-warp problem?. To fix it I need to know when the > system goes to sleep/resumes. In SIN I've solved via the platform driver, > introducing suspend() resume() callbacks... Well, you just need to make sure that a resume() actually is a visible event ... Sorry, but I don't see the point. Visible to what? Mine problem here is that the input device doesn't care about suspend/resume cycles (it is a straight char driver), probably because it doesn't need to (so far.) Low-level drivers (kbd & co) on the contrary are all bus or platform drivers, hooking directly into suspend/resume callbacks. Do you mean that I should back-propagate a suspend/resume event from the low-level drivers to the input one? -- There is only one thing a philosopher can be relied upon to do, and that is to contradict other philosophers. - William James - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists