From: Michal Semler <cijoml@volny.cz>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Bluetooth 1.2 and HID Proxy
Date: Sun, 6 Jun 2004 12:10:51 +0200 [thread overview]
Message-ID: <200406061210.52170.cijoml@volny.cz> (raw)
In-Reply-To: <1086476014.16316.129.camel@pegasus>
On Sunday 06 of June 2004 00:53, Marcel Holtmann wrote:
> 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
Site is nice, but you should provide screenshoots of steps how to use MacOS to
extract that firmware. Many people (including me) don't know how to work with
MacOS :)
> 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.
This is bad way. We as customers should make a preasure to vendors to allow us
upgrade our devices for free! I better spend my 14 euros in cinema with my
girl :) When device allow me to upgrade it's functionality, vendors should
allow us to do it. And if not, other vendors will support us and then we
should make preasure to vendors via market to allow us upgrading our devices.
And those how will block us to do it, we should turn them bankrupt via market.
> 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 ;)
To firmware licencing. I think you can share your extracted firmware, because
of this:
Re: [Bluez-users] CSR firmware
From:
Carl Orsborn <cjo@csr.com>
To:
cijoml@volny.cz
Date:
30.5.2004 09:58
SNIP
>This is great on Intersil. They allow users to upgrade their firmwares in
>their wifi cards.
>
We also allow it, but we have provided the means to prevent it.
Carl
SNIP
>
> Regards
>
> Marcel
Michal
>
>
>
>
> -------------------------------------------------------
> 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
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-06-06 10:10 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
2004-06-06 10:10 ` Michal Semler [this message]
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=200406061210.52170.cijoml@volny.cz \
--to=cijoml@volny.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox