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>, Hetz Ben Hamo <hetz@witch.dyndns.org>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: QEMU pcnet 6/28 patch against 6/30 CVS - not working?
Date: Sat, 03 Jul 2004 11:40:01 +0100	[thread overview]
Message-ID: <1088851201.376.3.camel@pcgem.rdg.cyberkinetica.com> (raw)
In-Reply-To: <40E5B44C.1050100@jamsoft.com>

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

Hi,

This new patch works for me with Mandrake 10 Official

It should apply cleanly against QEMU CVS and hopefully compile cleanly
on Linux as well as FreeBSD. I have also implemented the TX-ring poll so
in theory, it should be fully functional.

On Fri, 2004-07-02 at 20:15, David Black wrote:
> Thanks - yes, it's the 'pcnet' driver, and it comes up in 32 bit mode:
> 
> Jul  1 14:04:22 vs1a kernel: pcnet32.c:v1.27b 01.10.2002
> tsbogend@alpha.franken.de
> Jul  1 14:04:22 vs1a kernel: PCI: Found IRQ 9 for device 0000:00:03.0
> Jul  1 14:04:22 vs1a kernel: PCI: Setting latency timer of device
> 0000:00:03.0 to 64
> Jul  1 14:04:22 vs1a kernel: pcnet32: PCnet/PCI II 79C970A at 0xc020,
> warning: CSR address invalid,
> Jul  1 14:04:22 vs1a kernel:     using instead PROM address of 52 54
> 00 12 34 56 assigned IRQ 9.
> Jul  1 14:04:22 vs1a kernel: eth0: registered as PCnet/PCI II 79C970A
> Jul  1 14:04:22 vs1a kernel: pcnet32: 1 cards_found.
> 
> This driver is attractive to me because of the promise of decreased
> latency.  I get occasional data corruption with the ne2k-pci driver,
> too.
> 
> Dave
> 
> Antony T Curtis wrote: 
> > 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.
> > 
> >   
> FLAGS (\Seen))
-- 
Antony T Curtis <antony.t.curtis@ntlworld.com>

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

  parent reply	other threads:[~2004-07-03 10:49 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 ` [Qemu-devel] Re: QEMU pcnet 6/28 patch against 6/30 CVS - not working? Antony T Curtis
     [not found]   ` <40E5B44C.1050100@jamsoft.com>
2004-07-03 10:40     ` Antony T Curtis [this message]
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=1088851201.376.3.camel@pcgem.rdg.cyberkinetica.com \
    --to=antony.t.curtis@ntlworld.com \
    --cc=dave@jamsoft.com \
    --cc=hetz@witch.dyndns.org \
    --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).