public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: RE: [Bluez-devel] Question about role switch
Date: Wed, 15 Dec 2004 17:20:11 +0100	[thread overview]
Message-ID: <1103127611.8717.7.camel@pegasus> (raw)
In-Reply-To: <A1F0D47583A2D711919F00600819B3A45BDE4F@goofy.vitronics.com>

Hi Richard,

> >>>>>>>>This is my X-scale embedded system
> [System 1]$hciconfig -a
> hci0:   Type: UART
>         BD Address: 00:A0:96:08:E7:86 ACL MTU: 192:8  SCO MTU: 64:8
>         UP RUNNING PSCAN ISCAN
>         RX bytes:1842 acl:20 sco:0 events:93 errors:0
>         TX bytes:1415 acl:19 sco:0 commands:41 errors:0
>         Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
>         Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>         Link policy: RSWITCH HOLD SNIFF PARK
>         Link mode: SLAVE ACCEPT
>         Name: 'BlueZ (0)'
>         Class: 0x000100
>         Service Classes: Unspecified
>         Device Class: Computer, Uncategorized
>         HCI Ver: 1.1 (0x1) HCI Rev: 0x175 LMP Ver: 1.1 (0x1) LMP Subver: 0x175
>         Manufacturer: Cambridge Silicon Radio (10)
>                                
> >>>>>>>> This is my Linux PC. 
> >>>>>>>> I have the same USB dongle in the Linux and Windows PCs
> [System 2]# /sbin/hciconfig -a
> hci0:   Type: USB
>         BD Address: 00:02:72:40:3F:C2 ACL MTU: 192:8  SCO MTU: 64:8
>         UP RUNNING PSCAN ISCAN
>         RX bytes:135 acl:0 sco:0 events:19 errors:0
>         TX bytes:569 acl:0 sco:0 commands:18 errors:0
>         Features: 0xff 0xff 0x0f 0x00
>         Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>         Link policy: HOLD SNIFF PARK
>         Link mode: SLAVE ACCEPT
>         Name: 'Linux_Rich'
>         Class: 0x700408
>         Service Classes: Object Transfer, Audio, Telephony
>         Device Class: Audio/Video, Hands-free
>         HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP Subver: 0x20d
>         Manufacturer: Cambridge Silicon Radio (10)

everything before HCI 16.4 has not even limited scatternet support.
Check you my CSR page for more details.

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

  reply	other threads:[~2004-12-15 16:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-15 14:57 [Bluez-devel] Question about role switch Williams, Richard
2004-12-15 16:20 ` Marcel Holtmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-12-15 16:49 Williams, Richard
2004-12-15 17:24 ` Marcel Holtmann
2004-12-15 14:38 Williams, Richard
2004-12-15 14:41 ` Peter Wippich

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