Date: Tue, 20 May 2008 09:50:44 -0700 From: "Maksim Yevmenkin" <maksim.yevmenkin@gmail.com> To: "Leonardo Santagostini" <lsantagostini@gmail.com> Cc: freebsd-bluetooth@freebsd.org Subject: Re: Problem with a BCM2035B dongle Message-ID: <bb4a86c70805200950h76185ab3hd403918ed95733b1@mail.gmail.com> In-Reply-To: <9ab7eeeb0805191848p11e3b6d4u9bdd423e4e7d2533@mail.gmail.com> References: <9ab7eeeb0805190319u30ccbeefq1511afa063bd75fe@mail.gmail.com> <bb4a86c70805191032l283cab0dpb44546260855e597@mail.gmail.com> <9ab7eeeb0805191848p11e3b6d4u9bdd423e4e7d2533@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/19/08, Leonardo Santagostini <lsantagostini@gmail.com> wrote: > Sorry, but, by the way. > In the manufacturer page says: > > The BCM2035 is based on the production and UnPlugFest proven architecture of > the BCM2033 Bluetooth baseband core (BBC), peripheral transport unit (PTU) it really does not mean anything. its just marking buzz words, imo. "architecture" is too much generic word. all it probably means is that the 2035 chip has the same functional blocks as 2033 chip, i.e. cpu, memory, flash, radio etc. > Do you think we can make something ? did your 2035 dongle come with driver cd (for windows)? can you find any .bin or .hex files on the driver cd? what would really be helpful is a usb snoop trace (from windows) that shows how windows initializes this device. thanks, max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bb4a86c70805200950h76185ab3hd403918ed95733b1>