U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Proposal for a make option to include an additional stand alone program directory
Date: Thu, 26 Apr 2007 22:52:44 +0200	[thread overview]
Message-ID: <00ed01c78845$19bbd690$01c4af0a@Glamdring> (raw)
In-Reply-To: 463106E6.20203@freescale.com

----- Original Message ----- 
From: "Timur Tabi" <timur@freescale.com>
To: "Wolfgang Denk" <wd@denx.de>
Cc: <u-boot-users@lists.sourceforge.net>; "Jeff Mann" 
<MannJ@embeddedplanet.com>
Sent: Thursday, April 26, 2007 10:09 PM
Subject: Re: [U-Boot-Users] Proposal for a make option to include an 
additional stand alone program directory


> Wolfgang Denk wrote:
>
>> You cannot link non-GPL code into U-Boot.
>
> What if I use mkimage to merge u-boot.bin with proprietaryfirmware.bin?
>
> If that doesn't work, what if I burn u-boot.bin into flash at some 
> location, and then burn
> proprietaryfirmware.bin into flash at another location, and then I create 
> an an image file
> by copying all of flash?
>
> It depends on how you define linking.  I would say that taking two 
> binaries, one from GPL
> code and one from non-GPL code, and just merging them into another binary, 
> that cannot be
> a GPL violation.
>


If  combining U-Boot with the switch binary results in that you can tftp 
from any
of the 5 ports , and this is not possible without combining with the binary, 
then you
are most likely violating the GPL.

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.

If u-boot is used to start your closed binary, then you are IMO, not 
violating GPL.



Best Regards
Ulf Samuelsson

  parent reply	other threads:[~2007-04-26 20:52 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 [this message]
2007-04-26 21:04         ` Timur Tabi
2007-04-27  7:45           ` Stefan Roese
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='00ed01c78845$19bbd690$01c4af0a@Glamdring' \
    --to=ulf@atmel.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