level.
Signed-off-by: Anssi Hannula <[EMAIL PROTECTED]>
---
Index: linux-2.6.24-verbosehid/drivers/hid/hid-core.c
===
--- linux-2.6.24-verbosehid/drivers/hid/hid-core.c
+++ linux-2.6.24-verbosehid/drivers/hid/hid-core.c 2008
archives of the new list are available at mail-archive [2].
[1]
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=eb76c5c03caaa2b5c362b8514fb727047baa8fd9
[2] http://www.mail-archive.com/[EMAIL PROTECTED]/
--
Anssi Hannula
Andrew Morton wrote:
> On Mon, 3 Mar 2008 17:57:08 +0100 (CET)
> Jiri Kosina <[EMAIL PROTECTED]> wrote:
>
>
>> While Dmitry is lost ...
>>
>> --
>> Jiri Kosina
>> SUSE Labs
>>
>>
>> -- Forwarded message ------
>&
Match Xbox 360 controllers using the interface info, i.e. interface
class 255 (Vendor specific), subclass 93 and protocol 1, instead of
specifying the device ids individually. As the class is vendor-specific,
we have to still match against vendor id as well, though.
Signed-off-by: Anssi Hannula
Add Mad Catz and 0x0e6f xbox360 controllers which are found in
xpad_device[] table in xpad.c into the vendor id list. Also add
Logitech into the vendor list for Logitech Chillstream gamepads.
Signed-off-by: Anssi Hannula <[EMAIL PROTECTED]>
---
--- ./drivers/input/joystick/xpad.co2
Match Xbox 360 controllers using the interface info, i.e. interface
class 255 (Vendor specific), subclass 93 and protocol 1, instead of
specifying the device ids individually. As the class is vendor-specific,
we have to still match against vendor id as well, though.
Signed-off-by: Anssi Hannula
Match Xbox 360 controllers using the interface info, i.e. interface
class 255 (Vendor specific), subclass 93 and protocol 1, instead of
specifying the device ids individually. As the class is vendor-specific,
we have to still match against vendor id as well, though.
Signed-off-by: Anssi Hannula
Add 0e8f:0003 into the list of devices supported by the hid-plff
force feedback driver. These devices identify themselves as
"GreenAsia Inc.USB Joystick " and can be either adapters or
actual game controllers. The testing was done with a Köng Gaming
gamepad.
Signed-off-by: Ans
Add 0e8f:0003 into the list of devices supported by the hid-plff
force feedback driver. These devices identify themselves as
"GreenAsia Inc.USB Joystick " and can be either adapters or
actual game controllers. The testing was done with a Köng Gaming
gamepad.
Signed-off-by: Ans
v wrote:
On Sunday 09 September 2007 19:03, Kay Sievers wrote:
On 9/8/07, Anssi Hannula <[EMAIL PROTECTED]> wrote:
However, the change that broke id_path of udev is that
/sys/class/input/event5/device is now a symlink to the inputX directory
instead of being the same as the device symlink
Andrey Borzenkov wrote:
Anssi Hannula wrote:
Hi!
There seem to be changes in sysfs input structure between 2.6.22 and
2.6.23-rc5 which cause some breakage.
[...]
There is no longer:
/sys/class/input/eventX => /sys/class/input/inputX/eventX
instead there is:
/sys/class/inputX/input:eve
rably more time to adapt udev for coming changes in sysfs.
--
Anssi Hannula
Gerald Folcher wrote:
> Anssi Hannula wrote:
>
>> Could you perhaps provide the kernel log output when you plug your
>> device in with CONFIG_HID_DEBUG enabled in kernel configuration?
>
> Ok, after setting CONFIG_HID_DEBUG=y here's what got appended in the
>
the aforementioned MS-Windows registry there is also an id 0x652 for a
> Thrustmaster wheel with the same name).
Could you perhaps provide the kernel log output when you plug your device
in with CONFIG_HID_DEBUG enabled in kernel configuration?
Thanks,
--
Anssi Hannula
Jiri Kosina wrote:
On Wed, 20 Jun 2007, Anssi Hannula wrote:
did you make any progress here please? I am going to merge the patch,
still I'd be understand what caused it (on the other hand from Diogo's
last comment it doesn't seem 100% certain that we cased it somewhere
ar
Jiri Kosina wrote:
On Thu, 14 Jun 2007, Anssi Hannula wrote:
I'd of course happily merge the fix which initializes the value
properly into my tree, but I would be curious what broke it, to double
check that we didn't break anything else along with it.
Okay, I'll get back to yo
Jiri Kosina wrote:
On Thu, 14 Jun 2007, Anssi Hannula wrote:
do you have any idea what caused this to happen in 2.6.21 and not in
earlier versions?
Nope. Do you think it would be useful for me to bisect 2.6.20-2.6.21?
I'd of course happily merge the fix which initializes the value pro
Jiri Kosina wrote:
On Wed, 13 Jun 2007, Anssi Hannula wrote:
When setting the autocentering of PID devices, PID_DIRECTION_ENABLE is
not being explicitely set to 1. This results in autocentering working
only on the vertical axis when this field is preset to 0. This seems to
happen since
hat by setting it explicitely to 1 when preparing the set_effect
report for autocentering spring effect.
Signed-off-by: Diogo Kastrup <[EMAIL PROTECTED]>
Signed-off-by: Anssi Hannula <[EMAIL PROTECTED]>
---
--- linux/drivers/hid/usbhid/hid-pidff.bkp 2007-06-12 20:39:23.0
-0300
o it similarly for the
spring effect.
--
Anssi Hannula
le, and
>> a driver like hid-lgff.c would just need to do the device recognitions?
>
> I guess so, but you should check with the author.
>
Yes, it is.
--
Anssi Hannula
hw could
be quite easily done in ff-core.c or ff-memless.c.
(I also don't know what the triggers are useful for)
johann deneux also wrote in another message:
> The
> problem is to make an extension that does not duplicate the
> capabilities of the existing API. We don't want to have two ways of
> specifying the same effects.
How is this a problem?
--
Anssi Hannula
.
Then the events from the device are only sent to this one application :)
--
Anssi Hannula
; effect, I'd rather add
real effect types.
> Also yet another one such as FF_VECTOR or FF_3D could be considered as one
> posibility, but it's still the same -- to have no more than 3 entries to
> pass forces...
>
>> Do we have any idea if there any users of FF out there?
>
> At least me :). I'm using it for wheel and joystick in modules for locally
> developped multiplatform virtual reality system.
Wine and BZflag come to mind, though I think the support is quite
limited in both.
--
Anssi Hannula
els may
have defaulted to ff_joystick if no entry is present in devices[], hence
these devices working for some without the entry.
(so the alternative is to restore that behaviour)
BTW, shouldn't the PID/VID check in hid_lgff_init() do endian conversion?
--
Anssi Hannula
25 matches
Mail list logo
