From: Pete Popov <ppopov@mvista.com>
To: Michael Shmulevich <michaels@jungo.com>
Cc: no To-header on input <"unlisted-recipients:;"@hermes.mvista.com>,
"linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: MIPS/linux compatible PCI network cards
Date: Fri, 26 Jan 2001 10:17:27 -0800 [thread overview]
Message-ID: <3A71BF37.7DBE8234@mvista.com> (raw)
In-Reply-To: 3A712D90.3CC9EBAF@jungo.com
Michael Shmulevich wrote:
>
> Pete Popov wrote:
> >
> >
> > Another one is the RTL8139. It's quite cheap (I think less than $20).
> >
> > Pete
>
> Surprisingly enough, Realtek's driver is quite x86-oriented. It uses
> some ugly outb() functtions without any ioremap()'ping.
> We tried to modify it to work for MIPS, but failed. There are some
> hard-to-detect situations, when driver just cannot talk to the hardware,
> probably due to transmit/receive buffer synchronization. But after some
> period the connection is restored (reset?).
The 8139 driver (at least the latest one) has an "ifdef" option to use
I/O or memory mapping. I've tried both and both work fine without any
modifications. The I/O works fine, provided that you've set things up
correctly.
The inb()/outb() functions are part of just about every driver,
unfortunately. I really don't like this x86 emulation, but if you want
to be able to use drivers without having to modify every one of them,
you'll have to do this.
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
next prev parent reply other threads:[~2001-01-26 18:17 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 [this message]
2001-01-27 8:58 ` Michael Shmulevich
2001-01-27 21:31 ` Pete Popov
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=3A71BF37.7DBE8234@mvista.com \
--to=ppopov@mvista.com \
--cc="unlisted-recipients:;"@hermes.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox