[tulip] Tulip and PowerPC endian issue?

[Jim Rowe]

On Fri, 2003-01-31 at 12:21, Donald Becker wrote:
> 
> If you tried to ping, there should be more messages.  Run 'dmesg', or
> config syslog to record the "debug" level messages from the kernel:
> 
>    echo "kern.*		-/var/log/debug" >> /etc/syslog.conf

Here is the dmesg log after I try to ping with debug == 15:

Nov 30 00:02:35 eth0 kernel: pci-scan.c:v1.11 8/31/2002  Donald Becker
<becker@scyld.com> http://www.scyld.com/linux/drivers.html 
Nov 30 00:02:37 eth0 kernel: tulip.c:v0.95f 11/17/2002  Written by
Donald Becker <becker@scyld.com> 
Nov 30 00:02:37 eth0 kernel:   http://www.scyld.com/network/tulip.html 
Nov 30 00:02:37 eth0 kernel:   The PCI BIOS has not enabled the device
at 2/0!  Updating PCI command 0003->0007. 
Nov 30 00:02:37 eth0 kernel: eth1: ADMtek Centaur-C rev 17 at
0xc902f000, 00:10:7A:69:F0:79, IRQ 30. 
Nov 30 00:02:37 eth0 kernel: eth1:  MII transceiver #1 config 3100
status 7869 advertising 05e1. 
Nov 30 00:02:37 eth0 kernel:   PCI latency timer (CFLT) is unreasonably
low at 0.  Setting to 32 clocks. 
Nov 30 00:04:28 eth0 kernel: eth1: tulip_open() irq 30. 
Nov 30 00:04:28 eth0 kernel: eth1: MII link partner 45e1, negotiated
05e1. 
Nov 30 00:04:28 eth0 kernel: eth1: Setting full-duplex based on MII #1
link partner capability of 45e1. 
Nov 30 00:04:28 eth0 kernel: eth1: Done tulip_open(), CSR0 fff98000,
CSR5 fc674014 CSR6 ff972113. 
Nov 30 00:04:31 eth0 kernel: eth1: Comet link status 786d partner
capability 45e1. 
Nov 30 00:04:31 eth0 kernel: eth1: MII link partner 45e1, negotiated
05e1. 
Nov 30 00:05:31 eth0 kernel: eth1: Comet link status 786d partner
capability 45e1. 
Nov 30 00:05:31 eth0 kernel: eth1: MII link partner 45e1, negotiated
05e1. 
Nov 30 00:06:31 eth0 kernel: eth1: Comet link status 786d partner
capability 45e1. 
Nov 30 00:06:31 eth0 kernel: eth1: MII link partner 45e1, negotiated
05e1. 
Nov 30 00:07:31 eth0 kernel: eth1: Comet link status 786d partner
capability 45e1. 
Nov 30 00:07:31 eth0 kernel: eth1: MII link partner 45e1, negotiated
05e1. 
Nov 30 00:08:31 eth0 kernel: eth1: Comet link status 786d partner
capability 45e1. 
Nov 30 00:08:31 eth0 kernel: eth1: MII link partner 45e1, negotiated
05e1.


And here is the output of mii-diag -v. Everything seems to be ok? :

root@eth0:/usr/src/netdrivers# ./mii-diag -v eth1
mii-diag.c:v2.07 11/15/2002 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
  Using the new SIOCGMIIPHY value on PHY 1 (BMCR 0x1100).
 The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
 Basic mode control register 0x1100: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
   This transceiver is capable of  100baseTx-FD 100baseTx 10baseT-FD
10baseT.
   Able to perform Auto-negotiation, negotiation complete.
 Your link partner advertised 45e1: Flow-control 100baseTx-FD 100baseTx
10baseT-FD 10baseT, w/ 802.3X flow control.
   End of basic transceiver information.

 MII PHY #1 transceiver registers:
   1100 786d 001d 2411 05e1 45e1 0007 2001
   0000 0000 0000 0000 0000 0000 0000 0000
   1001 0000 20a7 0319 0000 0000 7490 0f0c
   ae8f 7514 2e5d 1428 8911 0444 0230 0000.
 Basic mode control register 0x1100: Auto-negotiation enabled.
 Basic mode status register 0x786d ... 786d.
   Link status: established.
   Capable of  100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation complete.
 Vendor ID is 00:07:49:--:--:--, model 1 rev. 1.
   No specific information is known about this transceiver type.
 I'm advertising 05e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD
10baseT
   Advertising no additional info pages.
   IEEE 802.3 CSMA/CD protocol.
 Link partner capability is 45e1: Flow-control 100baseTx-FD 100baseTx
10baseT-FD 10baseT.
   Negotiation  completed.


-- 
Jim Rowe
Advanced CounterMeasure Systems
Email: jrowe@acmsystems.com