xen-devel
[Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching
To: |
Zachary Amsden <zach@xxxxxxxxxx> |
Subject: |
[Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching |
From: |
Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx> |
Date: |
Thu, 16 Mar 2006 20:10:56 +0100 (MET) |
Cc: |
Andrew Morton <akpm@xxxxxxxx>, Joshua LeVasseur <jtl@xxxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Pratap Subrahmanyam <pratap@xxxxxxxxxx>, Wim Coekaerts <wim.coekaerts@xxxxxxxxxx>, Chris Wright <chrisw@xxxxxxxx>, Jack Lo <jlo@xxxxxxxxxx>, Dan Hecht <dhecht@xxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxxxx>, Christopher Li <chrisl@xxxxxxxxxx>, Virtualization Mailing List <virtualization@xxxxxxxxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxx>, Anne Holler <anne@xxxxxxxxxx>, Jyothy Reddy <jreddy@xxxxxxxxxx>, Kip Macy <kmacy@xxxxxxxxxxx>, Ky Srinivasan <ksrinivasan@xxxxxxxxxx>, Leendert van Doorn <leendert@xxxxxxxxxxxxxx>, Dan Arai <arai@xxxxxxxxxx> |
Delivery-date: |
Fri, 17 Mar 2006 10:59:07 +0000 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<200603131802.k2DI2nv8005665@xxxxxxxxxxxxxxxxxxx> |
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
List-post: |
<mailto:xen-devel@lists.xensource.com> |
List-subscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
References: |
<200603131802.k2DI2nv8005665@xxxxxxxxxxxxxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
>
>The question of licensing of such ROM code is a completely separate
>issue. We are not trying to hide some proprietary code by putting it
>inside of a ROM to keep it hidden. In fact, you can disassemble the
>ROM code and see it quite readily - and you know all of the entry points.
>Whether we can distribute our ROM code under a GPL compatible license
>is not something I know at this time. Just as you can't compile a
>binary using Linux kernel headers and claim that your binary is not
>subject to the GPL, our ROM code includes headers from other parts of
>our system that are specifically not under the GPL. How this affects
>the final license under which the ROM is distributed is not something
>I think we know at this time.
The code _you_ wrote can be put under any license(s) you want, so in
the worst case you do not need to rewrite your .c files.
Jan Engelhardt
--
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] [RFC, PATCH 5/24] i386 Vmi code patching, Zachary Amsden
- [Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching,
Jan Engelhardt <=
- [Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching, Andi Kleen
- [Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching, Chris Wright
- [Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching, Anthony Liguori
- [Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching, Chris Wright
- [Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching, Keir Fraser
- Re: [Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching, Zachary Amsden
- Re: [Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching, Eli Collins
- Re: [Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching, Stefan Berger
|
|
|