From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: dheitmueller@kernellabs.com
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: xc2038/3028 firmware
Date: Sat, 22 Mar 2014 13:22:53 +0100 [thread overview]
Message-ID: <532D809D.4060605@googlemail.com> (raw)
In-Reply-To: <CAGoCfizciqjEZ0QTtvSitAUYORjDFFM1br2xF3drnVSTUwzXdg@mail.gmail.com>
Hi Devin,
Am 21.03.2014 18:38, schrieb Devin Heitmueller:
> Hi Frank,
>
> I specifically asked for and received permission from
> Xceive/CrestaTech to make the xc5000 firmware freely redistributable.
> They were unwilling to entertain that though for the xc2028/3028 as
> they considered it a long deprecated product.
>
> In order to include firmware blobs in linux-firmware, there needs to
> be an actual license legally permitting redistribution - we don't have
> that for the 2028/3028.
>
> In general CrestaTech have been extremely cooperative with the Linux
> community, especially in recent years. However in this case they just
> couldn't justify the effort to do the paperwork for a chip that they
> stopped shipping years ago.
>
> Devin
Ok, so you've already asked them for a xc2028/3028 firmware
redistribution permission, but (in opposition to the xc5000) they didn't
grant it ?
Too bad. :-(
The xc2028/3028 is used in so many devices and playing manual firmware
extraction games sucks.
A too big obstacle for many users (if they even find out that their
device isn't working due to missing firmware)...
Regards,
Frank
> On Fri, Mar 21, 2014 at 1:25 PM, Frank Schäfer
> <fschaefer.oss@googlemail.com> wrote:
>> Hi,
>>
>> are there any reasons why the xc2028/3028 firmware files are not
>> included in the linux-firmware tree ?
>> The xc5000 firmware is already there, so it seems Xceive|has nothing
>> against| redistribution of their firmware... ?!
>>
>> Regards,
>> Frank
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-media" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2014-03-22 12:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 17:25 xc2038/3028 firmware Frank Schäfer
2014-03-21 17:38 ` Devin Heitmueller
2014-03-22 12:22 ` Frank Schäfer [this message]
[not found] <532C7581.2080503@googlemail.com>
2014-03-21 17:51 ` Mauro Carvalho Chehab
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=532D809D.4060605@googlemail.com \
--to=fschaefer.oss@googlemail.com \
--cc=dheitmueller@kernellabs.com \
--cc=linux-media@vger.kernel.org \
/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.