the default deadzone to '0' so I don't have to
do the above?
Thanks,
Simon.
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
time it can be 'away' or what is the size of
the inline buffer?
Many thanks,
Simon.
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
.
Thanks,
Simon.
SDL_missing_events2.txt.gz
Description: GNU Zip compressed data
)
|| || || || || + DPad/Hat (F=Null,0-7)
|| || || +| ++ Break Axis (0-3ff)
|| || ++ + Accel Axis (0-3ff)
++ ++ Steer Axis (f8f8-0708)
--
Are such labels worthwhile, or even available? Or should I just ignore
this aspect of the driver?
Simon
--
To unsubscribe from this list: send the line unsubscribe linux
with: echo 00FF00 rgb
+
Shouldn't the name presented in the sys/class/leds directories change
appropriately too?
Simon
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo
would need to be
1.5
Also using 'jscal -s 8,0,0,0,0,0...' I can turn off the calibration
altogether and see the raw values from the device.
Question: should a calibration really be applied to a dial?? evtest
displays without a fuzz and flat listed.
Simon
Hi,
I'm modifying the HID descriptor
The problem is that the 'broken line' calibration can not properly
represent/process a value with a small range - I guess this does not
matter when there is a large input range.
In my system I have a dial (RZ) with 4 positions (0..3):
expect to see -32768, -10922, +10922, +32768
Hi Simon
device?
Thanks,
Simon.#include sys/time.h
#include stdio.h
#include unistd.h
#include fcntl.h
int fd[15] = {0,0,0,0,0,0,0,0,0,0,0,0,0,0,0};
int scramble[] = {12, 2, 14, 6, 10, 7, 9, 1, 3, 15, 4, 5, 11, 8, 13};
void flash(int led, int enable)
{
// want to do the equivalant of:
// echo 1 /sys
On Thu, 24 Jan 2013, Simon Wood wrote:
From: simon simon@simon-virtual-machine.(none)
This patch to the SRW-S1 driver adds the ability to control all
LEDs simultaneously as testing showed that it was slow (noticably!!)
when seting or clearing all the LEDs in turn.
It adds a 'RPMALL' LED
On Thu, 24 Jan 2013, Simon Wood wrote:
From: simon simon@simon-virtual-machine.(none)
Add support the SRW-S1 by patching HID descriptor to read axis
as Generic Desktop X, Y and Z (rather than Usage page being
'Simulation').
Signed-off-by: Simon Wood si...@mungewell.org
tested-by: John
On Mon, 28 Jan 2013, si...@mungewell.org wrote:
From: simon simon@simon-virtual-machine.(none)
Add support the SRW-S1 by patching HID descriptor to read axis
as Generic Desktop X, Y and Z (rather than Usage page being
'Simulation').
Signed-off-by: Simon Wood si...@mungewell.org
Add support the SRW-S1 by patching HID descriptor to read axis
as Generic Desktop X, Y and Z (rather than Usage page being
'Simulation').
Slight glitch in making this patch set, there is no [5/5] - just the 4
parts as sent sorry if this causes confusion.
Simon.
--
To unsubscribe from
Simon,
thanks for respin of the patchset.
I thought we converged to hid-steelseries name in the end originally?
If you agree, I'll change it and apply.
I'd be OK with that,
Simon
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord
(as
USB_DEVICE_ID_LOGITECH_DFP_WHEEL in the line after your patch).
Perhaps you have a different revision. Can you please forward a 'lsusb
-vv' to we can compare.
I have attached the one from my DPF.
--
simon@selkie:~/speed-dreams-2.0$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0
Simon
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
the range is.
Simon.
This patch should be used in favor of the previous.
Signed-off-by: Paul Sbarra sbarra.p...@gmail.com
---
drivers/hid/hid-lg4ff.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/drivers/hid/hid-lg4ff.c b/drivers/hid/hid-lg4ff.c
index d7947c7
Resending as I missed adding linux-input to the receiptants,
Simon
Original Message
Subject: Re: [PATCH 1/3] hid: Add report descriptor for Logitech Driving
Force wheel
From:si...@mungewell.org
Date:Sun, February 3, 2013 8:30 pm
to a system and still
allow unique (but consistant) naming?
Cheers,
Simon
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signed-off-by: Paul Sbarra sbarra.p...@gmail.com
Looks good to me.
Signed-off-by: Simon Wood si...@mungewell.org
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
is not enabled?
Does forcing a 'depends on LED_CLASS' in Kconfig prevent the
hid-steelseries module being built on systems without LEDs, or is this
simply a way to ensure that the LED_CLASS module gets loaded first?
Simon.
From: Randy Dunlap rdun...@infradead.org
Fix hid-steelseries build by making
accordingly.
Signed-off-by: Elias Vanderstuyft elias@gmail.com
[anssi.hann...@iki.fi: added description and CCs]
Signed-off-by: Anssi Hannula anssi.hann...@iki.fi
Cc: Simon Wood si...@mungewell.org
Cc: sta...@vger.kernel.org
---
Simon, does this look OK to you, or do you think it should
structure under the USB ID for your device.
ie. for my Sony Dual Shock controller
--
simon@simon-virtual-machine:/sys/bus/usb/devices/1-1:1.0/0003:054C:0268.0001$
hexdump -C report_descriptor
05 01 09 04 a1 01 a1 02 85 01 75 08 95 01 15 00
|..u.|
0010 26 ff 00 81 03 75 01 95
the release more
with different IDs (recently saw a new DFGT version).
In the longer term we may wish to add an option/control to split (or not)
the brake/accel as the user requests. I don't actually think that anyone
wants combined axis, but there's no telling with some people ;-)
Simon
://patchwork.kernel.org/patch/3016111/
Simon
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
for the D-Pad axis.
http://comments.gmane.org/gmane.linux.kernel.input/19632
Don't know the current situation,
Simon
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo
/tags/v3.12#n301
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/hid/hid-sony.c?id=61ab44bebdefab296487e7cd723a634849278827
Do we need to fix this is the HID descriptor, or in 'hid-sony' input stuff?
Do you have example of another driver to copy?
Simon
On Wed, 6 Nov 2013, Simon Wood wrote:
Adjust the scaling and lineartity to match that of the Windows
driver (from MOMO testing).
Reported-by: Elias Vanderstuyft elias@gmail.com
Signed-off-by: Simon Wood si...@mungewell.org
I have applied the series, thanks.
Thanks to all involved
won't fix the kernel interface
anyway, but I was just curios: is there any known userspace using the
gamepad API?
SDL are talking about 'fixing things' just in-case we're breaking it
(again) for them
http://lists.libsdl.org/pipermail/sdl-libsdl.org/2013-November/091850.html
Simon
Sony Dualshock 3 controllers have two motors which can be used to provide
simple force feedback rumble effects. The right motor is can be used to
create
a weak rumble effect but does not allow to set the force. The left motor
is
used to create a strong rumble effect with adjustable
to get the Intec to rumble. Which runs without crashing machine.
Simon#!/usr/bin/python
#
# Small script to test the rumble on a PS3 gamepad
#
import usb
import time
rumble = 0
busses = usb.busses()
for bus in busses:
devices = bus.devices
for dev in devices:
if dev.idVendor
-lg4ff:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/hid/hid-lg4ff.c?id=refs/tags/v3.12#n402
Simon
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
drivers/hid/hid-sony.c | 53
+++---
1 file changed, 42 insertions(+), 11 deletions(-)
Doesn't this miss patching Kconfig (previous changes were reverted).
Simon
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body
On Sunday 17 November 2013 14:46:32 si...@mungewell.org wrote:
drivers/hid/hid-sony.c | 53
+++---
1 file changed, 42 insertions(+), 11 deletions(-)
Doesn't this miss patching Kconfig (previous changes were reverted).
Simon
@Simon: This may also be interesting for you because you've asked for it
in 8c40cb08b7c44f373c2c533614d70b6a.squir...@mungewell.org
Yes, very interesting. Builds on top of the other 2 patches.
This seems to work, however something is causing the LEDs to go out once
they have been set
Intec, but not with the SixAxis.
Simon
#!/usr/bin/python
#
# Small script to test the rumble on a PS3 gamepad
#
import usb
import time
rumble = 0
busses = usb.busses()
for bus in busses:
devices = bus.devices
for dev in devices:
if dev.idVendor == 0x054c and dev.idProduct
benjamin.tissoi...@redhat.com
Wow, its been a great week for the DualShock - got rumble and LED control,
and now I can confirm that the 'left D pad' analogue axis works.
Thanks guys,
Simon
tested-by: Simon Wood si...@mungewell.org
--
To unsubscribe from this list: send the line unsubscribe linux
confused about which kernel this should be in. I believe the
first in this patch series is required for 3.13 (but does not seemed to be
included (1)).
Without this, the kernel will be subject to lockups if anyone actually
uses the force feedback.
Simon
(1) -
https://git.kernel.org/cgit/linux
Anyone here want to collaborate?
I've decoded the majority of the HID stream including the multi-touch.
Also some good teardown info/pictures here:
http://mygaming.co.za/news/ps4/60397-cost-of-building-a-ps4.html
fccid = AK8CUHZCT1
ic = 409B-CUHZCT1
Simon.01 7e 7c 80 7f 08 00 04 00 00 6f 35
simon@womble:~/dualshock4$ sdptool records 1C:66:6D:07:C3:E0
Service Name: Wireless Controller
Service Description: Game Controller
Service Provider: Sony Computer Entertainment
Service RecHandle: 0x10001
Service Class ID List:
Human Interface Device (0x1124)
Protocol Descriptor List:
L2CAP
\:054C\:05C4.0006/report_descriptor'.
Unfortunately I wasn't able to decode it.
--
simon@womble:~/dualshock4$ ~/hidrd-0.2.0/src/hidrd-convert des_bt.bin -o code
Failed to read input item at offset 356:
invalid item encountered
--
Thanks for the other suggestions.
Simon
des_bt.bin
Description: Binary
. I am testing with the
DS4 connected with USB (not BT).
--
Jan 4 17:55:14 simon-virtual-machine kernel: [ 138.964626] usb 1-1: new
full-speed USB device number 3 using ohci-pci
Jan 4 17:55:14 simon-virtual-machine mtp-probe: checking bus 1, device 3:
/sys/devices/pci:00/:00:06.0/usb1/1-1
.
drwxr-xr-x 7 root root0 Jan 8 20:20 ..
lrwxrwxrwx 1 root root0 Jan 8 20:21 driver -
../../../../../../../bus/hid/drivers/hid-generic
--
Further more my DS3-SixAxis appears to work OK with the full kernel, where
the DS4 does not any suggestions?
Simon
--
To unsubscribe from this list
LEDs are listed in
'/sys/class/leds', but they don't change when instructed. They stay solid
white.
Cheers,
Simon
Tested-by: Simon Wood si...@mungewell.org
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo
\:054C\:05C4.0006/report_descriptor'.
Unfortunately I wasn't able to decode it.
--
simon@womble:~/dualshock4$ ~/hidrd-0.2.0/src/hidrd-convert des_bt.bin -o
code
Failed to read input item at offset 356:
invalid item encountered
--
After playing some more with the DS4, I noticed the comment
'pair'), but I believe that the kernel
stuff is OK.
Simon
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Use regular HID output reports instead of raw reports in the
dualshock4_state_worker function. (Thanks Simon Mungewell)
This description is actually wrong. hid_output_raw_report() is used
for regular HID output reports. What you do, is using SET_REPORT to
synchronously set output-reports
5c c5 73 41 25 44 8a 06 13
--
Simon.
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
for certain.
In my testing from a year ago or so, I could make the blink work via
sending data with python. The script can be found here:
http://www.spinics.net/lists/linux-input/msg28271.html
Note: Which LED to enable(LED1..4 1, 0x20=none)
Cheers,
Simon
--
To unsubscribe from this list: send
the blue
trigger set as 'timer' (or 'heartbeat') to cause a 'off-purple' blinking.
This would remove the contention in your scheme of having two places/leds
('red' and 'all') which could be set differently.
I can see if there's still some code on my disk if others are interested
in the idea.
Simon
can turn LEDs off/on straight away.
Cheers,
Simon
From a0597309d26ddecb5d4662d9e3bcb4d2689b7ed5 Mon Sep 17 00:00:00 2001
From: Simon Wood si...@mungewell.org
Date: Tue, 8 Apr 2014 21:39:59 -0600
Subject: [PATCH] HID: hid-sony - allow 3rd party INTEC controller to turn off
all leds
Without
://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/hid/hid-lgff.c?id=refs/tags/v3.15-rc1#n137
Can anyone see what might be wrong with the report, to cause this code to
spit out an error?
Cheers,
Simon.0x05, 0x01, /* Usage Page (Desktop), */
0x09, 0x05
of which 'Report ID's are actually used? If so, it possible that the
change has broken a number of devices...
I am trying to get the end user to test with an older kernel to see
whether his device was always 'broken'.
Thanks.
Simon
--
To unsubscribe from this list: send the line unsubscribe linux
which use hid-lgff, but have some which use
hid-lg4ff which was also changed to perform the same test. I can check
their operation/HID reports over the weekend.
Simon.
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More
,
however I think that this is probably unavoidable with current LED class
and this controller - it probably needs some overall discussion how the
LED class treats RGB leds.
I'd suggest that we use this patch series.
Thanks,
Simon.
tested-by Simon Wood si...@mungewell.org
DS4 failure when using
a chance to build this series of patches and test with the
controllers I have (*). Without specific instructions I wasn't sure
exactly what to test, but it seems to be OK and the devices
rumbled/wobbled appropriately,
Simon
tested-by: Simon Wood si...@mungewell.org
* controllers:
hid-sony: DS4, DS3SA
Port hid-lg4ff to ff-memless-next
Signed-off-by: Simon Wood si...@mungewell.org
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
.
Simon
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
, which occurs on
other times.
I have not found a trigger yet, but was wondering whether others are
seeing this. I am using a USB connected DS4 (no BT on this machine). OS is
Xubuntu 13.10 with patched kernel,
Simon.
--
simon@slipstream:~$ jstest /dev/input/js0
Driver version is 2.1.0.
Joystick
into a LiveCD of Xubuntu 14.04 (kernel 3.13.0-24) does not show
problem, but it is not using hid-sony for this device. Just shows 8 axis
available.
Simon.
Simon.
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More
to the controller state (ie alive after
first plug)? We see that the DS3 behaves differently wrt leds depending on
whether it is asleep or alive when plugged in.
I'll dig a little deeper tonight to see if I can track the problem down.
Simon.
--
To unsubscribe from this list: send the line unsubscribe
It might be a matter of the joydev module not being loaded into memory
the first time thus allowing the probe function to complete and set the
proper axis bits before the js* device is created. On subsequent
connects the module would already be loaded so the js* device would be
created
, report_enum-report_list);
-Kees
I tried this patch last night and saw Kernel Panics on controller
insertion and/or removal
And just noticed that you have another more recent one, so I'll try that
tonight. My bad :-(
Simon.
--
To unsubscribe from this list: send the line unsubscribe linux-input
hardware to test against...?
Simon.
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
gaming wheel(s). This is believed to be a fault with
the application not using correct bit-field testing and appears to have
been fixed on later versions (Xubuntu 13.10).
I also built v4, but have not yet had time/access to all the devices
(other than DS4) to test.
Cheers,
Simon
Tested-by: Simon
Port hid-lg4ff to ff-memless-next
Signed-off-by: Michal Malý madcatxs...@devoid-pointer.net
Tested-by: Tested-by: Elias Vanderstuyft elias@gmail.com
Signed-off-by: Simon Wood si...@mungewell.org
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body
about what they can really do - ie. gamepads claiming periodic ability
when all they are doing is faking it with rumble.
Simon.
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
designers to improve controller performance. If any information can be
feed 'forward' to improve the Linux driver, that would be useful too.
Many thanks,
Simon Wood.
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More
that applications can know which effects are really supported, and
enable/disable emulation somehow?
Apologies for asking some many questions, without answering anything...
Simon
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
to calibrate and unify
the force responses across different models.
There was some discussion about rate limiting the USB packets to the
wheel, and how to deal if app updates too quickly. Is there an upper limit
for the wheel itself, or is it just the USB 'pipe' which is the limiting
factor?
Simon
,
-1
};
--
Simon
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
... but I'm not saying that you
should :-).
Simon
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
library to
handle sending multiple force feedback signals to 'simple' devices,
perhaps you should engage with them.
Simon
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
, G27, DFGT) */
+#define LG4FF_MSW_G25 3 /* Switch device so that it emulates
G25 (only
G27) */
+#define LG4FF_MSW_MAX 3
Just to let everyone know I am looking at this patch, and have emailed
Michal some questions on whether it covers all options for control.
Cheers,
Simon
Simon mailed me his revised patchset which has the changes broken out into
four separate patches and allows to switch extended compatibility modes
on
the fly through sysfs. I looked them over and I they seem fine to me. I
suppose he'll submit them for review very soon.
Whilst it is my
Even if I did add the plumbing for HID over into the LED subsystem, is
there an
easy way to correlate input devices and their LEDs from userspace?
You can follow the symlinks through the '/sys' filesystem. For example the
following all point to the same LED.
--
simon@womble:~$ ls
/sys/class
should automatically cope with new wheels in the future.
Thanks to Michal for undertaking this work. I have been testing the code
over the past weeks and believe it to be working, I will confirm mid-next
week when I can gain access to my wheels.
Simon
--
To unsubscribe from this list: send
.
Thanks,
Simon
--
tested-by: Simon Wood si...@mungewell.org
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
bug.
I guess it's possible, I am running 3.19.0rc5. I'll build 3.19 and see if
it's showing the bug.
Simon
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo
pulled and built. It definately had
the patch (I looked in drivers/leds/leds.h before building) but built as
3.19 guess I'll just have a confused expression for the rest of the
day.
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/leds/leds.h
Simon.
--
To unsubscribe
transport (HID over Bluetooth or the like)?
Simon.
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
0003:046D:C298.000F: G27 Racing Wheel cannot be switched to DF-EX
mode. Load the hid_logitech module with lg4ff_no_autoswitch=1
parameter set and try again.
--
Would it make more sense to use EPERM, or is there another error code we
can throw to be more informative.
Thanks,
Simon
. IIRC
there was some 'magic' done with hid-steelseries to tweak problems with
LEDs.
I'd be open to helping this happen, given some guidance.
Simon
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo info
exposing them on the joystick interface) make sense?
Are there any examples of other devices doing this, so I can re-use the code?
Simon.
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
/way to reshuffle this data, or is this just how
it needs to be?
Given that more controllers are coming with 'motion' controls, is there a
framework in place for unifying support?
Cheers,
Simon.
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message
the 'original' reports (ie. with hid-sony changing them)
for reference. Note the BT one has a trailing zero (like the DS4 has)
which prevents decoding... I just cropped it off to decode.
Simon.
psmove_bt_report_orig.bin
Description: Binary data
psmove_bt_report_orig.code
Description: Binary data
this for accelerometers that are in tablets/convertibles:
https://github.com/hadess/iio-sensor-proxy/
Thanks I'll check it out. Thinking more of a AHRS rather than 'just'
rotating the screen. ;-)
Simon
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord
the SixAxis also have a gyroscope, I don't know how useful/reliable it
is, but it's there.
I had a recollection that there was a gyro, but didn't see it when looking
at the 'hidraw' stream.
It might be affected by the 'multi-touch axes' bug.
Simon
--
To unsubscribe from this list: send
is it? And BTW I get 9.80665/117 = 0.083817521
The '117' was taken from experimentation, average value accessed across
all accelerometer axis on a stationary device.
It does appear however that I can not use a calculator ;-) (...must have
been a prior value left there).
Simon.
--
To unsubscribe from
to be
a little careful.
Is there a 'short-cut' we can use if a HID device is only required to
trigger itself (and not other iio devices)? ie. not need true interrupt
system.
Simon.
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord
around I got the triggers working as well, I can
self trigger and even trigger another (iio-dummy) device.
However I couldn't trigger two devices at the same time from a single
trigger, is this normal for IIO?
Next is a little code clean-up and I'll post what I have for some more
comments,
Simon
settings work, but are then overridden (LED goes dark) after ~5s when
connected with USB. I believe that this is a 'feature' of the controller
with USB connection (and note there is no HID stream coming from the
device).
Does any one know of a trigger/command which will enable full USB operation?
Simon
the on Bluetooth list, and
appear in both the HID and the HCI streams (suggesting that they are
really sent from device). They are not seen on the USB connection.
Dropping them in 'raw_event()' seems a sensible approach,
Simon.
* http://www.spinics.net/lists/linux-bluetooth/msg63028.html
Signed
> The first patch might conflict with Simon's current work in progress, so
> that's why Simon is CC-ed to it.
Thanks for the 'heads-up', I think that the HID++ stuff I have in progress
won't be ready until the 4.4 cycle,
Cheers,
Simon
--
To unsubscribe from this list: send the line "
urn).
The mode should be selectable something like
--
root@retrobox:/home/simon# cd /sys/bus/hid/devices/0003\:046D\:C29B.0002
root@retrobox:/sys/bus/hid/devices/0003:046D:C29B.0002# ls
alternate_modes country driver hidraw input leds modalias power
range real_id report_descriptor subsyst
From: Simon Budig simon.bu...@kernelconcepts.de
This is a driver for the EDT Polytouch family of touch controllers
based on the FocalTech FT5x06 line of chips.
Signed-off-by: Simon Budig simon.bu...@kernelconcepts.de
---
Documentation/input/edt-ft5x06.txt | 56 ++
drivers/input
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/19/2012 03:50 PM, Henrik Rydberg wrote:
Looking good, just a question for Simon: In the mt report
function, the loop uses every fourth byte of rdbuf, but the access
looks a bit funny; buf[5], buf[6] etc. It is fine as long as it
works, just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/23/2012 07:45 PM, Henrik Rydberg wrote:
It looks all good to me, Reviewed-by: Henrik Rydberg
rydb...@euromail.se Thanks, Simon, for all your work.
Great, thanks. Is there something I have to do now? Or will you
incorporate this into your tree
On Wednesday 1 August 2012 11:50:28 Benjamin Tissoires wrote:
Hi Simon,
well, it's a known bug. This panel is now fixed in 3.6-rc0, and I
submitted the fix for stable. I'm still waiting for the stable
approval.
snip
PS: the fix is at
http://git.kernel.org/?p=linux/kernel/git/torvalds
edt_ft5x06_ts_data' has no member named 'raw_buffer'
Yeah, unfortunate oversight on my part.
Guenter Roeck provided a patch for this issue which looks good to me.
(Aug 7th, linux-input mailinglist)
Dmitry: Can you upstream this? Is there any action required on my part?
Thanks,
Simon
On Tuesday 21 August 2012 21:06:26 Henrik Rydberg wrote:
Hi Simon,
We're going through our collection of touch screens, making sure that they
all
work with current kernels, and we've found one that doesn't work with
today's
Linus master.
lsusb describes the screen as:
Bus
1 - 100 of 238 matches
Mail list logo
