From: Pascal Terjan <pterjan@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] new pcnet patch ?
Date: Thu, 12 Jan 2006 23:29:07 +0100 [thread overview]
Message-ID: <e8ca35370601121429m555cdcfbga6c2f273e58dbcf2@mail.gmail.com> (raw)
In-Reply-To: <dq5r7o$hb5$1@sea.gmane.org>
On 1/12/06, Ludovic Drolez <ldrolez@linbox.com> wrote:
> Anyone has an updated pcnet patch for 0.8.0 ?
I updated the patch but I had to make choices and I wanted to discuss
them here. As I have no time these days I had not yet posted it here
:/
The patch is on :
http://cvs.mandriva.com/cgi-bin/cvsweb.cgi/contrib-SPECS/qemu/qemu-0.8.0-pcnet.patch6
There are 2 points I'd like to discuss :
- the way to have several cards of different models at the same time
I added an enum {NIC_NE2000, NIC_PCNET} NICModel and the a field model
in NICInfo
- the options syntax
I added "-net pcnet[,vlan=n][,macaddr=addr]\n" but would be better
having an unique option and a way to specify model
next prev parent reply other threads:[~2006-01-12 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 15:05 [Qemu-devel] new pcnet patch ? Ludovic Drolez
2006-01-12 22:29 ` Pascal Terjan [this message]
2006-01-13 10:02 ` [Qemu-devel] " Ludovic Drolez
2006-01-15 13:00 ` Iain McFarlane
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=e8ca35370601121429m555cdcfbga6c2f273e58dbcf2@mail.gmail.com \
--to=pterjan@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).