From: Dirk Behme <dirk.behme@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v8 3/3] MIPS: Jz4740: Add qi_lb60 board support
Date: Sat, 13 Jul 2013 07:51:13 +0200 [thread overview]
Message-ID: <51E0EAD1.6070100@gmail.com> (raw)
In-Reply-To: <20130703095414.471D2380E12@gemini.denx.de>
Dear Wolfgang and Tom,
Am 03.07.2013 11:54, schrieb Wolfgang Denk:
> Dear Xiangfu Liu,
>
> In message <4E95A3BA.8000905@pobox.com> you wrote:
>>
>> Add support for the qi_lb60 (a.k.a QI Ben NanoNote) clamshell device
>> from Qi hardware:
>>
>> http://en.qi-hardware.com/wiki/Ben_NanoNote
>> http://en.qi-hardware.com/wiki/Main_Page
>> http://en.wikipedia.org/wiki/Qi_hardware
>>
>> This Jz4740-based clamshell device does not use NOR flash to boot.
>> The initial bring-up assumes that U-Boot is directly loaded into SDRAM
>> using USB boot tool, and starts from 0x80100000.
> ...
>> MAINTAINERS | 4 +
>> MAKEALL | 4 +-
>> board/qi/qi_lb60/Makefile | 45 +++++++++
>> board/qi/qi_lb60/config.mk | 31 +++++++
>> board/qi/qi_lb60/qi_lb60.c | 104 +++++++++++++++++++++
>> board/qi/qi_lb60/u-boot.lds | 61 +++++++++++++
>> boards.cfg | 1 +
>> include/configs/qi_lb60.h | 211 +++++++++++++++++++++++++++++++++++++++++++
>> 8 files changed, 460 insertions(+), 1 deletions(-)
>> create mode 100644 board/qi/qi_lb60/Makefile
>> create mode 100644 board/qi/qi_lb60/config.mk
>> create mode 100644 board/qi/qi_lb60/qi_lb60.c
>> create mode 100644 board/qi/qi_lb60/u-boot.lds
>> create mode 100644 include/configs/qi_lb60.h
>
> It has been pointed out (see [1]) that the files
>
> board/qi/qi_lb60/qi_lb60.c
> include/configs/qi_lb60.h
>
> added by this patch are licensed as GPL "version 3 of the License, or
> (at your option) any later version" - however, this is incompatible
> with the GPLv2 and GPLv2+ licenses that cover the rest of U-Boot.
>
> Would you be willing to re-license these files under GPLv2+ (and
> submit apatch to do that) ? Otherwise we would probably be forced to
> remove the qi_lb60 board support to be legally clean.
>
> Sorry for the inconvenience, but obviously this issue slipped through
> at the initial review of the code...
>
> [1] http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/164965
No answer since > one week.
Should we revert this for v2013.07, then?
Best regards
Dirk
[1]
http://git.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=commit;h=3c945542dad99b1ec4a324ad6b69b8de8829827b
next prev parent reply other threads:[~2013-07-13 5:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 14:22 [U-Boot] [PATCH v8 0/3] those series patches for add ben nanonote board Shinya Kuribayashi
2011-10-12 14:25 ` [U-Boot] [PATCH v8 1/3] MIPS: Ingenic XBurst Jz4740 processor support Shinya Kuribayashi
2011-10-12 14:26 ` [U-Boot] [PATCH v8 2/3] MIPS: Jz4740: Add NAND driver Shinya Kuribayashi
2011-10-28 20:38 ` Scott Wood
2011-10-12 14:27 ` [U-Boot] [PATCH v8 3/3] MIPS: Jz4740: Add qi_lb60 board support Shinya Kuribayashi
2013-07-03 9:22 ` [U-Boot] GPL v3 only code in U-Boot Dirk Behme
2013-07-03 9:25 ` Graeme Russ
2013-07-03 9:46 ` Wolfgang Denk
2013-07-03 9:54 ` [U-Boot] [PATCH v8 3/3] MIPS: Jz4740: Add qi_lb60 board support Wolfgang Denk
2013-07-13 5:51 ` Dirk Behme [this message]
2013-07-15 13:59 ` Tom Rini
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=51E0EAD1.6070100@gmail.com \
--to=dirk.behme@gmail.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