From: Josh Boyer <jwboyer@kernel.org>
To: Tedd Ho-Jeong An <tedd.an@intel.com>
Cc: linux-firmware@kernel.org,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"Bag, Amit K" <amit.k.bag@intel.com>,
"matt.chen@intel.com" <matt.chen@intel.com>
Subject: Re: [PATCH 1/4] linux-firmware: Add firmware file for Intel Bluetooth 9560
Date: Tue, 5 Dec 2017 13:15:06 -0500 [thread overview]
Message-ID: <CA+5PVA5ViRVRG53TSvUDOKcTx8pFV2FcmNaVcuEebB22xqE9eg@mail.gmail.com> (raw)
In-Reply-To: <20171130101838.69b51124@tedd-ubuntu-vm>
On Thu, Nov 30, 2017 at 1:18 PM, Tedd Ho-Jeong An <tedd.an@intel.com> wrote:
> From: Tedd Ho-Jeong An <tedd.an@intel.com>
>
> This patch adds the firmware file for Intel Bluetooth 9560
> Also it is known as Intel JeffersonPeak (JfP).
>
> FW Build: REL0186
>
> 9560:
> BL Ver: 37 11 10 06 01 2a 34 0f 00
> FW Ver: 37 11 10 23 01 ba 2c 11 00
>
> Release Version: 20.10
> ibt-17-x-x.sfi/ddc format will be used from 4.14 kernel version. Below
> is the commit ID for driver changes.
> https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=af3715e5cef8859571cabecc71e1cd4cc5869d6a
>
> Signed-off-by: Amit K Bag <amit.k.bag@intel.com>
> Signed-off-by: Tedd Ho-Jeong An <tedd.an@intel.com>
All four patches applied and pushed out. Thanks.
josh
next parent reply other threads:[~2017-12-05 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171130101838.69b51124@tedd-ubuntu-vm>
2017-12-05 18:15 ` Josh Boyer [this message]
2017-12-05 22:25 ` [PATCH 1/4] linux-firmware: Add firmware file for Intel Bluetooth 9560 Josh Boyer
2017-12-06 22:33 ` Kyle McMartin
2017-12-06 23:07 ` Kyle McMartin
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=CA+5PVA5ViRVRG53TSvUDOKcTx8pFV2FcmNaVcuEebB22xqE9eg@mail.gmail.com \
--to=jwboyer@kernel.org \
--cc=amit.k.bag@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-firmware@kernel.org \
--cc=matt.chen@intel.com \
--cc=tedd.an@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).