From: Pete Popov <ppopov@mvista.com>
To: Michael Shmulevich <michaels@jungo.com>
Cc: "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: MIPS/linux compatible PCI network cards
Date: Sat, 27 Jan 2001 13:31:44 -0800 [thread overview]
Message-ID: <3A733E40.9B1F02DD@mvista.com> (raw)
In-Reply-To: 3A728DCE.33C2CE8A@jungo.com
Michael Shmulevich wrote:
>
> Pete Popov wrote:
>
> > To get the realtek driver to work, all you need to do is to set
> > mips_io_port_base to KSEG1. Let's assume that the ethernet card has
> > been assigned i/o space at 0x14000000. The driver will pick that up as
> > the ioaddr and use the 0x1400000 as the "port". The inb()/outb() macros
> > add mips_io_port_base to the "port" value and now you have 0xB4000000,
> > so you can access the card.
> >
> > Pete
>
> The KSEG1() is indeed what I did, however the driver, as I tried to
> describe, starts to loose synchronization on buffer at some point and
> just waits quietly... Even with all the DEBUG and mental effort switched
> on I can't get the reason why this happens...
>
> By the way, which version of the driver are you talking about? Mine
> doesn't have any ifdef on anything... besides MODULE of course:-)
>
> Mine is:
>
> static const char *version =
> "rtl8139.c:v1.07 5/6/99 Donald Becker
> http://cesdis.gsfc.nasa.gov/linux/drivers/"
Hmmm, the above looks like the header for the 8129 driver, except that
it says rtl8139. Make sure you're using drivers/net/8139too.c I see
this in the driver: #define RTL8139_VERSION "0.9.10". I'm using test9
kernel, I doubt that you're driver is out of date -- it seems you're
perhaps using the wrong driver.
Regarding the I/O vs MEM accesses, look for this:
/* define to 1 to enable PIO instead of MMIO */
#undef USE_IO_OPS
Pete
next prev parent reply other threads:[~2001-01-27 21:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 22:06 MIPS/linux compatible PCI network cards Michael Shmulevich
2001-01-25 22:16 ` Ralf Baechle
2001-01-26 7:42 ` Carsten Langgaard
2001-01-26 7:43 ` Ralf Baechle
2001-01-26 11:45 ` Kevin D. Kissell
2001-01-26 11:45 ` Kevin D. Kissell
2001-01-26 11:47 ` Carsten Langgaard
2001-01-26 11:49 ` Carsten Langgaard
2001-01-26 21:00 ` Ralf Baechle
2001-01-26 21:00 ` Ralf Baechle
2001-01-25 22:22 ` Pete Popov
2001-01-25 22:29 ` Ralf Baechle
2001-01-26 7:56 ` Michael Shmulevich
2001-01-26 7:56 ` Michael Shmulevich
2001-01-26 18:17 ` Pete Popov
2001-01-27 8:58 ` Michael Shmulevich
2001-01-27 21:31 ` Pete Popov [this message]
2001-01-28 10:20 ` Michael Shmulevich
2001-01-27 19:22 ` Ralf Baechle
2001-01-28 10:11 ` Michael Shmulevich
2001-01-26 19:53 ` Jun Sun
2001-01-27 19:25 ` Ralf Baechle
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=3A733E40.9B1F02DD@mvista.com \
--to=ppopov@mvista.com \
--cc=linux-mips@oss.sgi.com \
--cc=michaels@jungo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.