public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Dodd <ted@cypress.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS in 2.4.8/9ac
Date: Thu, 30 Aug 2001 16:19:22 -0500	[thread overview]
Message-ID: <3B8EADDA.8070803@cypress.com> (raw)
In-Reply-To: <E15cZ3Y-0001qB-00@the-village.bc.nu>



Alan Cox wrote:
>>2.4.7-ac10 worked fine.2.4.8-ac8 through 2.4.9-ac3
>>have trouble. I have not tested 2.4.8-ac[1..7] yet.
>>
> 
> Ok can you transplant drivers/net/tulip from a working -ac into the
> current tree and see if that fixes it - that tells us if its a network
> driver bug or a kernel core bug.
this is the only diff I find in the tulip directory.
(2.4.8 and 2.4.9 have no diff)

--- linux-2.4.7-ac10/drivers/net/tulip/tulip_core.c
+++ linux-2.4.9-ac3/drivers/net/tulip/tulip_core.c
@@ -1409,6 +1409,10 @@
         if (chip_idx == LC82C168)
                 csr0 &= ~0xfff10000; /* zero reserved bits 31:20, 16 */

+       /* DM9102A has troubles with MRM, clear bit 24 too. */
+       if (pdev->vendor == 0x1282 && pdev->device == 0x9102)
+               csr0 &= ~0x01200000;
+
         /*
          *      And back to business
          */
@@ -1751,9 +1755,9 @@
                 kfree (tp->mtable);
  #ifndef USE_IO_OPS
         iounmap((void *)ioaddr);
-#endif

  err_out_free_res:
+#endif
         pci_release_regions (pdev);

  err_out_free_netdev:

---------
the second hunk could be a problem.
I'll try moving the endif back tomorrow.

	-Thomas



  reply	other threads:[~2001-08-30 21:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-30 21:00 NFS in 2.4.8/9ac Thomas Dodd
2001-08-30 21:08 ` Alan Cox
2001-08-30 21:19   ` Thomas Dodd [this message]
2001-09-19 21:12 ` Thomas Dodd
2001-09-19 22:06   ` Alan Cox

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=3B8EADDA.8070803@cypress.com \
    --to=ted@cypress.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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