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 17:42:20 +0200 [thread overview]
Message-ID: <1086536540.4765.35.camel@pegasus> (raw)
In-Reply-To: <200406061210.52170.cijoml@volny.cz>
Hi Michal,
> > 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 :)
I don't either. Can anyone with Mac OS X write some small words how to
extract GenericCSR.dfu from the BluetoothFWUpdate1.1.dmg file?
Btw the best way is to reverse engineer the Apple UDIF disk image format
and provide an open source tool for it.
> > 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.
You can't look at it with this naive view. The problem is much more
complex. I have contacts to many "Bluetooth companies" here in Germany,
but most of their products are build in Japan, Taiwan etc. The European
headquarters are better support and sales centers, because in most cases
they can't influence any decisions. Most companies I talked to are
willing to help, but actually they can't, because they don't have the
resources to do so.
My resources are limited, too. Only asking for firmware upgrade and
other information doesn't help. Start doing something and I mean start
writing code that allows us to work with. We still miss the DFU download
functionality and a PS Tool program for Linux.
> 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
I don't get that point, but of course you can upload the firmware from
an already updated dongle. Actually I don't think that I am going to
provide such a firmware file. Maybe someone else and then I will link,
but without written permission from Apple I don't think so.
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
next prev parent reply other threads:[~2004-06-06 15:42 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
2004-06-06 15:42 ` Marcel Holtmann [this message]
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=1086536540.4765.35.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