From: Marcel Holtmann <marcel@holtmann.org>
To: Sunnan <sunnan@handgranat.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] apple wireless mouse on apple ibook (g4, builtin usb)
Date: Mon, 16 Feb 2004 00:59:38 +0100 [thread overview]
Message-ID: <1076889578.2840.36.camel@pegasus> (raw)
In-Reply-To: <40300408.4070604@handgranat.org>
Hi Sunnan,
> I still haven't gotten my mouse to work (I know! sorry).
> One of the herrings I'm chasing is the name, is the problem the weird
> characters in the devices name? if so, can it be renamed?
this must be some Apple specific option. I like to know how it can be
done, but it has nothing to do with your device working or not.
> I've been able to find it more often with hcitool by clicking/moving it
> while hcitool is searching.
>
> Still no success with bthid, it has never given me anything else than
>
> Feb 15 23:30:04 slowstorm bthid[1035]: Bluetooth HID service started
> Feb 15 23:30:30 slowstorm bthid[1035]: Connection failed: Host is down (112)
>
> when I try to connect to my mouse with sudo bthid -c 00:0A:95:01:5F:57
>
> and bthid loves to just exit all the time.
I think this is an endian problem. From the last dump you send me I saw
< ACL data: handle 0x002d flags 0x02 dlen 24
L2CAP(d): cid 0x42 len 20 [psm 1]
SDP SSA Req: tid 0x1 len 0xf
pat uuid-16 0x0012
max 0xffff
aid(s) 0xffff - 0x0000
cont 00
> ACL data: handle 0x002d flags 0x02 dlen 15
L2CAP(d): cid 0x42 len 11 [psm 1]
SDP SSA Rsp: tid 0x1 len 0x6
cnt 0x3 len 0x3 frm->len 0x1 n 0x0
cont 00
The UUID of the HID service and the attribute id's of the request are
wrong. If it can't find the SDP record for the HID service, it can't
setup the HID descriptor and make your mouse working, but I don't know
why the bthid process exits.
Regards
Marcel
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-02-15 23:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 17:22 [Bluez-users] apple wireless mouse on apple ibook (g4, builtin usb) Sunnan
2004-02-13 17:51 ` Marcel Holtmann
2004-02-13 18:59 ` Sunnan
2004-02-13 19:56 ` Marcel Holtmann
2004-02-13 20:48 ` Sunnan
2004-02-13 21:50 ` Marcel Holtmann
2004-02-13 22:02 ` Sunnan
2004-02-13 22:29 ` Marcel Holtmann
2004-02-13 22:54 ` Sunnan
2004-02-13 23:21 ` Marcel Holtmann
[not found] ` <402D5EB0.3090601@handgranat.org>
2004-02-14 0:54 ` Marcel Holtmann
2004-02-14 11:06 ` Sunnan
2004-02-15 23:43 ` Sunnan
2004-02-15 23:59 ` Marcel Holtmann [this message]
2004-02-13 22:59 ` one more thing (was Re: [Bluez-users] apple wireless mouse on apple ibook (g4, builtin usb)) Sunnan
2004-02-13 23:22 ` Marcel Holtmann
2004-02-13 22:13 ` [Bluez-users] apple wireless mouse on apple ibook (g4, builtin usb) Ramon A Reveron
2004-02-13 22:15 ` 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=1076889578.2840.36.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=sunnan@handgranat.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