From: "Renato Golin" <rengolin@gmail.com>
To: "Jiri Kosina" <jkosina@suse.cz>
Cc: linux-kernel@vger.kernel.org,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>
Subject: Re: joydev.c and saitek cyborg evo force
Date: Mon, 4 Jun 2007 23:06:34 +0100 [thread overview]
Message-ID: <d9b9d95f0706041506l257819a7pbcb8b8efc2eec049@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706031139570.5177@jikos.suse.cz>
On 03/06/07, Jiri Kosina <jkosina@suse.cz> 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 reports is a range between 0 and 255, which is better than
-127 to 127 because it's unsigned but still requires further
calibration.
> I have never used ubuntu, but why should that be that difficult? Just
> download vanilla kernel from kernel.org, use your distro's .config, make
> oldconfig && make ... ?
The kernel is really simple, problem is that I use ubuntu since
version 5 and did distupgrade to 6.06, 6.10 and now 7.04. Lots of
configurations were changed, /dev structure, root points, mount, lvm
and lots of changes were made since then.
What's annoying me to get a personalized kernel now running is the lvm
new configuration that I don't master yet (nor am willing to lately)
and that's the only thing that breaks on my ubuntu with a personalized
kernel.
The filesystem changes were quite messy, on 6.10 I lost my swap space
(kernel couldn't mount it) and I didn't have time to investigate
properly. Now, with 7.04 it's back again... I'm too old to investigate
every detail... ;)
I'm sure if I get a fresh installation, kernel.org's kernel will work
like a charm...
cheers,
--renato
Reclaim your digital rights, eliminate DRM, learn more at
http://www.defectivebydesign.org/what_is_drm
next prev parent reply other threads:[~2007-06-04 22:06 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
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 [this message]
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=d9b9d95f0706041506l257819a7pbcb8b8efc2eec049@mail.gmail.com \
--to=rengolin@gmail.com \
--cc=dmitry.torokhov@gmail.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
all inboxes | Powered by JetHome®