From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] setup pairing?
Date: Wed, 26 Jan 2005 07:07:54 +0100 [thread overview]
Message-ID: <1106719674.28444.1.camel@pegasus> (raw)
In-Reply-To: <41F71444.4080404@coriand.com>
Hi Franz,
> thanks for your response!
>
> #./hciconfig -a
> hci0: Type: UART
> BD Address: 00:60:57:01:10:AE ACL MTU: 384:80 SCO MTU: 128:80
> UP RUNNING PSCAN ISCAN
> RX bytes:172 acl:0 sco:0 events:17 errors:0
> TX bytes:80 acl:0 sco:0 commands:17 errors:0
> Features: 0xff 0xff 0x09 0x00
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy:
> Link mode: SLAVE ACCEPT
> Name: 'WatchPad_15'
> Class: 0x000000
> Service Classes: Unspecified
> Device Class: Miscellaneous,
> HCI Ver: 1.1 (0x1) HCI Rev: 0xbc LMP Ver: 1.1 (0x1) LMP Subver: 0xbc
> Manufacturer: Cambridge Silicon Radio (10)
> #
>
> Problem is now, that I don't have ./hcidump cause of memory problems on
> this watch.
I assume that this is a problem with the PIN-helper. Check your logfiles
and install hcidump. You really need it to debug this stuff.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-01-26 6:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 4:20 [Bluez-users] setup pairing? Franz Coriand
2005-01-25 13:37 ` Marcel Holtmann
2005-01-26 3:53 ` Franz Coriand
2005-01-26 6:07 ` 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=1106719674.28444.1.camel@pegasus \
--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 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.