Vojtech Pavlik <[EMAIL PROTECTED]> writes:
> 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
> dr
Vojtech Pavlik <[EMAIL PROTECTED]> 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,
Pavel Machek <[EMAIL PROTECTED]> writes:
Hi!
>The /proc/bus/input/devices has an extensible structure. You can just
>add an "A:" line (for Activity) instead of adding a new proc file.
>
> I know, but IMO there is too much stuff to parse in there. Activity
counters
> ar
Vojtech Pavlik <[EMAIL PROTECTED]> writes:
On Sat, Jan 27, 2007 at 05:45:25PM +, Pavel Machek wrote:
> Hi!
>
> >Well, I do not think your kernel code is mergeable. But bits to enable
> >similar functionality in userspace probably would be mergeable.
> >
> > You sai
Pavel Machek <[EMAIL PROTECTED]> writes:
Well, I do not think your kernel code is mergeable. But bits to enable
similar functionality in userspace probably would be mergeable.
You said it :-)
This patch exports to the user space the inactivity time (in msecs) of a given
input device. Examp
"Scott Preece" <[EMAIL PROTECTED]> writes:
On 1/25/07, Bodo Eggert <[EMAIL PROTECTED]> wrote:
> Imagine one computer serving two users. Two monitors, two keyboards ...
---
Good point! Of late I've been working on single-user systems, so it
was not at the front of my brain, despite
SIN-NEW/debug.h 2007-01-25 14:07:39.0 +0100
@@ -0,0 +1,36 @@
+/*
+ * Copyright (C) 2007 Alessandro Di Marco
+ */
+
+/*
+ * This file is part of SIN.
+ *
+ * SIN is free software; you can redistribute it and/or modify it under the
+ * terms of the GNU General Public License as publis
achment fix the time-warp problem and remove the procfs
support. Feel free to contact me when you'll find a better way, maybe I could
help.
Best,
>From 602a3340fa5b11e6cfff91719f85668980bb338b Mon Sep 17 00:00:00 2001
From: Alessandro Di Marco <[EMAIL PROTECTED]>
Date: Wed, 24 Jan 200
Pavel Machek <[EMAIL PROTECTED]> writes:
Imagine for a moment that we solve time-warp somehow. Any other
problems?
Well, a user-level daemon have to process a lot of data just to detect user
interaction. Considering that the trackpad bandwidth is nearly 5KB/sec,
probably would be better to
"Scott Preece" <[EMAIL PROTECTED]> writes:
My own hot button is making sure that the definition of what
constitutes user activity is managed in exactly one place, whether in
the kernel or not. My naive model would be to put the response at user
level, but to provide a single point of d
Pavel Machek <[EMAIL PROTECTED]> writes:
>But I still believe it can be out.
>
> Do you believe it could be a user-space daemon or what?
Yes, what prevents userspace daemon watching /dev/input/event* to
provide this functionality?
Well that was my first attempt. Just an hack,
an be out.
Do you believe it could be a user-space daemon or what?
Best,
>From f97e411d29d5771e3ac3d9c8e8aa4ad3ae0a27e2 Mon Sep 17 00:00:00 2001
From: Alessandro Di Marco <[EMAIL PROTECTED]>
Date: Tue, 23 Jan 2007 02:21:07 +0100
Subject: [PATCH] Added sysfs support; various timer bugfix, but tim
@@ -174,7 +174,7 @@ int start_procfs(void)
goto cleanout9;
}
- interact->data = (void *) simulate_interaction;
+ interact->data = (void *) simulate_event;
interact->write_proc = fake_write_proc;
interact->owner = THIS_MODULE;
diff --git a/sin.c b/sin.c
index c490daa..0d9b9c4 100644
Bill Davidsen <[EMAIL PROTECTED]> writes:
Alessandro Di Marco wrote:
> Hi all,
>
> this is a new 2.6.20 module implementing a user inactivity trigger.
Basically
> it acts as an event sniffer, issuing an ACPI event when no user activity is
> detected fo
Arjan van de Ven <[EMAIL PROTECTED]> writes:
On Thu, 2007-01-18 at 20:29 +0100, Alessandro Di Marco wrote:
> Hi all,
>
> this is a new 2.6.20 module implementing a user inactivity trigger.
Basically
> it acts as an event sniffer, issuing an ACPI event when n
+ @rm -f Module.symvers
+endif
diff -uN SIN/acpi_enumerator.c SIN.new/acpi_enumerator.c
--- SIN/acpi_enumerator.c 1970-01-01 01:00:00.0 +0100
+++ SIN.new/acpi_enumerator.c 2007-01-18 19:20:53.0 +0100
@@ -0,0 +1,114 @@
+/*
+ * Copyright (C) 2007 Alessandro Di Marco
+ */
+
+/*
+ * This
16 matches
Mail list logo
