From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <447ADD92.4050108@killesreiter.de> Date: Mon, 29 May 2006 13:40:02 +0200 From: Gerhard Killesreiter MIME-Version: 1.0 To: BlueZ development References: <4461A33F.1060702@killesreiter.de> <44634846.3000006@xmission.com> <4461FE7D.3050108@killesreiter.de> <447105B1.3060908@killesreiter.de> <447140B7.2090100@xmission.com> <44718942.10609@killesreiter.de> <4471DE09.5050405@xmission.com> <4475D2DC.304@killesreiter.de> <447A9960.7020104@xmission.com> In-Reply-To: <447A9960.7020104@xmission.com> Subject: Re: [Bluez-devel] broadcom in disguise... Reply-To: BlueZ development List-Id: BlueZ development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: bluez-devel-bounces@lists.sourceforge.net Errors-To: bluez-devel-bounces@lists.sourceforge.net Brad Midgley wrote: Hi Brad! >> They claim that the chip can be addressed by the broadcom driver but >> would definitly be a CSR chip. >> >> Does that make any sense to anybody? >> > > no sense whatsoever. > > Yeah, this is what I thought too. I've replied to them, copying the lsusb info and they confirmed that they don't use the CSR-Chip anymore and will change the info on their internet page, typhoon.de. So I can only hope the vendor takes the thing back. Cheers, Gerhard _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel