From: Alex Zeffertt <ajz@cambridgebroadband.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] GPL 2 "or later" concern
Date: Tue, 19 Sep 2006 13:56:41 +0100 [thread overview]
Message-ID: <450FE909.1060504@cambridgebroadband.com> (raw)
In-Reply-To: <450FCA70.3060809@warmcat.com>
Andy Green wrote:
>
> Because the hardware is fixed, and the special nature of what U-boot
> does, a workaround for me might be to never update U-boot, but obviously
> that is less than fully desirable. That way we ship U-boot in the
> flash, provide sources for it, but never distribute a signed update
> avoiding the proposed potential problem.
>
I know this doesn't relate to your original question about licences, but
it would seem to me that distributing u-boot updates is *very* risky. One
slip and every customer could be sending you back dead units in the post.
If you make sure before you sell that u-boot can boot a kernel, and upgrade
the kernel (without assuming a working kernel is present) you won't need to
support u-boot upgrades.
Alex
next prev parent reply other threads:[~2006-09-19 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 18:05 [U-Boot-Users] GPL 2 "or later" concern Andy Green
2006-09-19 9:27 ` Alex Zeffertt
2006-09-19 10:46 ` Andy Green
2006-09-19 12:56 ` Alex Zeffertt [this message]
2006-09-19 19:17 ` Jerry Van Baren
2006-09-19 20:02 ` Andy Green
2006-09-19 21:11 ` Jerry Van Baren
2006-09-19 22:00 ` Andy Green
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=450FE909.1060504@cambridgebroadband.com \
--to=ajz@cambridgebroadband.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