From: mike <mikelee@avantwave.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] About rfcomm socket
Date: Mon, 06 Dec 2004 15:37:47 +0800 [thread overview]
Message-ID: <41B40C4B.90002@avantwave.com> (raw)
In-Reply-To: <1102043750.7350.41.camel@pegasus>
Dear Marcel
That is old version of bluez version, is it the problem ? Anyway, i
upgrade that first.
Thanks
best regard
Mike,Lee
Marcel Holtmann wrote:
>Hi Mike,
>
>
>
>>hci0: Type: UART
>> BD Address: 00:08:E0:01:49:6A ACL MTU: 192:8 SCO MTU: 64:8
>> UP RUNNING PSCAN ISCAN
>> RX bytes:231 acl:0 sco:0 events:27 errors:0
>> TX bytes:630 acl:0 sco:0 commands:27 errors:0
>> Features: 0xff 0xff 0x8b 0x78 0x18 0x18 0x00 0x80
>> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>> Link policy: RSWITCH HOLD SNIFF PARK
>> Link mode: SLAVE ACCEPT
>> Name: 'test'
>> Class: 0x000100
>> Service Classes: Unspecified
>> Device Class: Computer, Uncategorized
>> HCI Ver: 1.2 (0x2) HCI Rev: 0x490 LMP Ver: 1.2 (0x2) LMP Subver:
>>0x490
>> Manufacturer: Cambridge Silicon Radio (10)
>>
>>
>
>this one is fine, because it is a HCI 18.x firmware.
>
>
>
>>hci0: Type: USB
>> BD Address: 00:08:E0:00:00:04 ACL MTU: 192:8 SCO MTU: 64:8
>> UP RUNNING PSCAN ISCAN
>> RX bytes:4031 acl:64 sco:0 events:143 errors:0
>> TX bytes:2429 acl:66 sco:0 commands:31 errors:0
>> Features: 0xff 0xff 0x0b 0x00 0x00 0x00 0x00 0x00
>> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>> Link policy:
>> Link mode: SLAVE ACCEPT
>> Name: 'mike'
>> Class: 0x000000
>> Service Classes: Unspecified
>> Device Class: Miscellaneous,
>> HCI Ver: 1.1 (0x1) HCI Rev: 0x175 LMP Ver: 1.1 (0x1) LMP Subver:
>>0x175
>> Manufacturer: Cambridge Silicon Radio (10)
>>
>>
>
>This one is HCI 14.7 and previous HCI 16.x which is not good.
>
>
>
>>Actually, the 3rd device is a bluetooth-embedded phone, i can not get
>>the configuration out. SLAVE is accept for my target device, is it what
>>you want to see?
>>
>>
>
>You can, use "hcitool info ..." as root.
>
>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-devel mailing list
>Bluez-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
>
>
-------------------------------------------------------
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-12-06 7:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 2:25 [Bluez-devel] About rfcomm socket mike
2004-12-01 6:28 ` Marcel Holtmann
2004-12-01 8:53 ` [Bluez-users] " mike
2004-12-01 9:48 ` Marcel Holtmann
2004-12-02 4:26 ` mike
2004-12-02 7:44 ` Marcel Holtmann
2004-12-03 3:16 ` mike
2004-12-03 3:15 ` Marcel Holtmann
2004-12-06 7:37 ` mike [this message]
2004-12-06 7:38 ` Marcel Holtmann
2004-12-06 11:29 ` mike
2004-12-06 11:27 ` Marcel Holtmann
2004-12-06 13:17 ` Mike Lee
2004-12-06 13:27 ` Marcel Holtmann
2004-12-06 14:04 ` Mike Lee
2004-12-06 14:20 ` Marcel Holtmann
2004-12-06 14:47 ` Mike Lee
2004-12-06 15:41 ` Marcel Holtmann
2004-12-07 9:13 ` mike
2004-12-07 9:10 ` [Bluez-devel] " Sebastian Roth
2004-12-07 9:18 ` [Bluez-devel] " 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=41B40C4B.90002@avantwave.com \
--to=mikelee@avantwave.com \
--cc=bluez-devel@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