From owner-freebsd-current@FreeBSD.ORG  Wed Apr  3 18:16:54 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 E58F3472
 for <freebsd-current@freebsd.org>; Wed,  3 Apr 2013 18:16:54 +0000 (UTC)
 (envelope-from maksim.yevmenkin@gmail.com)
Received: from mail-da0-x22c.google.com (mail-da0-x22c.google.com
 [IPv6:2607:f8b0:400e:c00::22c])
 by mx1.freebsd.org (Postfix) with ESMTP id C092F617
 for <freebsd-current@freebsd.org>; Wed,  3 Apr 2013 18:16:54 +0000 (UTC)
Received: by mail-da0-f44.google.com with SMTP id z20so773241dae.31
 for <freebsd-current@freebsd.org>; Wed, 03 Apr 2013 11:16:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=x-received:references:mime-version:in-reply-to:content-type
 :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date
 :to; bh=ziNa8QwiAUfbdwSN9zZxswgkfHq0N8rSxSYosPbRg+k=;
 b=iKV2K6kxNMsw+gCgBvIb/0P/OIFolXXSi9N/cBECQiMuic4QQFulA4U8swn6ENoBLq
 67ARz9vQPBCFk+VO5Wkvj8svrq2KOIVUKZLMXqDGy5BAkd8RymZ8r2VIlDPqVOctqswM
 O+jWu212/mr7B+YRqsbOH+tkMp+A8k2CdR5sREqYwg75y5s8XltJbVhQAMDwZI4ONrIT
 25AjETn/w8hxUS5Bi14SVkqWtJ6aErZi6mznrbg//cJl9qgyBKe93A20l+e5JR4tw6x/
 TnaD3hLM5+y1Gd/S+tyAIs89kHGBke5AyBSNAKUni5eg8RgcL0PCMpPn0PVaQPO3SJt3
 f/oA==
X-Received: by 10.66.164.198 with SMTP id ys6mr4773674pab.77.1365013014611;
 Wed, 03 Apr 2013 11:16:54 -0700 (PDT)
Received: from [10.52.223.122] (mobile-166-137-177-095.mycingular.net.
 [166.137.177.95])
 by mx.google.com with ESMTPS id pa2sm6971057pac.9.2013.04.03.11.16.50
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Wed, 03 Apr 2013 11:16:53 -0700 (PDT)
References: <CAJ-VmomR2VAEoup2CZsBGvWFmgu0rTCfPv2kSpnq6qGNQNLXrQ@mail.gmail.com>
 <CAFPOs6qUf=rr2PAgdSyRZGnkmZmzLO28szz-GFwy4xDQQiLUfA@mail.gmail.com>
 <CAJ-Vmok3_1cntVzVDVkjKxC8O+E6h7YkG_v2-4F4G5zeE38SRg@mail.gmail.com>
 <CAJ-Vmok7SsgATVjAvmh23ttsSSbvQ-8h4JpgySNXT3244h=XRA@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CAJ-Vmok7SsgATVjAvmh23ttsSSbvQ-8h4JpgySNXT3244h=XRA@mail.gmail.com>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <F2DA2B15-A950-4DC2-946A-A85BB1D9BC5B@gmail.com>
X-Mailer: iPhone Mail (10B329)
From: maksim yevmenkin <maksim.yevmenkin@gmail.com>
Subject: Re: Patch ath3kfw to accept other device ids;
 blacklist ath bluetooth devices
Date: Wed, 3 Apr 2013 11:16:47 -0700
To: Adrian Chadd <adrian.chadd@gmail.com>
Cc: freebsd-current <freebsd-current@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 18:16:55 -0000

Hi Adrian !

Thank you for your work. I briefly looked at it and it seems fine to me.  I'=
m not able to give it a proper review as I'm traveling internationally curre=
ntly. Having said all that, I think it would be reasonable to commit it as i=
s into head.=20

Thanks,
Max


On Apr 3, 2013, at 10:52 AM, Adrian Chadd <adrian.chadd@gmail.com> wrote:

> Hi,
>=20
> Here you go:
>=20
> http://people.freebsd.org/~adrian/ath/20130401-ath-bluetooth.diff
>=20
> The ath3k driver in linux does a fair bit more than ath3kfw:
>=20
> * if it's a subset of chips that needs firmware, it squirts ath3k-1.fw ont=
o 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.
>=20
> 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.
>=20
> Thanks,
>=20
>=20
>=20
> Adrian