From owner-freebsd-current@FreeBSD.ORG Wed Apr 3 17:52:48 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 42466406 for ; Wed, 3 Apr 2013 17:52:48 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) by mx1.freebsd.org (Postfix) with ESMTP id D11A92D6 for ; Wed, 3 Apr 2013 17:52:47 +0000 (UTC) Received: by mail-wi0-f181.google.com with SMTP id hj8so1808706wib.8 for ; Wed, 03 Apr 2013 10:52:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=yKgir8Z+n9iI46H+WFolAgJvPGOZu5PRx8CcWDo9fKM=; b=OQXrRFzAlIVDn1+2XKw5sLcMfBQAbk5+59w9m9jCGmhS7p+4B1AvveX8HXLmQ7HaE2 +KGrEPUW0IglBJqxRKA+vgSFUr1C1oxeb6MqyXGeXyqii1tAC0q70KJlhOGTzwPuggJp CnKbSRFP6/SqybV7xYwpFLzGOc7MlWUQkUUMBoE6eUxRshrmV0m31mJJ4mm/HyWfSmJU 0HGpkBRw8cK6XMg8xV3hIkprou5ABBwtzwaDslHxn8Dxr9w+uhDHT+M3ZUkp1BdofthX d4KMFMhLvvXhYgowveHY0F3C0/U51o5czoDt7uXdiK0fhBQHDo/CmRt9/cFDy9DfZLF/ 6cDw== MIME-Version: 1.0 X-Received: by 10.180.188.3 with SMTP id fw3mr4175921wic.33.1365011566877; Wed, 03 Apr 2013 10:52:46 -0700 (PDT) Received: by 10.216.243.7 with HTTP; Wed, 3 Apr 2013 10:52:46 -0700 (PDT) In-Reply-To: References: Date: Wed, 3 Apr 2013 10:52:46 -0700 Message-ID: Subject: Re: Patch ath3kfw to accept other device ids; blacklist ath bluetooth devices From: Adrian Chadd To: Maksim Yevmenkin Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Apr 2013 17:52:48 -0000 Hi, Here you go: http://people.freebsd.org/~adrian/ath/20130401-ath-bluetooth.diff The ath3k driver in linux does a fair bit more than ath3kfw: * if it's a subset of chips that needs firmware, it squirts ath3k-1.fw onto it * there's a subset of chips that get ROM/RAM patches; so if it's one of those, squeeze the patch on; * it also will configure the AR3012 NIC between "config" and "normal" mode when it's loading in those patches. So it's likely that for full support, we're going to have to port over this functionality and throw those firmware / patch / config files somewhere to be uploaded when the relevant device is attached. Thanks, Adrian