From: Kevin Wolf <kwolf@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Taimoor Mirza <mooni_mirza@hotmail.com>,
Niels de Vos <nixpanic@users.sourceforge.net>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: EHCI support in QEMU
Date: Tue, 02 Mar 2010 11:48:40 +0100 [thread overview]
Message-ID: <4B8CED08.2030705@redhat.com> (raw)
In-Reply-To: <4B8C2EFF.3030106@web.de>
Am 01.03.2010 22:17, schrieb Jan Kiszka:
> Niels de Vos wrote:
>> If someone is interested in this partially ported patch, I'm happy to
>> share, but it will at least need some attention to make it compile.
>> After that, lots of tests need to be done and probably quite some
>> bugfixes are required. I'm happy to assist, but do not have a lot of
>> time to spare on this hobby project. On the occasion that it is something
>> more solid and starting to do something, I will of course inform this list
>> again.
>
> OK, to keep this heavy ball rolling, I would suggest posting your patch.
> Either it's already in a good shape to get it merged as experimental
> feature. Or I will pick it up in git tree, collect patches as they fly
> in, and will keep on pushing it upstream. I can't promise spending much
> time on hacking, but integration work, basic testing, and some more or
> less helpful comments should be feasible.
Yes, please post it. I won't promise anything either, but maybe I can
find some time to help a bit. Anyway, I'd love to see EHCI in qemu.
Kevin
next prev parent reply other threads:[~2010-03-02 10:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 4:24 [Qemu-devel] EHCI support in QEMU Taimoor Mirza
2010-02-15 9:36 ` [Qemu-devel] " Jan Kiszka
2010-03-01 20:30 ` Niels de Vos
2010-03-01 21:17 ` Jan Kiszka
2010-03-02 10:48 ` Kevin Wolf [this message]
2010-03-03 11:21 ` Niels de Vos
2010-03-03 22:44 ` David S. Ahern
2010-03-03 23:47 ` Jan Kiszka
2010-03-03 23:58 ` David S. Ahern
2010-03-04 15:24 ` Niels de Vos
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=4B8CED08.2030705@redhat.com \
--to=kwolf@redhat.com \
--cc=jan.kiszka@web.de \
--cc=mooni_mirza@hotmail.com \
--cc=nixpanic@users.sourceforge.net \
--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).