Date: Wed, 3 Apr 2013 10:52:46 -0700 From: Adrian Chadd <adrian.chadd@gmail.com> To: Maksim Yevmenkin <maksim.yevmenkin@gmail.com> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: Patch ath3kfw to accept other device ids; blacklist ath bluetooth devices Message-ID: <CAJ-Vmok7SsgATVjAvmh23ttsSSbvQ-8h4JpgySNXT3244h=XRA@mail.gmail.com> In-Reply-To: <CAJ-Vmok3_1cntVzVDVkjKxC8O%2BE6h7YkG_v2-4F4G5zeE38SRg@mail.gmail.com> References: <CAJ-VmomR2VAEoup2CZsBGvWFmgu0rTCfPv2kSpnq6qGNQNLXrQ@mail.gmail.com> <CAFPOs6qUf=rr2PAgdSyRZGnkmZmzLO28szz-GFwy4xDQQiLUfA@mail.gmail.com> <CAJ-Vmok3_1cntVzVDVkjKxC8O%2BE6h7YkG_v2-4F4G5zeE38SRg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmok7SsgATVjAvmh23ttsSSbvQ-8h4JpgySNXT3244h=XRA>