From: Antony T Curtis <antony.t.curtis@ntlworld.com>
To: Karel Gardas <kgardas@objectsecurity.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Updated 3c509 NIC patch.
Date: Thu, 20 Jan 2005 12:17:40 +0000 [thread overview]
Message-ID: <1106223460.75381.6.camel@pcgem.rdg.cyberkinetica.com> (raw)
In-Reply-To: <Pine.LNX.4.43.0501201031360.806-100000@thinkpad.gardas.net>
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
On Thu, 2005-01-20 at 10:31 +0100, Karel Gardas wrote:
> On Wed, 19 Jan 2005, Antony T Curtis wrote:
>
> > Hi,
> >
> > I think I have found the bug... will be making a new patch soon.
>
> Great! Thanks!
Actually, I have not only found the bug you encountered, but I have
found some other bugs in the implementation.
I have also implemented a "info pnp" command.
I have tested it with the following guests: FreeBSD 4, NetBSD 2 and
Linux (Mandrake 8) with up to 4 NICs configured (dummynet).
Hope this works for you,
> Karel
> --
> Karel Gardas kgardas@objectsecurity.com
> ObjectSecurity Ltd. http://www.objectsecurity.com
>
--
Antony T Curtis, BSc. UNIX, Linux, *BSD, Networking
antony.t.curtis@ntlworld.com C++, J2EE, Perl, MySQL, Apache
IT Consultancy.
[-- Attachment #2: qemu-3c509b.20050120.patch.gz --]
[-- Type: application/x-gzip, Size: 8863 bytes --]
[-- Attachment #3: qemu-isapnp.20050120.patch.gz --]
[-- Type: application/x-gzip, Size: 11828 bytes --]
next parent reply other threads:[~2005-01-20 12:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.43.0501201031360.806-100000@thinkpad.gardas.net>
2005-01-20 12:17 ` Antony T Curtis [this message]
2005-01-20 15:07 ` [Qemu-devel] Updated 3c509 NIC patch Karel Gardas
2005-01-20 16:56 ` Antony T Curtis
2005-01-20 17:13 ` Karel Gardas
2005-01-20 20:15 ` Karel Gardas
2005-01-20 21:21 ` Antony T Curtis
2005-01-20 21:54 ` Karel Gardas
2005-01-19 10:51 Karel Gardas
2005-01-19 13:09 ` Antony T Curtis
2005-01-19 17:28 ` Antony T Curtis
2005-01-19 18:59 ` Karel Gardas
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=1106223460.75381.6.camel@pcgem.rdg.cyberkinetica.com \
--to=antony.t.curtis@ntlworld.com \
--cc=kgardas@objectsecurity.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).