From: Luke -Jr <luke@dashjr.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU License and proprietary hardware
Date: Thu, 21 Jun 2007 17:24:25 -0500 [thread overview]
Message-ID: <200706211724.25832.luke@dashjr.org> (raw)
In-Reply-To: <7d3e40d50706210428g11396d53y73fc12d326d71a59@mail.gmail.com>
On Thursday 21 June 2007 06:28, Armbrost Failsafe wrote:
> We are looking into using QEMU as the base for a model of a custom system
> featuring some custom ASICs. But licensing issues are halting the process
> right now. Does anyone know what happens license-wise if we create a model
> of proprietary hardware using QEMU? Is that model automatically covered by
> the GPL and thus we have to give to anyone who asks about it? It is clear
> that if we keep it internal, it is OK. But anyone outside of our
> organization is to use it, shouldn't they automatically be entitled to
> receive the entire source of QEMU, including our models of proprietary
> devices? Even if these are developed from scratch without using any
> existing source code for devices?
Yep, that's the purpose of the GPL. It'll probably get a lot of people
promoting it if you do a public release, too...
next prev parent reply other threads:[~2007-06-21 22:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 11:28 [Qemu-devel] QEMU License and proprietary hardware Armbrost Failsafe
2007-06-21 22:24 ` Luke -Jr [this message]
2007-06-21 22:33 ` M. Warner Losh
2007-06-22 15:18 ` Luke -Jr
2007-06-22 16:07 ` Warner Losh
2007-06-22 16:23 ` Luke -Jr
2007-06-22 16:46 ` M. Warner Losh
2007-06-22 17:11 ` Luke -Jr
2007-06-22 17:30 ` M. Warner Losh
2007-06-22 17:31 ` Ronnie Misra
2007-06-22 17:37 ` Johannes Schindelin
2007-06-22 18:00 ` Luke -Jr
2007-06-22 18:22 ` Johannes Schindelin
2007-06-24 20:10 ` Paul Brook
-- strict thread matches above, loose matches on Subject: below --
2007-06-22 5:34 Balazs Attila-Mihaly (Cd-MaN)
2007-06-22 15:21 ` Luke -Jr
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=200706211724.25832.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).