From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] hcitool scan ...
Date: Tue, 30 Nov 2004 14:30:36 +0100 [thread overview]
Message-ID: <1101821436.9348.1.camel@notepaq> (raw)
In-Reply-To: <200411301420.24512.wim.delvaux@adaptiveplanet.com>
Hi Wim,
> > > > this depends on the Bluetooth chip and its firmware. Check this with
> > > > hcitool and hciconfig.
> > >
> > > sorry for my BT ignorance but what option should I use and which
> > > parameter presents Chip and Firmware ?
> >
> > hciconfig -a
> > hciconfig hci0 revision
> > hcitool info <bdaddr>
>
> for the Ipaq it shows
> /mnt/ramfs/tmp # hciconfig -a
> hci0: Type: UART
> BD Address: 00:02:C7:0D:85:96 ACL MTU: 128:8 SCO MTU: 64:8
> UP RUNNING PSCAN ISCAN AUTH
> RX bytes:252 acl:0 sco:0 events:12 errors:0
> TX bytes:430 acl:0 sco:0 commands:11 errors:0
> Features: 0xff 0xff 0x05 0x00
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy: HOLD SNIFF PARK
> Link mode: SLAVE ACCEPT
> Name: 'familiar'
> Class: 0x120112
> Service Classes: Networking, Object Transfer
> Device Class: Computer, Handheld
> HCI Ver: 1.1 (0x1) HCI Rev: 0x72 LMP Ver: 1.1 (0x1) LMP Subver: 0x72
> Manufacturer: Cambridge Silicon Radio (10)
>
> /mnt/ramfs/tmp # hciconfig hci0 revision
> hci0: Type: UART
> BD Address: 00:02:C7:0D:85:96 ACL MTU: 128:8 SCO MTU: 64:8
> HCI 11.2 (bc01b)
>
> for the desktop is shows
> buro:# hciconfig -a
> hci0: Type: USB
> BD Address: 00:60:57:02:71:A2 ACL MTU: 192:8 SCO MTU: 64:8
> UP RUNNING PSCAN ISCAN
> RX bytes:4470825 acl:40078 sco:0 events:110377 errors:0
> TX bytes:14530648 acl:125164 sco:0 commands:1112 errors:0
> Features: 0xff 0xff 0x09 0x00 0x00 0x00 0x00 0x00
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy:
> Link mode: SLAVE ACCEPT
> Name: 'buro-0'
> 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)
>
> buro:# hciconfig hci0 revision
> hci0: Type: USB
> BD Address: 00:60:57:02:71:A2 ACL MTU: 192:8 SCO MTU: 64:8
> HCI 12.7
> Chip version: BlueCore01b
> SCO mapping: PCM
>
> does that explain why hciconfig scan fails if they are connected ?
actually you won't be happy with anything before HCI 16.4 firmware.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-11-30 13:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 9:50 [Bluez-users] hcitool scan wim delvaux
2004-11-29 10:13 ` Marcel Holtmann
2004-11-29 10:16 ` wim delvaux
2004-11-29 10:32 ` Marcel Holtmann
2004-11-29 10:36 ` wim delvaux
2004-11-29 10:39 ` Marcel Holtmann
2004-11-30 13:20 ` wim delvaux
2004-11-30 13:30 ` 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=1101821436.9348.1.camel@notepaq \
--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