From: Chris Packham <judge.packham@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] SBx81CFC960: embed Fman microcode in the bootloader
Date: Sat, 22 Sep 2012 21:44:37 +1200 [thread overview]
Message-ID: <505D8885.5010000@gmail.com> (raw)
In-Reply-To: <20120921155810.12ABB203200@gemini.denx.de>
On 09/22/2012 03:58 AM, Wolfgang Denk wrote:
> Dear judge.packham at gmail.com,
>
> In message <1348216335-18105-1-git-send-email-judge.packham@gmail.com> you wrote:
>> From: Chris Packham <judge.packham@gmail.com>
>>
>> Instead of storing the mircocode in a separate flash block simply embed
>> the image as C code array of bytes.
>
> What exactly is the licensing of this code?
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.
> Would it not have to be GPL compatible to "link" it in such a way,
> which in turn would require the source code and the tools to build
> it ?
Well I took one law paper at university and quickly decided to major in
computer science instead so I am entirely unqualified to comment :).
That being said it probably depends on the definition of "link". No code
is actually being called directly from u-boot, it's just a convenient
transportation mechanism. Still there are statements in the GPL about
what constitutes distributing the code, someone more qualified can
tackle that.
I can understand why for u-boot this might be a gray area. Writing
firmware blobs to a flash block somewhere is a solution that avoids any
problems and makes my patch unsuitable/unnecessary.
next prev parent reply other threads:[~2012-09-22 9:44 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 [this message]
2012-09-24 14:25 ` Timur Tabi
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=505D8885.5010000@gmail.com \
--to=judge.packham@gmail.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 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.