linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Ghisoli <alexandre.ghisoli@ycom.ch>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] udev rules entry for bluetooth mouse
Date: Thu, 09 Feb 2006 13:50:30 +0100	[thread overview]
Message-ID: <1139489430.7543.7.camel@pc-05.ycom.ch> (raw)
In-Reply-To: <1139411355.8712.24.camel@bluez.bueche.ch>

Le mercredi 08 f=C3=A9vrier 2006 =C3=A0 16:09 +0100, Charles Bueche a =C3=
=A9crit :

> Hi all,
>=20
> thanks for the analysis and explanations. From what I have read and
> tested, here is a resum=C3=A9 of the Logitech V270 situation :
>=20
> - Logitech ignore Linux (this is not new, but need to be repeated)
> - the V270 mouse basically works as expected HID input device, but is
> overly sensible (probably due to its high resolution)
> - the mouse events go into /dev/input/mice by default
> - if evdev is loaded, mouse events go to /dev/input/event{1..N}
> - udev doesn't have the info to create a rule in 10-local.rules so the
> V270 get mapped to a fix name like /dev/input/v270
> - none of the tools I tried (locomo, logitech-applet) know the V270 for
> now. I tried to change some of them, but failed, due to lacking know-ho=
w
> in HID/USB/etc
> - KDE control center or xset cannot reduce the mouse sensibility enough
> to make it usuable (at least for my 40 years muscles control ability)


Thanks for this good resum=C3=A9, you point out the major current issue.

I just can add about udev-rules, Marcel and UDEV team are searching for
a better solution to add more infos on the udev struct, to let user
creates good rules with devices.

We can expect a workaround not so far :)

And about Linux support on Logitech product, I've several friends
working for this compagny, and with some insiders informations, I can
tell that Logitech try  now to make better software. They are aware of
the poor quality of their driver / software.
Just hope they can spend some time to change their devs :)





-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2006-02-09 12:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-02  9:33 [Bluez-users] udev rules entry for bluetooth mouse Charles Bueche
2006-02-02 10:38 ` Alexandre Ghisoli
2006-02-02 11:45   ` Charles Bueche
2006-02-07  9:15     ` Alexandre Ghisoli
2006-02-07 16:55     ` Alexandre Ghisoli
2006-02-07 22:24       ` Marcel Holtmann
2006-02-08 15:09         ` Charles Bueche
2006-02-09 12:50           ` Alexandre Ghisoli [this message]
2006-03-27 12:09           ` Charles Bueche

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=1139489430.7543.7.camel@pc-05.ycom.ch \
    --to=alexandre.ghisoli@ycom.ch \
    --cc=bluez-users@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).