From: Marcel Holtmann <marcel@holtmann.org>
To: "Rybalkin, Albert" <Albert.Rybalkin@Fiserv.com>
Cc: "'albertr@iral.com'" <albertr@iral.com>,
"'bluez-devel@lists.sourceforge.net'"
<bluez-devel@lists.sourceforge.net>
Subject: RE: [Bluez-devel] Recent CSR BlueCore2 firmware
Date: Mon, 05 Apr 2004 09:36:32 +0200 [thread overview]
Message-ID: <1081150592.2835.3.camel@pegasus> (raw)
In-Reply-To: <CF8C38B8FA1ED511A92400508BE37F0B0A961D1A@exchange_corp.bhcsecurities.com>
Hi Albert,
> Already tried it. Of course, they don't have any firmware
> updates. In fact, they seem to use a generic bluecore2
> firmware in their usb dongle, since it has generic CSR
> vendor/product ids.
even if it is has a CSR chip in it does not mean it will accept every
firmware. Your firmware must be signed with the right key otherwise the
bootloader won't boot it.
> It's probably a moot point, but just wondering why CSR
> seems to be so restrictive about letting people update
> firmware in their products? For instance, later releases
> supposed to confirm to 1.2 specs, why not allowing free
> access to it?
Take a look at the mailing list archive. There is a detailed description
why they did it this way.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-04-05 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 1:26 [Bluez-devel] Recent CSR BlueCore2 firmware Rybalkin, Albert
2004-04-05 7:36 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-04 23:25 Rybalkin, Albert
2004-04-05 0:05 ` 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=1081150592.2835.3.camel@pegasus \
--to=marcel@holtmann.org \
--cc=Albert.Rybalkin@Fiserv.com \
--cc=albertr@iral.com \
--cc=bluez-devel@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