From: Faisal Al-Humaimidi <falhumai96@gmail.com>
To: qemu-devel@nongnu.org
Subject: Permissively Licensing the CPU Component
Date: Wed, 19 Feb 2025 01:59:08 -0800 [thread overview]
Message-ID: <CAMx8kb0zN7CPjuFJatoF+5UBwdLaCA_AJGcxUV8cdBoDd1RBag@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
Hello QEMU developers,
I understand from this page, https://wiki.qemu.org/License, that TCG is
being licensed permissively (BSD license) so it can be integrated as a
library in other projects, which is great! However, I'd like to know if the
CPU part of QEMU, no peripherals included, is also permissively licensed
(maybe BSD or some other permissive license such as LGPL, ...etc.)?
The reason I am asking this question is because projects such as the
Unicorn Engine would greatly benefit from a permissively licensed CPU
component so that the project itself (Unicorn Engine) is also released
under a permissive license, which would be great for people wanting to do
research with the Unicorn Engine but are tied with proprietary code (e.g.,
in proprietary university research projects). I have started a discussion
for that matter with the Unicorn Engine developers in their GitHub page,
https://github.com/unicorn-engine/unicorn/issues/2114, and it would be
great to have a feedback regarding this matter from the official QEMU
developers, whether directly on the issue or a reply to this email and I'd
relay your response.
Kind regards,
Faisal Al-Humaimidi
[-- Attachment #2: Type: text/html, Size: 1491 bytes --]
next reply other threads:[~2025-02-19 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 9:59 Faisal Al-Humaimidi [this message]
2025-02-19 10:22 ` Permissively Licensing the CPU Component Daniel P. Berrangé
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=CAMx8kb0zN7CPjuFJatoF+5UBwdLaCA_AJGcxUV8cdBoDd1RBag@mail.gmail.com \
--to=falhumai96@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).