mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Albert D. Cahalan" <acahalan@cs.uml.edu>
To: linux-kernel@vger.kernel.org
Subject: tulip driver problem
Date: Mon, 6 Aug 2001 12:19:10 -0400 (EDT)	[thread overview]
Message-ID: <200108061619.f76GJAA99461@saturn.cs.uml.edu> (raw)


The tulip driver in 2.4.8-pre3 does not work.
The tulip driver version 0.9.14 from sourceforge does not work.
The tulip driver in 2.2.14 is OK.
The de4x5 driver does not work.
I think I had the driver in 2.4.3 working at one point.

The error I'm getting from the 0.9.14 driver:
NETDEV WATCHDOG: eth0: transmit timed out

This is the Force PowerCore 6750 single-board computer with
a PowerPC processor and the DEC 21143 Ethernet chip.

Booting 2.2.14 shows:

POSIX conformance testing by UNIFIX
PCI: Probing PCI hardware
remapping IO (0x10e3:0x0 BAR 0): 0xbff001 -> 0xbff000
remapping MEM(0x10e3:0x0 BAR 1): fcfff000 -> 0xfcfff000
remapping IO (0x1011:0x19 BAR 0): 0xbfef81 -> 0xbfef80
remapping MEM(0x1011:0x19 BAR 1): fcffec00 -> 0xfcffec00
Linux NET4.0 for Linux 2.2
...
RAM disk driver initialized:  16 RAM disks of 4096K size
tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov
eth0: Digital DS21143 Tulip rev 65 at 0xbfef80, 00:80:42:0E:CF:E8, IRQ 9.
eth0:  EEPROM default media type Autosense.
eth0:  Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block.
eth0:  Index #1 - Media AUI (#2) described by a 21142 Serial PHY (2) block.
eth0:  MII transceiver #1 config 1000 status 782d advertising 00a1.
Looking up port of RPC 100003/2 on 172.16.101.112
Looking up port of RPC 100005/1 on 172.16.101.112
VFS: Mounted root (NFS filesystem).
Freeing unused kernel memory: 68k init 32k prep 8k pmac 12k open firmware

The firmware (which likes the Ethernet just fine) reports the
host bridge and Ethernet as:

Probing PCIbus at 0x80000000
Device ID = 0x0002; Vendor ID = 0x1057; 
Status    = 0x0080; Command   = 0x0146; 
Base Class= 0x06;   Sub Class = 0x00;   Prg. Inter= 0x00;   Rev. ID   = 0x40; 
BIST      = 0x00;   Header Typ= 0x00;   Latency Ti= 0x00;   Cache Line= 0x08; 
base addr0= 0x00000000, base addr1= 0x00000000; 
Max Lat   = 0x00;   Min Gnt   = 0x00;   IRQ Pin   = 0x00;   IRQ Line  = 0x00; 
Found PCI device: Motorola MPC106 PowerPC PCI bridge

Probing PCIbus at 0x8000D800
Device ID = 0x0019; Vendor ID = 0x1011; 
Status    = 0x0280; Command   = 0x0005; 
Base Class= 0x02;   Sub Class = 0x00;   Prg. Inter= 0x00;   Rev. ID   = 0x41; 
BIST      = 0x00;   Header Typ= 0x00;   Latency Ti= 0x20;   Cache Line= 0x00; 
base addr0= 0x00850001, base addr1= 0x00000000; 
Max Lat   = 0x28;   Min Gnt   = 0x14;   IRQ Pin   = 0x01;   IRQ Line  = 0xFF; 
Found PCI device: DEC 21143 PCI/Cardbus Ethernet LAN

When using lspci I get:

00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40)
        Flags: bus master, fast devsel, latency 0

00:1b.0 Ethernet controller: Digital Equipment Corporation DECchip 21142/43 (rev 41)
        Flags: bus master, medium devsel, latency 32, IRQ 9
        I/O ports at bfef80
        Memory at fcffec00 (32-bit, non-prefetchable)
        Expansion ROM at b7fc0000 [disabled]

             reply	other threads:[~2001-08-06 16:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-06 16:19 Albert D. Cahalan [this message]
2001-08-06 17:03 ` Tom Rini
2001-08-06 20:16   ` Albert D. Cahalan
2001-08-07 10:44     ` Lech Szychowski
2001-08-07 14:59       ` Colonel
2001-08-06 16:35 chen, xiangping
2001-08-07  2:32 Colonel
2001-08-07  3:44 ` Tom Rini

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=200108061619.f76GJAA99461@saturn.cs.uml.edu \
    --to=acahalan@cs.uml.edu \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®