Thread: Clara HD Display time when reading
View Single Post
Old 07-23-2019, 03:05 PM   #228
frostschutz
Linux User
frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.
 
frostschutz's Avatar
 
Posts: 2,282
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
you can see what it returns if you set debug=1

after some trial and error with dd and hexdump - it worked yet didn't. short reads missing the event we were interested in, delay due to unwanted pipe buffereing or waiting for additional block when read wasn't short, and added to that the general cumbersomeness of doing this for more than one device in parallel, etc. etc.

I caved in and wrote a little C helper to just poll across devices and just dump whatever events there are. The interpretation of those still happens on the shell side

A few things fell under the bus while doing so (whoops, touchscreen= button= update= is currently uneffective) I'll re-implement those later.

Right now it's experimental and the main question is, does it drain the battery or not, and does it work otherwise too.

Last edited by frostschutz; 07-23-2019 at 03:09 PM.
frostschutz is offline   Reply With Quote