On mer., 2009-11-11 at 18:08 +0100, Michael Biebl wrote:
> Yves-Alexis Perez wrote:
> > On mer., 2009-11-11 at 16:49 +0100, Michael Biebl wrote:
> >> I think only the devices named input* are relevant (9 to go). Then
> >> test each of
> >> them if it has a capabilities/sw file.
> >>
> >> What do you get if you run
> >> cd /sys/class/input
> >> for i in `seq 0 8`; do
> >> cat input$i/capabilites/sw
> >> done 
> > 
> > cor...@hidalgo: for i in `seq 0 8`; do
> > for> cat input$i/capabilites/sw
> > for> done
> > cat: input0/capabilites/sw: No such file or directory
> > cat: input1/capabilites/sw: No such file or directory
> > cat: input2/capabilites/sw: No such file or directory
> > cat: input3/capabilites/sw: No such file or directory
> > cat: input4/capabilites/sw: No such file or directory
> > cat: input5/capabilites/sw: No such file or directory
> > cat: input6/capabilites/sw: No such file or directory
> > cat: input7/capabilites/sw: No such file or directory
> > cat: input8/capabilites/sw: No such file or directory
> > cor...@hidalgo: find /sys/class/input -name sw
> 
> That won't work as find does not seem to follow symlinks.
> find /sys/ -name sw is likely more successfull

Good point, it worked. So, in the end:

grep . /sys/class/input/*/capabilities/sw
/sys/class/input/input0/capabilities/sw:0
/sys/class/input/input1/capabilities/sw:0
/sys/class/input/input2/capabilities/sw:0
/sys/class/input/input3/capabilities/sw:0
/sys/class/input/input4/capabilities/sw:1
/sys/class/input/input5/capabilities/sw:0
/sys/class/input/input6/capabilities/sw:8
/sys/class/input/input7/capabilities/sw:0
/sys/class/input/input8/capabilities/sw:0

with even4 beeing the Lid Switch. if sw=1 that means (according to
input.h : #define SW_LID      0x00) capability is present (which would
agree with lsinput.


> > 
> > /dev/input/event4
> >    bustype : BUS_HOST
> >    vendor  : 0x0
> >    product : 0x5
> >    version : 0
> >    name    : "Lid Switch"
> >    phys    : "PNP0C0D/button/input0"
> >    bits ev : EV_SYN EV_SW
> > 
> 
> I'm honestly not 100% sure if it's a DK-power issue or not. Mind to
> forward/file
> this bug upstream and ask for clarification?
> It doesn't look like a Debian specific issue so is best handled
> upstream anyways.

Sure, no problem.

Cheers,


-- 
Yves-Alexis

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to