public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: cijoml@volny.cz
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Bluetooth 1.2 and HID Proxy
Date: Sun, 06 Jun 2004 00:53:34 +0200	[thread overview]
Message-ID: <1086476014.16316.129.camel@pegasus> (raw)
In-Reply-To: <200406052338.15162.cijoml@volny.cz>

Hi Michal,

> pls start new webpage on bluez which will collect all known doglech which we 
> know reflash with newer firmware and pls try describe step-by-step howto.

currently I am preparing a site with notes about firmware upgrade and
DFU. I will also summarize the public statements of the CSR signature
and so on. However don't expect a howto for getting firmware from one
device into another. I am not concerned in upgrading of any dongle,
because today an USB Bluetooth dongle is so cheap that you can buy
yourself a new one if the firmware is too old. I paid 14 EUR for my
D-Link dongle at eBay. The problem what I see is that the dongle
manufacturers are too lazy to get out the Bluetooth 1.2 capable dongles.
For the CSR based BlueCore02 based dongles they only have to change
their firmware and can sell it as a complete new product. If they
started with a 8 Mbit flash from the beginning they don't even have to
change their design.

The other point is the HID Proxy support. Actually people are asking me
where they can buy such dongles. I can't tell them, because I don't
know. And again, every BlueCore02 with 8 Mbit flash can use HID Proxy.
So where is the problem? I think Apple is doing this the right way. They
really support their hardware. The question is why D-Link can't provide
an update for the dongle ;)

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-06-05 22:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-05 10:03 [Bluez-users] Bluetooth 1.2 and HID Proxy Marcel Holtmann
2004-06-05 10:27 ` Michal Semler
2004-06-05 10:55   ` Marcel Holtmann
2004-06-05 21:38 ` Michal Semler
2004-06-05 22:53   ` Marcel Holtmann [this message]
2004-06-06 10:10     ` Michal Semler
2004-06-06 15:42       ` Marcel Holtmann
2004-06-09 14:24 ` Edd Dumbill

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=1086476014.16316.129.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=cijoml@volny.cz \
    /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