Return-path: Received: from mail.3eti.com ([65.220.88.139]:32820 "EHLO 3eSpam.3eti.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751041Ab1CKRVI convert rfc822-to-8bit (ORCPT ); Fri, 11 Mar 2011 12:21:08 -0500 From: Chaoxing Lin To: 'Rafa? Mi?ecki' CC: "Chen, Xianwen" , "linux-wireless@vger.kernel.org" , Larry Finger , Brett Rudley Subject: RE: Status of Broadcom 4353? Date: Fri, 11 Mar 2011 17:21:04 +0000 Message-ID: References: <7A94256FD72B884D9E7C55586C3CBCEE15B0286A4E@SJEXCHCCR01.corp.ad.broadcom.com> <4D798863.2060303@lwfinger.net> <4D7A3EAD.10306@lwfinger.net> In-Reply-To: Content-Type: text/plain; charset="iso-8859-2" MIME-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: Well, just throw some ideas. Not mean to mess. Older Broadcom driver did put firmware in /lib/firmware/ e.g. BCM2033-FW.bin -----Original Message----- From: Rafa? Mi?ecki [mailto:zajec5@gmail.com] Sent: Friday, March 11, 2011 12:02 PM To: Chaoxing Lin Cc: Chen, Xianwen; linux-wireless@vger.kernel.org; Larry Finger; Brett Rudley Subject: Re: Status of Broadcom 4353? W dniu 11 marca 2011 17:58 u?ytkownik Chaoxing Lin napisa?: > Try to put firmware in > /lib/firmware/ instead of /lib/firmware/brcm/ which is the located in the git tree, but NOT necessarily the location the driver is looking for. It is. Please, don't mess. -- Rafa?