From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Proposal for a make option to include an additional stand alone program directory
Date: Fri, 27 Apr 2007 09:45:23 +0200 [thread overview]
Message-ID: <200704270945.24109.sr@denx.de> (raw)
In-Reply-To: <463113F0.4010804@freescale.com>
On Thursday 26 April 2007 23:04, Timur Tabi wrote:
> I think there's a lot of misunderstanding going on here, and it's probably
> my fault for not being clear. The non-GPL firmware is not run on the host
> processor. It is loaded into the memory of an on-board device.
This seems to be the same as needed for the Intel IXP4xx NPE's (Network
Processing Engines). These are on-chip co-processors used for ethernet
communication. And Intel provides a binary image for these NPE's that is
*not* released under a GPL compatible license. And here I know for sure that
this makes is impossible to even "link" this binary into the U-Boot image by
something like "#include "npe-binary.h".
What we have to do instead, is program this binary into a specific FLASH
sector and load it from there into the NPE's. If you "dump" this complete
FLASH image, or generate this combined image via some other tool, then it
should be no problem.
> What I was considering is making a change to the build process so that when
> the user built u-boot.bin, if the firmware binary were present, it would
> merge that into the u-boot.bin binary, for convenience.
>
> > If your version of u-boot has any knowledge about program locations
> > within the closed
> > binary, or vice versa, then you are most likely violating the GPL.
>
> The binary is not being executed by U-Boot, it is being copied into device
> memory by U-Boot via a loader application. If the loader application is
> GPL, then I don't see how this is a GPL violation. However, if the loader
> is not GPL, then I'm not sure.
Please see above. The NPE-loader *is* GPL-compatible in this case and it is
not possible to include the binary of the NPE's in the standard U-Boot build
process.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office: Kirchenstr. 5, D-82194 Groebenzell, Germany
=====================================================================
next prev parent reply other threads:[~2007-04-27 7:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 17:15 [U-Boot-Users] Proposal for a make option to include an additional stand alone program directory Jeff Mann
2007-04-26 18:37 ` David Hawkins
2007-04-26 19:33 ` Jeff Mann
2007-04-26 20:02 ` Wolfgang Denk
2007-04-26 20:43 ` David Hawkins
2007-04-26 18:44 ` Timur Tabi
2007-04-26 19:13 ` Jeff Mann
2007-04-26 19:24 ` Timur Tabi
2007-04-26 20:10 ` Wolfgang Denk
2007-04-26 20:16 ` Timur Tabi
2007-04-26 20:31 ` Wolfgang Denk
2007-04-26 20:05 ` Wolfgang Denk
2007-04-26 20:09 ` Timur Tabi
2007-04-26 20:15 ` Wolfgang Denk
2007-04-26 20:19 ` Timur Tabi
2007-04-26 20:41 ` Wolfgang Denk
2007-04-26 20:53 ` Jerry Van Baren
2007-04-26 20:59 ` Timur Tabi
2007-04-27 9:38 ` Wolfgang Denk
2007-04-27 19:00 ` Timur Tabi
2007-04-27 19:32 ` Ulf Samuelsson
2007-04-27 20:13 ` Jerry Van Baren
2007-04-30 19:51 ` Wolfgang Denk
2007-04-30 19:45 ` Wolfgang Denk
2007-04-26 20:52 ` Ulf Samuelsson
2007-04-26 21:04 ` Timur Tabi
2007-04-27 7:45 ` Stefan Roese [this message]
2007-04-27 9:40 ` Wolfgang Denk
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=200704270945.24109.sr@denx.de \
--to=sr@denx.de \
--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.