From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] SBx81CFC960: embed Fman microcode in the bootloader
Date: Mon, 24 Sep 2012 09:25:25 -0500 [thread overview]
Message-ID: <50606D55.7060509@freescale.com> (raw)
In-Reply-To: <505D8885.5010000@gmail.com>
Chris Packham wrote:
> Good point. I got the firmware out of the SDK that came with our
> P2041RDB. I believe the intent was that the Fman microcode is written to
> a reserved flash block and downloaded to the frame manager by the OS
> when needed. As a Freescale customer I would actually prefer to have the
> source released under the GPL and build everything into the u-boot image.
For the record, Freescale considers embedding Fman or QE microcode into a
"GPL binary" (e.g. a compiled U-boot or Linux image) to be a GPL
violation. I'm sure there might be some linker or compiler tricks that
some people would say are not GPL violations, but I'm not going to debate
any of that. I'm just stating what our official position is.
Having said that, I do realize that Freescale still ships some QE firmware
binaries as C header/source files that are supposed to be #included into
customer code. Unfortunately, not all Freescale developers have gotten
the message.
--
Timur Tabi
Linux kernel developer at Freescale
prev parent reply other threads:[~2012-09-24 14:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 9:49 [U-Boot] QE firmware/microcode handling Gerlando Falauto
2012-09-20 15:16 ` Wolfgang Denk
2012-09-20 15:22 ` Timur Tabi
2012-09-20 18:24 ` Scott Wood
2012-09-20 21:28 ` Timur Tabi
2012-09-21 1:55 ` McClintock Matthew-B29882
2012-09-21 8:32 ` [U-Boot] [PATCH] SBx81CFC960: embed Fman microcode in the bootloader judge.packham at gmail.com
2012-09-21 11:32 ` Tabi Timur-B04825
2012-09-21 15:58 ` Wolfgang Denk
2012-09-21 16:30 ` Timur Tabi
2012-09-22 9:44 ` Chris Packham
2012-09-24 14:25 ` Timur Tabi [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=50606D55.7060509@freescale.com \
--to=timur@freescale.com \
--cc=u-boot@lists.denx.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