Hi Kalle,
I'm hitting you up because it looks like you've supplied some firmware
for ath3k devices in the past.
Some new ath3k devices were recently enabled in the kernel [1], however
it looks like there's no firmware available under a license which would
allow distros to redistribute it. According to users at [2] the files
should be named AthrBT_0x11020100.dfu and ramps_0x11020100_40.dfu. Any
chance you or someone else at QCA could help get this into
linux-firmware?
Thanks,
Seth
[1] http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=7e730c7f3d1f39c25cf5f7cf70c0ff4c28d7bec7
[2] http://bugs.launchpad.net/bugs/1394368
On Mon, Aug 17, 2015 at 03:50:10PM +0300, Kalle Valo wrote:
> Hi Seth,
>
> Seth Forshee <[email protected]> writes:
>
> > I'm hitting you up because it looks like you've supplied some firmware
> > for ath3k devices in the past.
> >
> > Some new ath3k devices were recently enabled in the kernel [1], however
> > it looks like there's no firmware available under a license which would
> > allow distros to redistribute it. According to users at [2] the files
> > should be named AthrBT_0x11020100.dfu and ramps_0x11020100_40.dfu. Any
> > chance you or someone else at QCA could help get this into
> > linux-firmware?
>
> I pinged our bluetooth team about this. Remind me again later if the
> firmware is still not yet released.
Great, thanks Kalle.
Seth
Hi Seth,
Seth Forshee <[email protected]> writes:
> I'm hitting you up because it looks like you've supplied some firmware
> for ath3k devices in the past.
>
> Some new ath3k devices were recently enabled in the kernel [1], however
> it looks like there's no firmware available under a license which would
> allow distros to redistribute it. According to users at [2] the files
> should be named AthrBT_0x11020100.dfu and ramps_0x11020100_40.dfu. Any
> chance you or someone else at QCA could help get this into
> linux-firmware?
I pinged our bluetooth team about this. Remind me again later if the
firmware is still not yet released.
--
Kalle Valo