public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] tryig to get bluetooth keyboad to work
Date: Mon, 26 Feb 2007 10:36:54 +0100	[thread overview]
Message-ID: <1172482614.27370.11.camel@violet> (raw)
In-Reply-To: <752642.79554.qm@web31711.mail.mud.yahoo.com>

Hi Tim,

> Thanks for the response.
> 
> Heres my hciconfig right after it locks up.
> 
> > HCI Event: Number of Completed Packets (0x13) plen 5
>     handle 2 packets 1
> > ACL data: handle 2 flags 0x02 dlen 18
>     L2CAP(s): Config rsp: scid 0x0041 flags 0x00
> result 0 clen 4
>       Success
>       MTU 48 
> > HCI Event: QoS Setup Complete (0x0d) plen 21
>     status 0x00 handle 2 flags 0
>     Service type: 1
>     Token rate: 0
>     Peak bandwith: 0
>     Latency: 11250
>     Delay variation: -1
> < ACL data: handle 2 flags 0x02 dlen 14
>     L2CAP(d): cid 0x0041 len 10 [psm 19]
>       HIDP: Data: Output report
>       0000: 01 00 00 00 00 00 00 00  00               
>        .........
> < ACL data: handle 2 flags 0x02 dlen 7
>     L2CAP(d): cid 0x0041 len 3 [psm 19]
>       HIDP: Data: Output report
>       0000: 02 00                                     
>        ..
> < ACL data: handle 2 flags 0x02 dlen 14
>     L2CAP(d): cid 0x0041 len 10 [psm 19]
>       HIDP: Data: Output report
>       0000: 05 00 00 00 00 00 00 00  00               
>        .........
> < ACL data: handle 2 flags 0x02 dlen 8
>     L2CAP(d): cid 0x0041 len 4 [psm 19]
>       HIDP: Data: Output report
>       0000: 06 00 00                                  
>        ...
> < ACL data: handle 2 flags 0x02 dlen 14
>     L2CAP(d): cid 0x0041 len 10 [psm 19]
>       HIDP: Data: Output report
>       0000: 05 00 00 00 00 00 00 00  00               
>        .........
> > ACL data: handle 2 flags 0x02 dlen 14
>     L2CAP(d): cid 0x0041 len 10 [psm 19]
>       HIDP: Data: Input report
>       0000: 05 44 7c 72 d3 c9 03 00  00               
>        .D|r.....

you might wanna try a 2.6.20-mh1 kernel. That has full report mode
support and might make it work without issues.

Regards

Marcel



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2007-02-26  9:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-25  7:26 [Bluez-users] tryig to get bluetooth keyboad to work tim culwins
2007-02-25 23:50 ` Marcel Holtmann
2007-02-26  2:57   ` tim culwins
2007-02-26  9:36     ` Marcel Holtmann [this message]

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=1172482614.27370.11.camel@violet \
    --to=marcel@holtmann.org \
    --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