From: Flameeyes <dgp85@users.sourceforge.net>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] Sidewinder debug information
Date: Mon, 22 Dec 2003 19:18:53 +0000 [thread overview]
Message-ID: <200312221918.53891.dgp85@users.sourceforge.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 466 bytes --]
Hi,
with 2.6.0 kernel, I have some troubles with sidewinder support.
It works perfectly, but when using it, the kernel log is fullfilled by
messages like these:
sidewinder.c: Read 5 triplets. [77773]
sidewinder.c: Read 5 triplets. [77773]
so dmesg command it's useless.
With the attached patch the SWDEBUG is removed and the messages aren't
printed.
--
Flameeyes <dgp85@users.sourceforge.net>
You can find LIRC for 2.6 kernels at
http://flameeyes.web.ctonet.it/
[-- Attachment #2: sidewinder-debug.diff --]
[-- Type: text/x-diff, Size: 463 bytes --]
--- linux/drivers/input/joystick/sidewinder.c.orig 2003-12-22 19:05:48.147132360 +0000
+++ linux/drivers/input/joystick/sidewinder.c 2003-12-22 19:05:54.770125512 +0000
@@ -45,8 +45,6 @@ MODULE_LICENSE("GPL");
* as well as break everything.
*/
-#define SW_DEBUG
-
#define SW_START 400 /* The time we wait for the first bit [400 us] */
#define SW_STROBE 45 /* Max time per bit [45 us] */
#define SW_TIMEOUT 4000 /* Wait for everything to settle [4 ms] */
reply other threads:[~2003-12-22 18:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200312221918.53891.dgp85@users.sourceforge.net \
--to=dgp85@users.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.