From: "Deepesh S Gujarathi" <d_gujarathi@hotmail.com>
To: "Marcel Holtmann" <marcel@holtmann.org>
Cc: "BlueZ Mailing List" <bluez-devel@lists.sourceforge.net>
Subject: Re: blueZ-bthid testing
Date: Wed, 7 Jan 2004 18:26:39 +0530 [thread overview]
Message-ID: <Law11-OE46C3SpmFZfs000064c7@hotmail.com> (raw)
In-Reply-To: 1073394980.2508.59.camel@pegasus
Hi Marcel,
I created the uinput node with the following command
# mknod /dev/input/uinput c 10 223
and the bthid error (bthid[2040]: can't open input device: no such file or
directory (2)) is gone, but for some reason I still cant move the cursor.
- I checked the hcidump and it shows all the data coming from the MS
wireless mouse as I move the mouse and click
- the tail -f /var/log/messages shows the following
Bluetooth HID service started
Connected: Microsoft Five Button Mouse
Vendor HID usage 0xff00fe01 value 0x1
adequate battery
- when I do an lsmod I see
Module Used by Not tainted
uinput 1
hci_usb 1
l2cap 5
bluez 4 [hci_usb l2cap]
input 0 (autoclean) [uinput]
I doubt the following, if anyone can verify it would be great
- my XF86Config-4 file consists
Section "InputDevice"
Identifier "MSmouse"
driver "mouse"
option "Protocol" "IMPS/2"
option "Device" "/dev/input/mice"
option "ZAxisMapping" "4 5"
option "Buttons" "5"
option "Emulate3Buttons" "false"
EndSection
now is the protocol IMPS/2 correct for a MS Intelliexplorer mouse (I copied
it from the Logitech example) ?
- also in the option "Device" the value specified as "/dev/input/mice" does
it need to be /dev/input/uinput or something else ?
- does the mousedev module need to be loaded to make it work ?
I am determined to get this MS mouse working....;)
thanks for your patience
Deepesh
Deepesh S Gujarathi
Encodex Technologies (India) Pvt. Ltd.
69 Amchi Colony, Bavdhan Khurd
Pune - 411021
91-20-2953590 , 2953591
URL: www.encodexindia.com
----- Original Message -----
From: "Marcel Holtmann" <marcel@holtmann.org>
To: "Deepesh S Gujarathi" <d_gujarathi@hotmail.com>
Cc: "BlueZ Mailing List" <bluez-devel@lists.sourceforge.net>
Sent: Tuesday, January 06, 2004 6:46 PM
Subject: Re: blueZ-bthid testing
> Hi Deepesh,
>
> > I tried to create the device node using the following commands but I
still
> > get the same error ( > bthid[2040]: can't open input device: no such
file or
> > directory (2)) .
> > I created a device node using the command
> > # mknod /dev/misc/uinput c 10 101
> > I hope I an not feeding the wrong MAJOR device number.
>
> yes you do. According to Documentation/devices.txt it is "c 10 223". And
> of course the kernel module "uinput" must be loaded.
>
> Regards
>
> Marcel
>
>
>
next prev parent reply other threads:[~2004-01-07 12:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <LAW11-OE33GHeqXipAS00015cf1@hotmail.com>
2004-01-05 14:54 ` [Bluez-devel] Re: blueZ-bthid testing Marcel Holtmann
2004-01-06 13:03 ` Deepesh S Gujarathi
2004-01-06 13:16 ` [Bluez-devel] " Marcel Holtmann
2004-01-07 12:56 ` Deepesh S Gujarathi [this message]
2004-01-07 13:11 ` Marcel Holtmann
2004-01-08 11:09 ` Deepesh S Gujarathi
2004-01-08 12:07 ` [Bluez-devel] " Charles Bueche
2004-01-10 9:09 ` [Bluez-devel] " Deepesh S Gujarathi
2004-01-10 13:32 ` 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=Law11-OE46C3SpmFZfs000064c7@hotmail.com \
--to=d_gujarathi@hotmail.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.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