[systemd-devel] Detecting inactive sessions

Lennart Poettering lennart at poettering.net
Tue Dec 2 17:41:16 PST 2014


On Wed, 19.11.14 00:46, Bastien Nocera (hadess at hadess.net) wrote:

> On Tue, 2014-11-18 at 19:32 +0100, Bastien Nocera wrote:
> > On Tue, 2014-11-11 at 16:46 +0100, Lennart Poettering wrote:
> > <snip>
> > > I am willing to take a patch for this, but then again, as I own a Yoga
> > > I might look into this myself too one day.
> > 
> > If you can write the scaffolding for it, I'm happy writing the code that
> > talks to the accelerometer, and that would make it work on your Yoga.
> > I've already written that code once, and I should be able to transform
> > it into something mergeable.
> > 
> > Do note that we would have to handle 3 types of accelerometers:
> > - IIO with ring buffer (the type supported by iio-sensor-proxy and in
> > the Yoga)
> > - polling IIO (the type used in cheap tablets such as mine)
> > - input device accelerometers (as present in the WeTab, and Dell Venue 8
> > tablet, apparently)
> 
> I'll correct my own mail.
> 
> We want to handle 4 types of accelerometers:
> - quaternion sensor IIO with ring buffer (the type present in some
> Yogas)
> - accelerometer IIO with ring buffer (the type supported by
> iio-sensor-proxy and in the Yoga as well)
> - polling IIO (the type used in cheap tablets such as mine)
> - input device accelerometers (as present in the WeTab)
> 
> Given that range of devices, it makes less and less sense to me to put
> it in systemd. I think that I might start thinking about a D-Bus API,
> and expect interested desktops to use that instead of adding hardware
> specific code in systemd.
> 
> What do you think?

Sounds OK to me too. As you prefer, especially if you are doing the
work ;-)

Lennart

-- 
Lennart Poettering, Red Hat


More information about the systemd-devel mailing list