public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: old tulip patch
Date: Tue, 13 Jan 2004 01:09:03 +0000	[thread overview]
Message-ID: <16387.17711.667314.728494@napali.hpl.hp.com> (raw)
In-Reply-To: <200401130013.i0D0D2F6012444@napali.hpl.hp.com>

I'll drop it from my tree then and let you and Jeff figure out what to
do about it.

Thanks,

	--david

>>>>> On Mon, 12 Jan 2004 17:00:59 -0800, Grant Grundler <iod00d@hp.com> said:

  Grant> On Mon, Jan 12, 2004 at 04:13:02PM -0800, David Mosberger wrote:
  >> I'd like to remove the attached old patch from my linux-ia64-2.5 tree.
  >> If anybody thinks it's still needed, please speak up now.

  Grant> Sorry - that's my mess. Feel free to remove it.
  Grant> I expect tulip will stop working for some folks.

  Grant> Turns out that while the simple udelay() usually works, the driver
  Grant> ignores the 802.3 spec.  Newer patch is here:
  Grant> ftp://ftp.parisc-linux.org/patches/diff-tulip_phy_reset-03

  Grant> Jeff Garzik rejected this patch because it introduces a potential
  Grant> 1ms delay while holding off interrupts. I agree this is not a good
  Grant> thing. But it's better than not working.

  Grant> Jeff wanted me to avoid this by adding schedule_timeout() to the code
  Grant> path someplace. I refused since the above Works For Me and the init
  Grant> sequence in tulip is, uhm, well, "difficult". It covers too many
  Grant> different NICs for me to even begin to understand all the variations.
  Grant> I felt my patch was fairly low risk change to a "mature" product.

  Grant> I'll maintain the patch for SuSE/RHAS/Debian on ia64 and for parisc-linux.

  Grant> thanks,
  Grant> grant

  parent reply	other threads:[~2004-01-13  1:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13  0:13 old tulip patch David Mosberger
2004-01-13  1:00 ` Grant Grundler
2004-01-13  1:09 ` David Mosberger [this message]
2004-01-13  1:23 ` Grant Grundler

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=16387.17711.667314.728494@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@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