On 11/08/07, Jiri Kosina <[EMAIL PROTECTED]> wrote:
> Force feedback functionality shouldn't be influenced in any means by this
> patch - FF implementation doesn't care about the values of the
> input_dev->abs{max,min,fuzz,flat}.
So it means the patch should work for all other joysticks as well?
T
On Sat, 11 Aug 2007, Renato Golin wrote:
> fixes perfectly. But it probably breaks the output range and kills the
> force-feedback.
Thanks for testing.
Force feedback functionality shouldn't be influenced in any means by this
patch - FF implementation doesn't care about the values of the
inpu
On 10/08/07, Jiri Kosina <[EMAIL PROTECTED]> wrote:
> does the attached patch (against 2.6.23-rc2) fix the problem with axis
> ranges for you please?
Hi Jiri,
fixes perfectly. But it probably breaks the output range and kills the
force-feedback.
I couldn't find fftest for debian (the package wit
On Fri, 10 Aug 2007, Renato Golin wrote:
> I've never tried force-feedback with it (or it never worked) as I don't
> know which games support it (I thought none did).
You can use fftest utility (part of input-utils) which can be used to test
FF capabilities of the device.
> I'll apply the patc
On 10/08/07, Jiri Kosina <[EMAIL PROTECTED]> wrote:
> Renato, does force feedback work properly in Linux with this device? If
> so, that would mean that the device has logical maximum and minimum for X
> and Y axes different in input and output, and we would need to handle this
> properly (we curre
On Fri, 10 Aug 2007, Jiri Kosina wrote:
> Renato, does force feedback work properly in Linux with this device? If
> so, that would mean that the device has logical maximum and minimum for
> X and Y axes different in input and output, and we would need to handle
> this properly (we currently don
On Sat, 21 Jul 2007, Renato Golin wrote:
> sorry for the delay, below the report descriptor and attached is the
> full report when I've connected the joystick.
Hi Renato,
I guess I can now see the problem. The important parts of the dump are
[11165.496717] INPUT(6)[INPUT]
[11165.496722]
On 20/06/07, Jiri Kosina <[EMAIL PROTECTED]> wrote:
Could you please send me the report descriptor of the device, so that I
could debug it locally here?
Hi Jiri,
sorry for the delay, below the report descriptor and attached is the
full report when I've connected the joystick.
report descript
On Thu, 14 Jun 2007, Renato Golin wrote:
> Applied your patch and the log is below,
[...]
> [ 6973.596722] calling input_set_abs_params, code: 0, min: ff81,
> max: 7f, fuzz: 0, flat: f
> [ 6973.596724] Absolute.X
> [ 6973.596732] calling input_set_abs_params, code: 1, min: ff81,
> max: 7f,
On 12/06/07, Jiri Kosina <[EMAIL PROTECTED]> wrote:
could you please apply the stupid patch below (against 2.6.20, I know you
are using it :) ) and report the result? It should show us whether the
values 0 and 4096 (which can be seen in your hid parsing debug dump) are
correctly passed from HID t
On Tue, 12 Jun 2007, Renato Golin wrote:
> At joydev_connect, the last parameter "input_dev" reports me that range
> (dev->absmax[i] and dev->absmin[i]). When I turned on HID_DEBUG it
> reported [0, 4096] for both axis 0 and 1, which is correct so it must be
> between HID and joydev.
Renato,
On 6/12/07, Renato Golin <[EMAIL PROTECTED]> wrote:
On 12/06/07, Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
> We need to find out why you see [-127, 127] range, because if joydev
> would see [0, 4096] range it would perform automatic correction and
> map values like this:
>
> c0: 2048, c1: 2048,
On 12/06/07, Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
We need to find out why you see [-127, 127] range, because if joydev
would see [0, 4096] range it would perform automatic correction and
map values like this:
c0: 2048, c1: 2048, c2: 262144, c3: 262144
Hi Dmitry,
That's the values I got
Hi Renato,
On 6/12/07, Renato Golin <[EMAIL PROTECTED]> wrote:
On 12/06/07, Jiri Kosina <[EMAIL PROTECTED]> wrote:
> the thing is that the aim of this quirk is to normalize the values that
> are being reported by bogus devices, so we don't really want to trust the
> values they provide here, do
On 12/06/07, Jiri Kosina <[EMAIL PROTECTED]> wrote:
the thing is that the aim of this quirk is to normalize the values that
are being reported by bogus devices, so we don't really want to trust the
values they provide here, do we?
Hi Jiri,
I don't know about the other joysticks, but Saitek did
On Mon, 4 Jun 2007, Renato Golin wrote:
> > sorry, don't fully understand - what do you mean by "got the messages
> > but not the fix"?
> The range "detected" was 0 to 255 but both X and Y axis are reporting
> 4096.
> I think that the code in drivers/hid/hid-input.c:
> if ((device->quirks & HID_
On 04/06/07, Renato Golin <[EMAIL PROTECTED]> wrote:
> Well calibration using jscal might be needed, that should be fine. The
> question is whether the ranges are now correct and calibration using jscal
> works fine.
Ok, so maybe in that case my automatic calibration is still worth to
put on joy
On 04/06/07, Jiri Kosina <[EMAIL PROTECTED]> wrote:
sorry, don't fully understand - what do you mean by "got the messages but
not the fix"?
The range "detected" was 0 to 255 but both X and Y axis are reporting 4096.
I think that the code in drivers/hid/hid-input.c:
if ((device->quirks & HID_QU
On Mon, 4 Jun 2007, Renato Golin wrote:
> Patched and run, we're almost there... I put an additional printk on
> usb/input/hid-core.c and hid/hid-input.c to assure I got the right copy,
> got the messages but not the fix.
Hi Renato,
sorry, don't fully understand - what do you mean by "got the
On 03/06/07, Jiri Kosina <[EMAIL PROTECTED]> wrote:
Please try this patch on top of 2.6.20
Hi Jiri,
Patched and run, we're almost there... I put an additional printk on
usb/input/hid-core.c and hid/hid-input.c to assure I got the right
copy, got the messages but not the fix.
What joydev repor
On Fri, 1 Jun 2007, Renato Golin wrote:
> 06a3:ffb5 Saitek PLC
Please try this patch on top of 2.6.20
diff --git a/drivers/usb/input/hid-core.c b/drivers/usb/input/hid-core.c
index c6c9e72..d73f949 100644
--- a/drivers/usb/input/hid-core.c
+++ b/drivers/usb/input/hid-core.c
@@ -692,6 +692,7 @@ v
On 31/05/07, Jiri Kosina <[EMAIL PROTECTED]> wrote:
Yes, the problem with axis ranges definitely looks like that. Renato,
could you please send me vendor id and product id of the joystick in
question, I will send you a patch to test whether normalizing the values
on hid-level (as we already do fo
On Thu, 31 May 2007, Jiri Kosina wrote:
> Yes, the problem with axis ranges definitely looks like that. Renato,
> could you please send me vendor id and product id of the joystick in
> question, I will send you a patch to test whether normalizing the values
> on hid-level (as we already do for
On Thu, 31 May 2007, Dmitry Torokhov wrote:
> > Now, why joydev's input_dev is reporting -127, 127 just for the two
> > first axis?
> Is it getting hit with HID_QUIRK_BADPAD? What does evtest utility show
> for the device?
Yes, the problem with axis ranges definitely looks like that. Renato,
co
On 5/30/07, Renato Golin <[EMAIL PROTECTED]> wrote:
Now, why joydev's input_dev is reporting -127, 127 just for the two first axis?
Is it getting hit with HID_QUIRK_BADPAD? What does evtest utility show
for the device?
--
Dmitry
-
To unsubscribe from this list: send the line "unsubscribe linu
On 30/05/07, Renato Golin <[EMAIL PROTECTED]> wrote:
On 30/05/07, Jiri Kosina <[EMAIL PROTECTED]> wrote:
> do any data appear in the kernel log when you generate events with the
> device (i.e. move the joystick, press the buttons, etc)? That should be
> reported if DEBUG_DATA is defined properly
On 30/05/07, Jiri Kosina <[EMAIL PROTECTED]> wrote:
do any data appear in the kernel log when you generate events with the
device (i.e. move the joystick, press the buttons, etc)? That should be
reported if DEBUG_DATA is defined properly on the older kernels.
Not at all... only my own debug mes
On Wed, 30 May 2007, Renato Golin wrote:
> But it's pathetic the fact that ubuntu's kernel have an option USB_DEBUG
> I did it and monitored mesasges and syslog and both shows the same
> data... I guess that dump after mouse detection is DEBUG_DATA in place.
Hi Renato,
do any data appear in th
On 30/05/07, Jiri Kosina <[EMAIL PROTECTED]> wrote:
well I have changed the overall HID code design in 2.6.21 a little bit.
Anyway, just hardcoding '#define DEBUG' and '#define DEBUG_DATA' (that's
also important) in 2.6.20-and-older kernels should have similar result as
CONFIG_HID_DEBUG in post-2
On Wed, 30 May 2007, Renato Golin wrote:
> The HID sources are quite different from 2.6.21 and 2.6.20 but I don't
> know how much was because Canonical guys and how much it really changed.
> :( I will eventually put a Gentoo on my old laptop and try it for real,
> sorry I couldn't be of much he
On 21/05/07, Jiri Kosina <[EMAIL PROTECTED]> wrote:
could you please turn on the HID debugging support ("Device Drivers -> HID
devices -> HID debugging support" in menuconfig of any reasonably recent
kernel) and show the output that appears when the joystick is plugged in,
and also when you gener
On 21/05/07, Jiri Kosina <[EMAIL PROTECTED]> wrote:
could you please turn on the HID debugging support ("Device Drivers -> HID
devices -> HID debugging support" in menuconfig of any reasonably recent
kernel) and show the output that appears when the joystick is plugged in,
and also when you gener
On Mon, 21 May 2007, Dmitry Torokhov wrote:
> > I have a Saitek Cyborg Evo Force, a very good joystick with force-
> > feedback. Problem is, on Windows it works well (its drivers know its
> > own idiosyncrasies) but on Linux it gets a bit fuzzy.
> I think we need to make HID driver to report rea
On Friday 18 May 2007 09:54, Renato Golin wrote:
> Hi,
>
> I'm a kernel newbie so please, pardon my French.
>
> I have a Saitek Cyborg Evo Force, a very good joystick with force-
> feedback. Problem is, on Windows it works well (its drivers know its
> own idiosyncrasies) but on Linux it gets a bi
On 18/05/07, Renato Golin <[EMAIL PROTECTED]> wrote:
Problem is, on joydev_connect, when defining the corrections for every
axis, the joystick is reporting dev->absmax = 127 and dev->absmin =
-127 for both axis 0 and 1, so the correction is based on a signed
range when the joystick is actually se
Hi,
I'm a kernel newbie so please, pardon my French.
I have a Saitek Cyborg Evo Force, a very good joystick with force-
feedback. Problem is, on Windows it works well (its drivers know its
own idiosyncrasies) but on Linux it gets a bit fuzzy.
The behaviour is that, all axis are working fine, ex
36 matches
Mail list logo
