From: Marcel Holtmann <marcel@holtmann.org>
To: Lars Grunewaldt <lgw@dark-reality.de>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] another problem with hidd/MX900 mouse
Date: Sun, 08 Aug 2004 12:16:09 +0200 [thread overview]
Message-ID: <1091960169.2773.14.camel@pegasus> (raw)
In-Reply-To: <4115F36B.8090202@dark-reality.de>
Hi Lars,
> the MX900 works flawless now with both an Epox BTD on my notebook and
> the docking station from Logitech on my desktop PC. Great work, thanks a
> lot :)
>
> But there is one issue not directly connected to the mouse, and I hope
> you can help me out here.
>
> hidd (I think) registers the mouse after connection as /dev/mouse2, and
> X11 uses it without any issues - as long as the mouse is connected
> *before* the X11-Server is started. Without a connected mouse, there's
> no /dev/mouse2, and I don't know how to tell the X11 server "hey look
> again the pointing device appeared".
>
> Another option might be some kind of "mirror" for the device, i.e. with gpm.
>
> Any ideas how to make the mouse working without restarting X11 (and all
> running programs...)
use only /dev/input/mice for your mouse device.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-08-08 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-08 9:33 [Bluez-devel] another problem with hidd/MX900 mouse Lars Grunewaldt
2004-08-08 10:16 ` Marcel Holtmann [this message]
2004-08-08 11:57 ` Lars Grunewaldt
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=1091960169.2773.14.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=lgw@dark-reality.de \
/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