All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Deepesh S Gujarathi <d_gujarathi@hotmail.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Re: blueZ-bthid testing
Date: Wed, 07 Jan 2004 14:11:06 +0100	[thread overview]
Message-ID: <1073481066.2508.150.camel@pegasus> (raw)
In-Reply-To: <Law11-OE46C3SpmFZfs000064c7@hotmail.com>

Hi Deepesh,

> 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) ?

yes it is, but maybe you need to have additional CorePointer options.
Look at some XFree config howto's.

> - also in the option "Device" the value specified as "/dev/input/mice" does
> it need to be /dev/input/uinput or something else ?

No. The mice device is correct.

> - does the mousedev module need to be loaded to make it work ?

Yes.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-01-07 13:11 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
2004-01-07 13:11         ` Marcel Holtmann [this message]
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=1073481066.2508.150.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=d_gujarathi@hotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.