From: Marcel Holtmann <marcel@holtmann.org>
To: "Rybalkin, Albert" <Albert.Rybalkin@Fiserv.com>
Cc: "'bluez-devel@lists.sourceforge.net'"
<bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Recent CSR BlueCore2 firmware
Date: Mon, 05 Apr 2004 02:05:55 +0200 [thread overview]
Message-ID: <1081123555.2836.0.camel@pegasus> (raw)
In-Reply-To: <CF8C38B8FA1ED511A92400508BE37F0B0A961D19@exchange_corp.bhcsecurities.com>
Hi Albert,
> I'm sorry if it's not the right place to ask questions
> like this, but I have a generic BlueCore2-base usb
> dongle that has an old firmware v1.75. I would like to
> update it to the recent CSR firmware release. I found a windows
> CSR firmware updater, but was not able to locate any
> firmware files. CSR doesn't seem to have it available on
> their web site either. Does anyone know where should I look at?
> Or can anyone who has a CSR BlueCore2 module with recent firmware
> be so kind to save a copy of firmware with windows updater
> and email it to me to albertr iral com? Thanks.
ask the manufacturer of your dongle.
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 0:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 23:25 [Bluez-devel] Recent CSR BlueCore2 firmware Rybalkin, Albert
2004-04-05 0:05 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-05 1:26 Rybalkin, Albert
2004-04-05 7:36 ` 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=1081123555.2836.0.camel@pegasus \
--to=marcel@holtmann.org \
--cc=Albert.Rybalkin@Fiserv.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