From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-boot] fastboot command question
Date: Thu, 22 Aug 2013 07:08:50 +0200 [thread overview]
Message-ID: <201308220708.51160.marex@denx.de> (raw)
In-Reply-To: <52155BBC.3040307@boundarydevices.com>
Dear Eric Nelson,
Adding Wolfgang and Tom to CC.
> On 08/21/2013 04:30 AM, TigerLiu at viatech.com.cn wrote:
> > Hi, experts:
> >
> > Why not include cmd_fastboot.c in common directory in 2013.07 release
> > package?
> >
> > Because of code license?
> >
> > Or other reason?
>
> Hi Tiger,
>
> You bring up a question we're interested in as well.
>
> It looks to me as if this died somewhere back in April of 2011
> with this discussion:
>
> http://lists.denx.de/pipermail/u-boot/2011-April/thread.html#90983
>
> And a straw-man design document discussed here:
> http://lists.denx.de/pipermail/u-boot/2011-April/thread.html/#091597
>
> And a message about licensing in May of 2012:
> http://lists.denx.de/pipermail/u-boot/2012-May/125304.html
>
> Do we need a clean-room implementation in order to comply with?
>
> Is anybody working either the licensing or implementation of this?
Not that I am aware of, but I did not follow this discussion at all. What is
fastboot anyway, is that the android thing?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-08-22 5:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 11:30 [U-Boot] [U-boot] fastboot command question TigerLiu at viatech.com.cn
2013-08-22 0:30 ` Eric Nelson
2013-08-22 5:08 ` Marek Vasut [this message]
2013-08-22 9:52 ` TigerLiu at viatech.com.cn
2013-08-22 14:01 ` [U-Boot] " Eric Nelson
2013-08-22 13:56 ` [U-Boot] [U-boot] " Eric Nelson
2013-08-22 13:59 ` Tom Rini
2013-08-22 14:30 ` Eric Nelson
2013-08-22 15:02 ` Tom Rini
2013-08-22 15:26 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2013-08-21 10:15 TigerLiu at viatech.com.cn
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=201308220708.51160.marex@denx.de \
--to=marex@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox