From: Charles Bueche <charles@bueche.ch>
To: Edd Dumbill <edd@usefulinc.com>
Cc: Peter Klausler <peter@klausler.com>,
BlueZ Developers List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Logitech MX900 mouse with Dell Inspiron 8600
Date: Wed, 03 Dec 2003 21:18:03 +0100 [thread overview]
Message-ID: <1070482683.18058.6.camel@bluez.bueche.ch> (raw)
In-Reply-To: <1070380907.19169.55.camel@saag>
Hi,
[first, thanks a lot for helping me. I plan a mini-HOWTO ln a web page
when I'm done so other can get the same setup working.]
I tried your patch on my linux-2.6.0-test11-gentoo Dell I8600 with my
Logitech MX900 mouse. It applies OK, but (don't know if it's gentoo
specific), my uinput is at /dev/misc/uinput, not /dev/input/uinput. So I
had to fix the path in out.c.
After this, I get the mouse events in X. The movements are OK, but the
button 1 is not doing its job. If I cat < /dev/input/mice, I see
something happen when I click it, so it's obviously not the button
hardware.
I have compiled my X with a patch to enable the PS/2++ protocol. The
patch is from Eric Wong, can be downloaded here :
http://www.yhbt.net/normalperson/files/linux/LogitechMX_kernel_and_X_patch/4.3.0-XFree86_logitech_ps2.patch
could this patch be the reason for my button 1 problem ?
Hints welcome.
Charles
On Tue, 2003-12-02 at 17:01, Edd Dumbill wrote:
> On Tue, 2003-12-02 at 15:55, Edd Dumbill wrote:
> > Hmm, I'd thought I'd sent this to the list, but obviously didn't.
> > Here's a patch for Peter's bthid stuff to work with the uinput driver in
> > Linux 2.6. Use at your own risk. I had it going OK with an Apple
> > keyboard and MS mouse.
>
> And if I'd attached the patch first time, it would have been truly
> impressive.
>
> Here we are.
>
> -- Edd
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2003-12-03 20:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-30 14:12 [Bluez-devel] Logitech MX900 mouse with Dell Inspiron 8600 Charles Bueche
2003-11-30 18:51 ` Charles Bueche
2003-12-01 15:38 ` Peter Klausler
2003-12-02 15:55 ` Edd Dumbill
2003-12-02 16:01 ` Edd Dumbill
2003-12-03 20:18 ` Charles Bueche [this message]
2003-12-03 20:35 ` Marcel Holtmann
2003-12-04 8:53 ` Olivier Bornet
2003-12-04 13:52 ` Marcel Holtmann
2003-12-04 13:57 ` Olivier Bornet
2003-12-04 14:10 ` Marcel Holtmann
2003-12-04 16:35 ` Olivier Bornet
2003-12-04 17:03 ` Marcel Holtmann
2003-12-09 20:31 ` Charles Bueche
2003-12-09 22:42 ` Olivier Bornet
2003-12-10 8:12 ` Charles Bueche
2003-12-10 8:30 ` Olivier Bornet
2003-12-13 15:56 ` Charles Bueche
2003-12-13 16:39 ` Marcel Holtmann
2003-12-13 18:51 ` Charles Bueche
2003-12-13 19:04 ` Marcel Holtmann
2003-12-14 13:55 ` Charles Bueche
2003-12-14 14:22 ` Marcel Holtmann
2003-12-14 20:01 ` Charles Bueche
2003-12-14 20:09 ` Marcel Holtmann
2003-12-10 1:41 ` Marcel Holtmann
2003-12-02 17:39 ` Marcel Holtmann
2003-12-02 17:42 ` Peter Klausler
2003-12-02 17:56 ` Marcel Holtmann
2003-12-03 10:10 ` Stephen Crane
2003-12-03 13:06 ` Marcel Holtmann
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=1070482683.18058.6.camel@bluez.bueche.ch \
--to=charles@bueche.ch \
--cc=bluez-devel@lists.sourceforge.net \
--cc=edd@usefulinc.com \
--cc=peter@klausler.com \
/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