mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin Eriksson" <nitrax@giron.wox.org>
To: "Urban Widmark" <urban@teststation.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: via-rhine and MMIO
Date: Mon, 29 Oct 2001 21:11:27 +0100	[thread overview]
Message-ID: <009e01c160b5$e48038c0$0201a8c0@HOMER> (raw)
In-Reply-To: <Pine.LNX.4.30.0110291847420.21339-100000@cola.teststation.com>

----- Original Message -----
From: "Urban Widmark" <urban@teststation.com>
To: "Martin Eriksson" <nitrax@giron.wox.org>
Cc: <linux-kernel@vger.kernel.org>
Sent: Monday, October 29, 2001 7:13 PM
Subject: Re: via-rhine and MMIO


> On Mon, 29 Oct 2001, Martin Eriksson wrote:
>
> > I have done some changes to the via-rhine driver in 2.4.13 to be able to
run
> > with MMIO. I know it isn't really needed but I do it mainly for fun &
> > learning.
>
> Any measurable performance difference?

I don't think so, it would be slightly less latency, but as via-rhine needs
to copy the data anyway...

>
> Any important changes from the driver that used to be on
>     http://www.cs.umu.se/~c97men/linux ?
> (I have a copy of "v1.03a ME1.0 3/12/00")

Yes _I_ have matured a bit =) And the new driver does not choose between
MMIO/PORTIO at runtime, because most other drivers seem to select this via
CONFIG_ directives.

>
>
> > /* Reload the station address from the EEPROM. */
> > writeb(0x20, ioaddr + MACRegEEcsr);
> > /* Typically 2 cycles to reload. */
> > for (i = 0; i < 150; i++)
> >     if (! (readb(ioaddr + MACRegEEcsr) & 0x20))
> >         break;
> > ...
> >
> > If I run this code when I'm using MMIO, I get a hardware adress of
> > "ff:ff:ff:ff:ff:ff" instead of the right one (and everything craps up).
But
> > when I comment out this part all is fine. So what's it needed for
anyway?
>
> It is needed on some cards when rebooting from some other OSes that power
> down the card (eg vt6102 chips on win98). The writeb causes the chip
> itself to reload the hardware address from eeprom. Perhaps it no longer
> finds the eeprom and just reads 0xff from some unmapped memory space.
>
> Does it work to enable MMIO after the reset code?

I'll check that out, and if all works fine I'll release a patch. By the way,
how *do* you measure network performance the best way? What I have done now
is only to stress test the driver, by copying a 400MB file from my Windows
machine to /dev/null and at the same time recieving a 400MB file over FTP
from my Sun Sparc which is bridged on another via-rhine.

_____________________________________________________
|  Martin Eriksson <nitrax@giron.wox.org>
|  MSc CSE student, department of Computing Science
|  Umeå University, Sweden



  reply	other threads:[~2001-10-29 20:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-29 13:06 Martin Eriksson
2001-10-29 18:13 ` Urban Widmark
2001-10-29 20:11   ` Martin Eriksson [this message]
2001-10-29 21:22     ` Urban Widmark
2001-10-29 21:36   ` Experimental via-rhine.c, mmio enabled Martin Eriksson
2001-10-30  9:12 ` via-rhine and MMIO Jeff Garzik
2001-11-03 15:55   ` [patch] " Urban Widmark

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='009e01c160b5$e48038c0$0201a8c0@HOMER' \
    --to=nitrax@giron.wox.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=urban@teststation.com \
    /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

Powered by JetHome