Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Michael Shmulevich <michaels@jungo.com>
To: unlisted-recipients:; (no To-header on input)
Cc: "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: MIPS/linux compatible PCI network cards
Date: Fri, 26 Jan 2001 09:56:00 +0200	[thread overview]
Message-ID: <3A712D90.3CC9EBAF@jungo.com> (raw)
In-Reply-To: 3A70A718.F0628BBB@mvista.com

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?). 

Michael Shmulevich
______________________________________
Software Developer
Jungo - R&D 
email: michaels@jungo.com
web: http://www.jungo.com
Phone: 1-877-514-0537(USA)  +972-9-8859365(Worldwide) ext. 233
Fax:   1-877-514-0538(USA)  +972-9-8859366(Worldwide)

WARNING: multiple messages have this Message-ID (diff)
From: 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: Fri, 26 Jan 2001 09:56:00 +0200	[thread overview]
Message-ID: <3A712D90.3CC9EBAF@jungo.com> (raw)
Message-ID: <20010126075600.YUM0UJfdgSOwpkx7WyXcWjHiJz1CY6sqgABhrShWL9s@z> (raw)
In-Reply-To: 3A70A718.F0628BBB@mvista.com

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?). 

Michael Shmulevich
______________________________________
Software Developer
Jungo - R&D 
email: michaels@jungo.com
web: http://www.jungo.com
Phone: 1-877-514-0537(USA)  +972-9-8859365(Worldwide) ext. 233
Fax:   1-877-514-0538(USA)  +972-9-8859366(Worldwide)

  parent reply	other threads:[~2001-01-26  7:56 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 [this message]
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
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=3A712D90.3CC9EBAF@jungo.com \
    --to=michaels@jungo.com \
    --cc=linux-mips@oss.sgi.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