qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Antony T Curtis <antony.t.curtis@ntlworld.com>
To: David Black <dave@jamsoft.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: QEMU pcnet 6/28 patch against 6/30 CVS - not working?
Date: Fri, 02 Jul 2004 11:25:03 +0100	[thread overview]
Message-ID: <1088763903.911.14.camel@pcgem.rdg.cyberkinetica.com> (raw)
In-Reply-To: <40E46BE1.3030904@jamsoft.com>

[-- Attachment #1: Type: text/plain, Size: 855 bytes --]

On Thu, 2004-07-01 at 20:54, David Black wrote:
> Hello,
> 
> I applied your AMD pcnet NIC patch dated 6/28, to the QEMU CVS snapshot 
> from dad-answers.com dated 6/30.
> 
> The patch seems to apply well, with some manual patching needed on vl.c 
> and Makefile.target, but nothing that looked problematic.

The patch attached should apply more cleanly against current CVS.

I will try to see if it works any differently with running Linux. I
assume you are using the pcnet32 driver, not the lance driver. Looking
at the Linux driver source, it is able to use the DWORD I/O mode ... The
FreeBSD, WinXP and OS/2 drivers appear to use the WORD I/O mode. It is
possible that there is a bug in the simulation - particularly where the
Linux driver probes the card in both modes. I will have to test it out.

-- 
Antony T Curtis <antony.t.curtis@ntlworld.com>

[-- Attachment #2: qemu-pcnet.patch2.gz --]
[-- Type: application/x-gzip, Size: 15163 bytes --]

       reply	other threads:[~2004-07-02 10:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <40E46BE1.3030904@jamsoft.com>
2004-07-02 10:25 ` Antony T Curtis [this message]
     [not found]   ` <40E5B44C.1050100@jamsoft.com>
2004-07-03 10:40     ` [Qemu-devel] Re: QEMU pcnet 6/28 patch against 6/30 CVS - not working? Antony T Curtis
2004-07-04 13:05       ` Hetz Ben Hamo
2004-07-03 23:37         ` Antony T Curtis
2004-07-04 17:57       ` Brad Watson

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=1088763903.911.14.camel@pcgem.rdg.cyberkinetica.com \
    --to=antony.t.curtis@ntlworld.com \
    --cc=dave@jamsoft.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).