public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Gifford <maillist@jg555.com>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	jgarzik@pobox.com, pdh@colonel-panic.org
Subject: Re: 64bit build of tulip driver
Date: Thu, 31 Mar 2005 19:52:06 -0800	[thread overview]
Message-ID: <424CC566.3080007@jg555.com> (raw)
In-Reply-To: <20050331161206.GB19219@colo.lackof.org>

Grant
    Thanx for your feedback. I got it working, but I don't think the 
patch is the best. Here is the patch, and the information, but if you 
can recommend a different way to fix it, let me know. The patch was done 
by Peter Horton.
Here is the link to the full patch, 
http://ftp.jg555.com/patches/raq2/linux/linux-2.6.11.6-raq2_fix-2.patch
but here is the section for this issue
@@ -1628,6 +1631,16 @@
                 }
         }
 
+#if defined(CONFIG_MIPS_COBALT) && defined(CONFIG_MIPS64)
+        /*
+         * something very bad is happening. without this
+         * cache flush the PHY can't be read. I've tried
+         * various ins & outs, delays etc but only a call
+         * to printk or this flush seems to fix it ... help!
+         */
+        flush_cache_all();
+#endif
+
         /* Find the connected MII xcvrs.
            Doing this in open() would allow detecting external xcvrs
            later, but takes much time. */

>Are there any config option differences? 
>e.g. MWI or MMIO options enabled on 64-bit but not 32-bit?
>  
>
I verified that there are no differences.

>ISTR to remember submitting a patch so additional data
>gets printed in tulip_stop_rxtx. Here is a reference to the patch
>but I don't think it is relevant to the this problem:
>	http://lkml.org/lkml/2004/12/15/119
>
>  
>
Applied the patch, here is the output

0000:00:07.0: tulip_stop_rxtx() failed (CSR5 0xf0660000 CSR6 0xb3862002)
0000:00:07.0: tulip_stop_rxtx() failed (CSR5 0xf0660000 CSR6 0xb3862002)
0000:00:07.0: tulip_stop_rxtx() failed (CSR5 0xf0660000 CSR6 0xb3862002)
0000:00:07.0: tulip_stop_rxtx() failed (CSR5 0xf0660000 CSR6 0xb3862002)
0000:00:07.0: tulip_stop_rxtx() failed (CSR5 0xf0660000 CSR6 0xb3862002)
0000:00:07.0: tulip_stop_rxtx() failed (CSR5 0xf0660000 CSR6 0xb3862002)
0000:00:07.0: tulip_stop_rxtx() failed (CSR5 0xf0660000 CSR6 0xb3862002)
0000:00:07.0: tulip_stop_rxtx() failed (CSR5 0xf0660000 CSR6 0xb3862002)

I was able to get some more information on the bootup sequence with the 
updates.
Here is the output now from the driver

Linux Tulip driver version 1.1.13 (May 11, 2002)
PCI: Enabling device 0000:00:07.0 (0045 -> 0047)
tulip0: Old format EEPROM on 'Cobalt Microserver' board.  Using 
substitute media control info.
tulip0:  EEPROM default media type Autosense.
tulip0:  Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block.
tulip0: ***WARNING***: No MII transceiver found!
eth0: Digital DS21143 Tulip rev 65 at ffffffffb0001400, 
00:10:E0:00:32:DE, IRQ 19.
PCI: Enabling device 0000:00:0c.0 (0005 -> 0007)
tulip1: Old format EEPROM on 'Cobalt Microserver' board.  Using 
substitute media control info.
tulip1:  EEPROM default media type Autosense.
tulip1:  Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block.
tulip1: ***WARNING***: No MII transceiver found!
eth1: Digital DS21143 Tulip rev 65 at ffffffffb0001480, 
00:10:E0:00:32:DF, IRQ 20.


-- 
----
Jim Gifford
maillist@jg555.com


  reply	other threads:[~2005-04-01  3:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-30 18:03 64bit build of tulip driver Jim Gifford
2005-03-31 16:12 ` Grant Grundler
2005-04-01  3:52   ` Jim Gifford [this message]
2005-04-01  6:51     ` Grant Grundler
     [not found]       ` <424D7AE9.5050100@jg555.com>
2005-04-01 18:26         ` Grant Grundler
2005-04-01 20:23           ` Jim Gifford
2005-04-01 22:11             ` Grant Grundler
2005-04-02  4:38           ` Jim Gifford

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=424CC566.3080007@jg555.com \
    --to=maillist@jg555.com \
    --cc=grundler@parisc-linux.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pdh@colonel-panic.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