Return-path: Received: from mail-qy0-f174.google.com ([209.85.216.174]:39692 "EHLO mail-qy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751041Ab1CKR1k convert rfc822-to-8bit (ORCPT ); Fri, 11 Mar 2011 12:27:40 -0500 Received: by qyk7 with SMTP id 7so6086758qyk.19 for ; Fri, 11 Mar 2011 09:27:39 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <7A94256FD72B884D9E7C55586C3CBCEE15B0286A4E@SJEXCHCCR01.corp.ad.broadcom.com> <4D798863.2060303@lwfinger.net> <4D7A3EAD.10306@lwfinger.net> Date: Fri, 11 Mar 2011 18:27:38 +0100 Message-ID: Subject: Re: Status of Broadcom 4353? From: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= To: Chaoxing Lin Cc: "Chen, Xianwen" , "linux-wireless@vger.kernel.org" , Larry Finger , Brett Rudley Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: W dniu 11 marca 2011 18:21 użytkownik Chaoxing Lin napisał: > Well, just throw some ideas. Not mean to mess. > Older Broadcom driver did put firmware in /lib/firmware/ e.g. BCM2033-FW.bin I had no idea about that, sorry. Newest driver looks in brcm subdir, I'm sure of that. -- Rafał