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 messages from joydev (like: recalibrating for value 2048) when a new limit is reached. I've even changed "printk(KERN_DEBUG ...)" to a plain printk() as I do on joydev to avoid fall into the wrong log level but didn't work as well. I've changed USB DEBUG in menuconfig, saved the new conf. The files I've changed manually (undef -> define) were: -> drivers/hid/ hid-core.c:#undef DEBUG hid-core.c:#undef DEBUG_DATA hid-input.c:#undef DEBUG -> drivers/usb/input/ hid-core.c:#undef DEBUG hid-core.c:#undef DEBUG_DATA hid-ff.c:#undef DEBUG hid-tmff.c:#undef DEBUG than $ make drivers/hid/hid.ko drivers/usb/input/usbhid.ko $ rmmod usbhid hid ; modprobe usbhid hid the output from the last mail was on both /var/log/messages and syslog, although syslog had other messages from the network card (using ndiswrapper). cheers, --renato Reclaim your digital rights, eliminate DRM, learn more at http://www.defectivebydesign.org/what_is_drm - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
