Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
To: Stephen Crane <steve.crane@rococosoft.com>
Cc: Super Smart <alwaysgone@seznam.cz>,
	BlueZ Mailing List <bluez-users@lists.sourceforge.net>,
	samlee@ptl.com.tw
Subject: Re: [Bluez-users] TDK Firmware Upgrade Procedure....
Date: 22 May 2003 18:54:29 +0200	[thread overview]
Message-ID: <1053622480.17764.144.camel@pegasus> (raw)
In-Reply-To: <1053622053.1771.40.camel@baroque.rococosoft.com>

Hi Stephen,

> I was unable to get this installed on our Win2k machines. hciconfig
> currently reports: 
> 
> hci0:   Type: USB
>         BD Address: 00:80:98:24:4E:8A ACL MTU: 192:8  SCO MTU: 64:8
>         UP RUNNING PSCAN ISCAN
>         RX bytes:2514 acl:37 sco:0 events:149 errors:0
>         TX bytes:1355 acl:35 sco:0 commands:53 errors:0
>         Features: 0xff 0xff 0x0d 0x00
>         Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>         Link policy: RSWITCH HOLD SNIFF PARK
>         Link mode: SLAVE ACCEPT
>         Name: 'bluez-server'
>         Class: 0x000100
>         Service Classes: Unspecified
>         Device Class: Computer, Uncategorized
>         HCI Ver: 1.1 (0x1) HCI Rev: 0x86 LMP Ver: 1.1 (0x1) LMP Subver:
> 0x86
>         Manufacturer: Cambridge Silicon Radio (10)

this is exactly what I have in my list. It is a CSR BlueCore01b chip
with HCI 12.3 firmware. If the update will bring it up to HCI 16.4 it is
the first BlueCore01b based device with limited scatternet capability
that I have seen.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2003-05-22 16:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22  8:10 [Bluez-users] TDK Firmware Upgrade Procedure Super Smart
2003-05-22 16:34 ` Marcel Holtmann
2003-05-22 16:47   ` Stephen Crane
2003-05-22 16:54     ` Marcel Holtmann [this message]
2003-05-23 14:50   ` [Bluez-users] TDK Firmware Upgrade Proc edure Super Smart
2003-05-23 14:55     ` [Bluez-users] TDK Firmware Upgrade Procedure Marcel Holtmann
2003-05-25 12:32       ` [Bluez-users] TDK Firmware Upgrade Proc edure Super Smart
2003-05-25 12:37         ` [Bluez-users] TDK Firmware Upgrade Procedure 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=1053622480.17764.144.camel@pegasus \
    --to=marcel@rvs.uni-bielefeld.de \
    --cc=alwaysgone@seznam.cz \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=samlee@ptl.com.tw \
    --cc=steve.crane@rococosoft.com \
    /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