From owner-freebsd-bluetooth@FreeBSD.ORG  Mon Jul 26 17:02:38 2004
Return-Path: <owner-freebsd-bluetooth@FreeBSD.ORG>
Delivered-To: freebsd-bluetooth@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id AFB0B16A4D0
	for <freebsd-bluetooth@freebsd.org>;
	Mon, 26 Jul 2004 17:02:38 +0000 (GMT)
Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.198])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 60CA943D69
	for <freebsd-bluetooth@freebsd.org>;
	Mon, 26 Jul 2004 17:02:38 +0000 (GMT)
	(envelope-from maksim.yevmenkin@gmail.com)
Received: by mproxy.gmail.com with SMTP id m69so82562rne
	for <freebsd-bluetooth@freebsd.org>;
	Mon, 26 Jul 2004 10:02:24 -0700 (PDT)
Received: by 10.38.12.79 with SMTP id 79mr764530rnl;
        Mon, 26 Jul 2004 09:55:44 -0700 (PDT)
Message-ID: <bb4a86c704072609552a201257@mail.gmail.com>
Date: Mon, 26 Jul 2004 09:55:44 -0700
From: Maksim Yevmenkin <maksim.yevmenkin@gmail.com>
To: Peter Grehan <grehan@freebsd.org>, freebsd-bluetooth@freebsd.org
In-Reply-To: <41053315.6090906@savvis.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <41053315.6090906@savvis.net>
Subject: Re: BCM2033 bluez 1.0 firmware ?
X-BeenThere: freebsd-bluetooth@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Using Bluetooth in FreeBSD environments
	<freebsd-bluetooth.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth>,
	<mailto:freebsd-bluetooth-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bluetooth>
List-Post: <mailto:freebsd-bluetooth@freebsd.org>
List-Help: <mailto:freebsd-bluetooth-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth>,
	<mailto:freebsd-bluetooth-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2004 17:02:38 -0000

Hi Peter,

>  I've just given Bluetooth a whirl on FreeBSD/PPC, and it seems
> to work fine.

first, let me thank you for trying this. i'm very glad it worked for you.

>  However, I couldn't get the 1.0 firmware from bluez to work.
> The 0.9 version seemed to be fine.

hmm... i'm a bit confused here. what do you mean by "1.0 firmware from
bluez"? from what i can see at

http://cvs.sourceforge.net/viewcvs.py/bluez/bluefw/firmware/

cvs: bluez/bluefw/firmware/BCM2033-FW.bin - actual firmware

Revision 1.7  - (view) (download) (as text) (annotate) - [select for diffs]
Sat Apr 26 00:33:40 2003 UTC (15 months ago) by maxk
Branch: MAIN
CVS Tags: REL-1_0, REL-1_2, HEAD
Changes since 1.6: +414 -368 lines
Diff to previous 1.6

Update BCM firmware to version 2.16.

and

cvs: bluez/bluefw/firmware/BCM2033-MD.hex - mini-driver

Revision 1.3  - (view) (download) (annotate) - [select for diffs]
Thu May 23 21:03:15 2002 UTC (2 years, 2 months ago) by maxk
Branch: MAIN
CVS Tags: REL-1_0, REL-1_2, REL-0_5, REL-0_6, REL-0_7, REL-0_8, HEAD
Changes since 1.2: +83 -83 lines
Diff to previous 1.2

Upgrade to version 2.13

both files were updated at least year ago.

> Has anyone given the 1.0 f/w a go ?

i have belkin bluetooth adapter that uses bcm2033 chip and i'm pretty
sure i tried the above mentioned files with it and everything worked
just fine.

1) could you please clarify what do you mean by "1.0 version f/w"?

2) could you please tell me exactly what adapter do you have? (i.e.
d-link, belkin other)

3) could you please point me to the "1.0 version f/w" so i can try it
with my adapter?

4) is there any particular reason you would like to use "1.0 f/w"
instead of "0.9 f/w"?

thanks,
max