From: Ben Hutchings <ben@decadent.org.uk>
To: Takashi Iwai <tiwai@suse.de>
Cc: Ian Minett <ian_minett@creativelabs.com>,
linux-kernel@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [GIT PULL] Firmware files for CA0132 HD-audio codec (v2)
Date: Sun, 21 Apr 2013 19:40:06 +0100 [thread overview]
Message-ID: <1366569606.3408.121.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <s5hfvyrotfg.wl%tiwai@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]
On Tue, 2013-04-16 at 08:56 +0200, Takashi Iwai wrote:
> Hi Ben,
>
> could you pull the firmware files for Creative CA0132 HD-audio codec
> driver from below? It's the revised version.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/linux-firmware.git tags/ca0132-fw-v2
Pulled, thanks.
Ben.
> ----------------------------------------------------------------
> Firmware files for CA0132 HD-audio codec (v2)
>
> This contains the external firmware files loaded by Creative CA0132
> HD-audio codec driver. The firmwares are used optionally since 3.9
> kernel.
>
> v1->v2: fix the installation path of ct*.bin firmware files
>
> ----------------------------------------------------------------
> Ian Minett (1):
> linux-firmware: Add firmware files for Creative CA0132 HD-audio codec
>
> LICENCE.ca0132 | 48 ++++++++++++++++++++++++++++++++++++++++++++++++
> WHENCE | 11 +++++++++++
> ctefx.bin | Bin 0 -> 655436 bytes
> ctspeq.bin | Bin 0 -> 4120 bytes
> 4 files changed, 59 insertions(+)
> create mode 100644 LICENCE.ca0132
> create mode 100644 ctefx.bin
> create mode 100644 ctspeq.bin
>
>
> Thanks!
>
> Takashi
>
--
Ben Hutchings
All extremists should be taken out and shot.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2013-04-21 18:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 6:56 Takashi Iwai
2013-04-21 18:40 ` Ben Hutchings [this message]
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=1366569606.3408.121.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=dwmw2@infradead.org \
--cc=ian_minett@creativelabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®