From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Seth Forshee <seth.forshee@canonical.com>
Cc: <linux-bluetooth@vger.kernel.org>
Subject: Re: Missing firmware for AR3012 devices
Date: Mon, 17 Aug 2015 15:50:10 +0300 [thread overview]
Message-ID: <87io8ef5a5.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20150810211649.GB60315@ubuntu-hedt> (Seth Forshee's message of "Mon, 10 Aug 2015 16:16:49 -0500")
Hi Seth,
Seth Forshee <seth.forshee@canonical.com> 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
next prev parent reply other threads:[~2015-08-17 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 21:16 Missing firmware for AR3012 devices Seth Forshee
2015-08-17 12:50 ` Kalle Valo [this message]
2015-08-17 15:36 ` Seth Forshee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87io8ef5a5.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=seth.forshee@canonical.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.