mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Renato Golin" <rengolin@gmail.com>
To: "Jiri Kosina" <jkosina@suse.cz>
Cc: linux-kernel@vger.kernel.org, "Dmitry Torokhov" <dtor@insightbb.com>
Subject: Re: joydev.c and saitek cyborg evo force
Date: Wed, 30 May 2007 10:14:31 +0100	[thread overview]
Message-ID: <d9b9d95f0705300214u7eb257fg783aefd73077d33@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0705300207160.3961@jikos.suse.cz>

On 30/05/07, Jiri Kosina <jkosina@suse.cz> 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.6.21.
>
> In your particular case, the DEBUG_DATA might really be more interesting.

Yup, did both on all drivers/hid/*.c and drivers/usb/input/hid*.c
recompiled and reloaded all modules (hid.ko, usbhid.ko and joydev.ko)

But it's pathetic the fact that ubuntu's kernel have an option
USB_DEBUG and on Makefile is says "if USB_DEBUG; aditional_opt=
-DDEBUG" but inside the files all DEBUG flags are hardcoded undefined.

Also, to turn on KERN_DEBUG messages I saw on kernel hacking webpages:

$ echo 15 15 15 15 > /proc/sys/kernel/printk
$ echo 8 > /proc/sys/kernel/printk

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.

cheers,
--renato

Reclaim your digital rights, eliminate DRM, learn more at
http://www.defectivebydesign.org/what_is_drm

  reply	other threads:[~2007-05-30  9:14 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18 13:54 Renato Golin
2007-05-18 21:35 ` Renato Golin
2007-05-21  4:16 ` Dmitry Torokhov
2007-05-21 12:49   ` Jiri Kosina
2007-05-24 13:27     ` Renato Golin
2007-05-29 23:57     ` Renato Golin
2007-05-30  0:10       ` Jiri Kosina
2007-05-30  9:14         ` Renato Golin [this message]
2007-05-30 14:56           ` Jiri Kosina
2007-05-30 15:18             ` Renato Golin
2007-05-30 22:26               ` Renato Golin
2007-05-31 19:53                 ` Dmitry Torokhov
2007-05-31 20:22                   ` Jiri Kosina
2007-05-31 21:48                     ` Jiri Kosina
2007-06-01 18:16                     ` Renato Golin
2007-06-03  9:41                       ` Jiri Kosina
2007-06-04 22:06                         ` Renato Golin
2007-06-04 22:10                           ` Jiri Kosina
2007-06-04 22:46                             ` Renato Golin
2007-06-12 12:28                               ` Renato Golin
2007-06-12 12:37                               ` Jiri Kosina
2007-06-12 13:08                                 ` Renato Golin
2007-06-12 13:13                                   ` Dmitry Torokhov
2007-06-12 13:31                                     ` Renato Golin
2007-06-12 13:45                                       ` Dmitry Torokhov
2007-06-12 15:25                                       ` Jiri Kosina
2007-06-14 22:24                                         ` Renato Golin
2007-06-20 10:00                                           ` Jiri Kosina
2007-07-21  0:10                                             ` Renato Golin
2007-08-10 15:10                                               ` Jiri Kosina
2007-08-10 15:54                                                 ` Jiri Kosina
2007-08-11 17:38                                                   ` Renato Golin
2007-08-11 21:06                                                     ` Jiri Kosina
2007-08-11 21:15                                                       ` Renato Golin
2007-08-10 16:31                                                 ` Renato Golin
2007-08-11 13:42                                                   ` Jiri Kosina

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d9b9d95f0705300214u7eb257fg783aefd73077d33@mail.gmail.com \
    --to=rengolin@gmail.com \
    --cc=dtor@insightbb.com \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome