lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4BC852CD.40406@tremplin-utc.net>
Date:	Fri, 16 Apr 2010 14:06:37 +0200
From:	Éric Piel <eric.piel@...mplin-utc.net>
To:	Marcin Derlukiewicz <marcin@...lukiewicz.pl>
CC:	Jiri Kosina <jkosina@...e.cz>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Samu Onkalo <samu.p.onkalo@...ia.com>,
	Pavel Machek <pavel@....cz>, lm-sensors@...sensors.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] lis3lv02d: provide means to disable polled input interface

On 16/04/10 13:41, Marcin Derlukiewicz wrote:
:
> sorry for the delay, had a crunch time
> 
> here is the link for this lsof:
> https://bugzilla.novell.com/attachment.cgi?id=354953
So apparently, it's opened by mplayer. Indeed, by default mplayer always
opens the first joystick device, because some people like to  control a
movie with a joystick.

I don't think much can be done from the kernel point of view. Maybe
there are even people who enjoy controlling their movies by moving their
laptop! Here, my ~/.mplayer/config looks like:
[default]
input=js-dev=/dev/input/js8

You could also put a udev rule to change the name of this joystick to
something like js1.

All I could think of in the kernel side to improve this situation would
be to give more information about joystick devices, and define a subtype
"accelerometer", which mplayer could avoid selecting by default. I don't
know enough the input interface to know if this already exists...

See you,
Eric

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ