RE: SS4000E LEDS and Power/Reset Buttons
- To: "'Arnaud Patard \(Rtp\)'" <email@example.com>
- Cc: <firstname.lastname@example.org>
- Subject: RE: SS4000E LEDS and Power/Reset Buttons
- From: "Chris Wilkinson" <email@example.com>
- Date: Mon, 01 Apr 2013 14:34:29 -0400
- Message-id: <000601ce2f07$8c6292f0$a527b8d0$@net>
- In-reply-to: <firstname.lastname@example.org>
- References: <001e01ce2beb$5bc15970$13440c50$@net> <email@example.com> <000001ce2db4$67abab30$37030190$@net> <firstname.lastname@example.org>
Yes that works. I see a constant stream of messages from the w83792d sensor
chip on the serial port and in syslog reporting sensor values. Maybe the
chip is being polled now at 100ms but anyway it's bogging down the cpu. I
built-in the I2C Support>I2C debugging messages support in the kernel so it
could be that too.
It would be nice if there was a way to turn these on/off without rebuilding
From: Arnaud Patard (Rtp) [mailto:email@example.com]
Sent: Sunday, March 31, 2013 3:53 AM
To: Chris Wilkinson
Subject: Re: SS4000E LEDS and Power/Reset Buttons
"Chris Wilkinson" <firstname.lastname@example.org> writes:
> Presumably this just sets up the polling for the buttons. How does one
> the state?
yeah, this sets the polling but without it, the driver is refusing to
register the input device, so, actually it makes things working.
Once booted, you should get a /dev/input/event0 (for instance) and also
you should get some key press event through normal keyboard stuff.
To get the name of the event file, look at /proc/bus/input/devices (oh,
you need evdev to get the event file).
To UNSUBSCRIBE, email to debian-arm-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact