From: Steve Rae <srae@broadcom.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/4] add code to handle Android sparse image format
Date: Fri, 29 Aug 2014 16:13:05 -0700 [thread overview]
Message-ID: <54010901.3020106@broadcom.com> (raw)
In-Reply-To: <201408292254.03094.marex@denx.de>
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 <srae@broadcom.com>
>>>>>>
>>>>>> 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
next prev parent reply other threads:[~2014-08-29 23:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 17:53 [U-Boot] [PATCH v2 0/4] Implement "sparse format" for fastboot Steve Rae
2014-08-28 17:53 ` [U-Boot] [PATCH v2 1/4] add code to handle Android sparse image format Steve Rae
2014-08-28 21:16 ` Tom Rini
2014-08-28 21:31 ` Steve Rae
2014-08-28 21:52 ` Steve Rae
2014-08-29 8:20 ` Marek Vasut
2014-08-29 15:11 ` Tom Rini
2014-08-29 17:38 ` Steve Rae
2014-08-29 20:54 ` Marek Vasut
2014-08-29 23:13 ` Steve Rae [this message]
2014-09-03 0:03 ` Steve Rae
2014-09-03 0:33 ` Tom Rini
2014-08-28 17:53 ` [U-Boot] [PATCH v2 2/4] update code which handles " Steve Rae
2014-08-28 17:53 ` [U-Boot] [PATCH v2 3/4] cleanup code which handles the " Steve Rae
2014-08-28 19:43 ` Tom Rini
2014-08-28 20:33 ` Steve Rae
2014-08-28 17:53 ` [U-Boot] [PATCH v2 4/4] implement " Steve Rae
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=54010901.3020106@broadcom.com \
--to=srae@broadcom.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