From: David Woodhouse <dwmw2@infradead.org>
To: David Henningsson <david.henningsson@canonical.com>
Cc: "chase.douglas@canonical.com" <chase.douglas@canonical.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Merging alsa-firmware into linux-firmware
Date: Wed, 21 Jul 2010 10:31:28 +0100 [thread overview]
Message-ID: <1279704688.6002.4.camel@localhost> (raw)
In-Reply-To: <4C46BE09.5050309@canonical.com>
On Wed, 2010-07-21 at 11:29 +0200, David Henningsson wrote:
> On 2010-07-20 12:51, David Woodhouse wrote:
> > On Tue, 2010-07-20 at 11:38 +0100, David Henningsson wrote:
> >> Hi,
> >>
> >> Chase Douglas (@canonical) and I plan to take what's left of
> >> alsa-firmware and try to merge it into linux-firmware, this might happen
> >> now or in the coming weeks. This will make alsa-firmware obsolete as all
> >> firmware will be provided by linux-firmware instead.
> >>
> >> Any words of disagreement, warnings or encouragement before we do so?
> >
> > Encouragement, certainly...
>
> Great!
>
> There are a few firmwares (e g echoaudio and hdsploader) that actually
> are .c files with a big constant array in it, like this:
>
> static u_int32_t digiface_firmware[24413] = {
> 0xffffffff, 0x66aa9955, 0x8001000c, 0xe0000000, 0x8006800c, 0xb0000000,
> 0x8004800c, 0xb4fc0100, 0x8003000c, 0x00000000, 0x8001000c, 0x90000000,
> ...etc...
>
> Would you prefer the actual .c files in the linux-firmware git tree
> source (and the makefile that goes with it), or just the output from
> them (the binary firmware files)?
If it's just a big constant array, you might as well just give me the
binary. If there's *real* source, we'd want that too.
--
dwmw2
next prev parent reply other threads:[~2010-07-21 9:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 10:38 Merging alsa-firmware into linux-firmware David Henningsson
2010-07-20 10:51 ` David Woodhouse
2010-07-21 9:29 ` David Henningsson
2010-07-21 9:31 ` David Woodhouse [this message]
2010-07-26 8:15 ` David Henningsson
2010-07-26 8:36 ` Takashi Iwai
2010-07-20 13:31 ` Clemens Ladisch
2010-07-20 15:47 ` David Henningsson
2010-07-21 6:53 ` Clemens Ladisch
2010-07-21 13:31 ` David Henningsson
2010-07-21 14:02 ` David Woodhouse
2010-07-21 14:30 ` David Henningsson
2010-07-20 13:36 ` Takashi Iwai
2010-07-22 10:07 ` David Henningsson
2010-07-22 11:20 ` Takashi Iwai
2010-07-22 12:41 ` David Henningsson
2010-07-22 12:46 ` Takashi Iwai
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=1279704688.6002.4.camel@localhost \
--to=dwmw2@infradead.org \
--cc=alsa-devel@alsa-project.org \
--cc=chase.douglas@canonical.com \
--cc=david.henningsson@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox