From: malc <av1474@comtv.ru>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Development ideas
Date: Mon, 2 Feb 2009 13:33:26 +0300 (MSK) [thread overview]
Message-ID: <Pine.LNX.4.64.0902021330360.2184@linmac.oyster.ru> (raw)
In-Reply-To: <62296.66.114.33.28.1233532262.squirrel@webmail.bespin.org>
On Sun, 1 Feb 2009, Scott Conrad VanderWoude wrote:
> Qemu is great: Before taking classes in a networking-focused college
QEMU
> curriculum, I learned quite a bit about networking using just one
> dedicated server by having it run multiple Qemu instances communicate
> with each other. I haven't joined the Qemu development team with a bunch
> of volunteer labor since the project I'm involved with to freely help
> others is a different one, but please know the development efforts have
> tremendously helped and been appreciated. Thank you kindly.
>
> I've probably been using Qemu for a few years now, and have noticed new
[..snip..]
> Gravis Ultrasound support: Will it simply be new to version 0.92, or is
0.9.2
> this purposefully being kept out of mainstream Qemu for some reason (like
> Intellectual Property concerns)? Adding a new sound card may take more
> effort than the previously-mentioned tweaks, but I had seen it at Mac's
malc's
> GIT repository
> http://repo.or.cz/w/qemu/malc.git?a=commit;h=052aedb6c704c4f4b9d6875db35d8e1eeaffeade
> and now at
> http://svn.savannah.gnu.org/viewvc/trunk/hw/?root=qemu
> and some versions of Qemu documentation on the web seem to refer to it.
> However, I haven't been seeing it included in the pre-compiled Qemu
> packages bundled with the operating systems I've been using, and so
> haven't experienced it yet.
It's up-to binary distribution maintainers, GUS emulation is under 3
clause BSD license, just like the rest of audio cards emulated by QEMU
save for ac97.c.
[..snip..]
--
mailto:av1474@comtv.ru
prev parent reply other threads:[~2009-02-02 10:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 23:51 [Qemu-devel] Development ideas Scott Conrad VanderWoude
2009-02-02 10:33 ` malc [this message]
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=Pine.LNX.4.64.0902021330360.2184@linmac.oyster.ru \
--to=av1474@comtv.ru \
--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).