02 Nov, 2017
1 commit
-
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.By default all files without license information are under the default
license of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'
SPDX license identifier. The SPDX identifier is a legally binding
shorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the use cases:
- file had no licensing information it it.
- file was a */uapi/* one with no licensing information in it,
- file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was:
- Files considered eligible had to be source code files.
- Make and config files were included as candidates if they contained >5
lines of source
- File already had some variant of a license header in it (even if
Reviewed-by: Philippe Ombredanne
Reviewed-by: Thomas Gleixner
Signed-off-by: Greg Kroah-Hartman
19 Feb, 2015
1 commit
-
Introduce a module parameter to disable automatic switch of Logitech gaming
wheels from compatibility to native mode. This only applies to multimode wheels.Signed-off-by: Michal Malý
Tested-by: Simon Wood
Signed-off-by: Jiri Kosina
25 Sep, 2012
1 commit
-
Range limiting command for the Driving Force Pro wheel is only a FF_SPRING
effect so that the wheel creates resistance when the user tries to turn it past
the limit. It is however possible to overpower the FFB motors quite easily which
leads to the X axis value exceeding the expected limit. This confuses
games which dynamically adjust calibration using the highest/lowest min and max
values reported by the wheel. Joydev device driver also doesn't take in account
any changes in an axis range after the joystick device is created.This patch recalculates received ABS_X axis value so it is always in
range where 0 is the left limit and 16383 the right limit.
Logitech driver for Windows does the same thing. As for any concerns about
possible loss of precision, I compared a large set of raw/adjusted values
generated by "mult_frac" to values returned by the Windows driver and I got
a 100% match.Other Logitech wheels will probably need a similar fix, but I currently lack
the information needed to write one.Signed-off-by: Michal Malý
Signed-off-by: Jiri Kosina
03 Apr, 2012
2 commits
-
This patch fixes a possible race condition caused by the sysfs
interface being removed after the memory used by the interface
was already kfree'd.Signed-off-by: Michal Malý
Signed-off-by: Jiri Kosina -
This patch adds support for custom device-specific properties which can now be
stored as private driver data and read/saved using hid_get/set_drvdata().Signed-off-by: Michal Malý
Tested-by: simon@mungewell.org
Signed-off-by: Jiri Kosina
04 Aug, 2011
2 commits
-
The description of lg4ff driver has to be changed to reflect the fact that the
driver now handles a lot more Logitech wh the Wii. Entry in Kconfig has been
renamed to LOGIWHEELS_FFSigned-off-by: Michal Malý
Signed-off-by: Simon Wood
Signed-off-by: Jiri Kosina -
Wheel range of certain Logitech wheels - namely Driving Force GT, Driving Force
Pro, G25 and G27 can be adjusted. Minimu is 40 degrees, maximum 900. DFGT, G25
and G27 all use a common command, DFP uses another one. Range can be set from
userspace by writing to
"/sys/module/hid_logitech/drivers/hid:logitech/range". The driver use list
to store range of each connected wheel; it's not possible to use driver_data in
hid_device struct as it's already b hig-lg driver.Signed-off-by: Michal Malý
Signed-off-by: Simon Wood
Signed-off-by: Jiri Kosina
22 Sep, 2010
1 commit
-
The following patch adds support for the Logitech Speed Force Wireless gaming
wheel. Originally designed for the WII console. Details on the protocol:http://wiibrew.org/wiki/Logitech_USB_steering_wheel
This patch relies on previous patch:
"Don't Send Feature Reports on Interrupt Endpoint"Logitech as produce a very similar wheel for the PS2/PS3, it is expected that
this patch could also support the PS2/PS3 wheel if the USB ID's are added and
(if required) the HID descriptor is modified.Signed-off-by: Simon Wood
Signed-off-by: Jiri Kosina
03 Feb, 2010
1 commit
-
Conflicts:
drivers/hid/hid-ids.h
13 Jan, 2010
1 commit
-
Implements a new USB-HID for Force Feedback based on the normal
Logitech Force Feedback code and FF-Memless.Currently only supports the FF_CONSTANT effect although the joystick
appears to support additional non-standard ones.Signed-off-by: Gary Stein
Signed-off-by: Jiri Kosina
12 Dec, 2009
1 commit
-
kbuild.h forces include of autoconf.h on the
commandline using -include - so we do not need to
include the file explicit.Signed-off-by: Sam Ravnborg
Signed-off-by: Michal Marek
15 Oct, 2008
1 commit
-
Merge the logitech force feedback processing directly into logitech
driver from the usbhid core.Signed-off-by: Jiri Slaby
Signed-off-by: Jiri Kosina
