On 14-08-29 04:13 PM, Steve Rae wrote:


On 14-08-29 01:54 PM, Marek Vasut wrote:
On Friday, August 29, 2014 at 07:38:39 PM, Steve Rae wrote:
On 14-08-29 08:11 AM, Tom Rini wrote:
On Thu, Aug 28, 2014 at 02:52:40PM -0700, Steve Rae wrote:
On 14-08-28 02:31 PM, Steve Rae wrote:
On 14-08-28 02:16 PM, Tom Rini wrote:
On Thu, Aug 28, 2014 at 10:53:51AM -0700, Steve Rae wrote:
Add original file (pristine) from :

https://www.codeaurora.org/cgit/quic/la/kernel/lk/plain/app/aboot/abo

ot.c?h=master

[3b5092d20bd15a7a2879c13e9f64acc48d04af2d]

Signed-off-by: Steve Rae <[email protected]>

OK, let us back the truck up, so to speak.  This particular
version of
the file has an odd license.  Looking at
https://android.googlesource.com/kernel/lk/+/master/app/aboot/aboot.c

[54963a727d3e4ed1e945c7ec012b5cc5de168ac5] and it has the normal
BSD-3-Clause text.  Lets grab and adapt that so we can drop the
license issue.

OK -- "v3" coming soon!

OOPS! -- this "aboot.c" does not contain the support for the "sparse
image format" -- I cannot use this file!

Can you poke around more for a version of aboot.c that has sparse image
support and comes more directly from google.com and thus hopefully
someone caught the rather strange license text changes?

I have previously spent hours looking for:
(1) sparse_format.h -- which we now have (thanks to Colin Cross)
(2) any implementation of the "while()" loop which parses this "sparse
format"
This implementation, in aboot.c (also recommended by Colin Cross), is
also available from "Code Aurora" -- but it has the same wording as the
"Linux Foundation" file; I have not found it anywhere else.
I cannot spend any more time on this license issue....
Please keep me informed of the outcome!

... and, this is how it ends. Again, legal crap proved to be a death
sentence
for a patch and carried with it an excessive amount of wasted effort.

Best regards,
Marek Vasut


I certainly hope not 100% dead!!!!
If U-Boot would accept (the currently one-off) BSD-3L-Clause, then this
could live!
Thanks, Steve

Any progress on the license wording?

(1) create BSD-3L-Clause
or
(2) leave the original text in place, and add the following:
 * NOTE:
 *   Although it is very similar, this license text is not identical
 *   to the "BSD-3-Clause", therefore, DO NOT MODIFY THIS LICENSE TEXT!
or
(3) ???

Please let me know!
Thanks, Steve
_______________________________________________
U-Boot mailing list
[email protected]
http://lists.denx.de/mailman/listinfo/u-boot

Reply via email to