qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Armbrost Failsafe" <armbrost@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] QEMU License and proprietary hardware
Date: Thu, 21 Jun 2007 13:28:53 +0200	[thread overview]
Message-ID: <7d3e40d50706210428g11396d53y73fc12d326d71a59@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 692 bytes --]

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?

/armbrost

[-- Attachment #2: Type: text/html, Size: 711 bytes --]

             reply	other threads:[~2007-06-21 11:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-21 11:28 Armbrost Failsafe [this message]
2007-06-21 22:24 ` [Qemu-devel] QEMU License and proprietary hardware Luke -Jr
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=7d3e40d50706210428g11396d53y73fc12d326d71a59@mail.gmail.com \
    --to=armbrost@gmail.com \
    --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).