Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
To: Super Smart <alwaysgone@seznam.cz>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>,
	steve.crane@rococosoft.com, samlee@ptl.com.tw
Subject: Re: [Bluez-users] TDK Firmware Upgrade Procedure....
Date: 23 May 2003 16:55:56 +0200	[thread overview]
Message-ID: <1053701766.10300.26.camel@pegasus> (raw)
In-Reply-To: <64468.207869-20715-230692224-1053701433@seznam.cz>

Hi,

> TDK comes with Widcomm software
> (http://www.tdksys.com/support/drivers/range.asp?id=1) -- However, we
> just use it to update the firmware -- we use your BlueZ on Linux and
> AveLink's Demo for Windoz.  Works fine now.
> 
> After upgrade, we have HCI 16.4

can you send me the output of "hciconfig -a".

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-23 14:55 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
2003-05-23 14:50   ` [Bluez-users] TDK Firmware Upgrade Proc edure Super Smart
2003-05-23 14:55     ` Marcel Holtmann [this message]
2003-05-25 12:32       ` 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=1053701766.10300.26.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