qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Antony T Curtis <antony.t.curtis@ntlworld.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] amd pcnet works with ecos/x86
Date: Wed, 11 Aug 2004 14:03:03 +0100	[thread overview]
Message-ID: <1092229212.83749.23.camel@pcgem.rdg.cyberkinetica.com> (raw)
In-Reply-To: <20040811142049.32307a53.jani@iv.ro>

On Wed, 2004-08-11 at 12:20, Jani Monoses wrote:
> Hello Anthony
> 
> I used your patch since ecos support PCNet and not NE2000 and it works
> fine(i.e resists ping floods)
> One thing which I needed to modify in ecos was the checking of ANR register
> PHYSSTAT_LINK before send.It would not send anything thinking the link is
> downso I simply commented the check out.

Ok - I have looked at the ecos code and it is accessing registers which
do not exist on the AMD PCNet-II chip which I have emulated.

It is using the MII registers which only exist on the AMD PCNet-Pro chip

I wonder if ecos would behave properly on a real PCNet-II controller
which does not have a MII... 

> I see linux does not use those regs either but another method for checking
> link status, but will have to look at the spec to see what exactly.

The only way to check link status on PCNet/PCNet-II chips is via the BCR
registers - by programming and polling the LED status.

-- 
Antony T Curtis, BSc.                   UNIX, Linux, *BSD, Networking
antony.t.curtis@ntlworld.com            C++, J2EE, Perl, MySQL, Apache
                                        IT Consultancy.

      reply	other threads:[~2004-08-11 13:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11 11:20 [Qemu-devel] amd pcnet works with ecos/x86 Jani Monoses
2004-08-11 13:03 ` Antony T Curtis [this message]

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