All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Anycom USB-240 & firmware
Date: Sat, 29 Jan 2005 02:15:49 +0100	[thread overview]
Message-ID: <1106961349.10580.7.camel@pegasus> (raw)
In-Reply-To: <cteadv$tbe$1@sea.gmane.org>

Hi Jesse,

> I recently bought an Anycom USB-240. It ships
> with BT 1.1 firmware, as depicted below, but
> it *should* be BT 1.2 capable hardware.
> 
> % hciconfig -a
> hci0:   Type: USB
>         BD Address: 00:0B:0D:34:1F:E0 ACL MTU: 120:20  SCO MTU: 64:0
>         UP RUNNING PSCAN ISCAN
>         RX bytes:254 acl:0 sco:0 events:43 errors:0
>         TX bytes:416 acl:0 sco:0 commands:30 errors:0
>         Features: 0xff 0xff 0x05 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: 0x100100
>         Service Classes: Object Transfer
>         Device Class: Computer, Uncategorized
>         HCI Ver: 1.1 (0x1) HCI Rev: 0x0 LMP Ver: 1.1 (0x1) LMP Subver: 0x757
>         Manufacturer: Silicon Wave (11)
> 
> My interest in Bluetooth is primarily tied to
> audio right now. I've been doing a lot of work
> with SIP phones lately so I've ordered a BT 1.2
> Logitech Mobile Freedom Headset to play with.
> It should arrive in a week or two.
> 
> Anyway, the Logitech headset is BT 1.2 capable
> so I'd like to upgrade my USB-240 firmware to
> 1.2 also (freq hopping to avoid my 802.11b nets,
> etc...), but this post on the Anycom website
> claims that the USB-240's headset and handsfree
> profiles don't work well under Linux with BT
> 1.2 firmware:
>     http://tinyurl.com/5pqnm
> 
> So in the interest of NOT frying my shiny new
> USB-240, does anyone on this list currently use
> a USB-240 with a headset or handsfree profile
> device? Which firmware do you use?

if you wanna play with audio then you should better buy a dongle with a
CSR chip.

> Also, if I *do* decide to upgrade the adapter's
> firmware, am I likely to have better luck with
> Anycom's firmware via a Win32 install? Or with
> Bluez supplied firmware? Does the Bluez firmware
> even work with my Silicon Wave chipset?

As far as I know these Silicon Wave chips are ROM only version and so
you can't update the firmware. However I don't even know of any firmware
updates for Silicon Wave.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-01-29  1:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-28 21:22 [Bluez-users] Anycom USB-240 & firmware Jesse Guardiani
2005-01-29  1:15 ` Marcel Holtmann [this message]
2005-01-29 11:14   ` Michal Semler
2005-01-29 13:58     ` Marcel Holtmann
2005-01-29 14:41       ` Michal Semler
2005-02-01 20:10   ` [Bluez-users] " Jesse Guardiani
2005-02-02  3:44     ` Jesse Guardiani

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=1106961349.10580.7.camel@pegasus \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.