All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: mzyngier@freesurf.fr
Cc: akpm@osdl.org, linux-net@vger.kernel.org,
	Maillist netdev <netdev@oss.sgi.com>
Subject: Re: [PATCH][2.6] de4x5 cleanup
Date: Sat, 30 Aug 2003 15:16:21 -0400	[thread overview]
Message-ID: <3F50F805.9090805@pobox.com> (raw)
In-Reply-To: <wrpn0dr55n1.fsf@hina.wild-wind.fr.eu.org>

Marc Zyngier wrote:
>>>>>>"Jeff" == Jeff Garzik <jgarzik@pobox.com> writes:
> 
> 
> Jeff> It looks pretty good.  My big objection isn't the Space.c stuff
> Jeff> but de4x5 itself.  I had hoped it would be gone by now :) Oh
> Jeff> well, not your fault.
> 
> Well... I too, had hoped the tulip (and its dc21040 derivative)
> driver would be the only one. While it works nicely on modern stuff
> (2114[023]), it has some problems on a few of my test boxes (mostly
> Alphas with onboard 21040).

Well, 2.6 tulip intentionally doesn't work at all on 21040 and 21041 :) 
  That's what de2104x driver is for.  Can you give that a beating, and 
verify that it works for you?

I know that 2114x chips with sym phys still have some issues; jamal has 
created a patch that fixes that (mostly updates tulip with the latest 
Becker phy code from Donald's tulip.c), which in turn fixes some 2114x 
issues on alpha.


> And most of all, tulip doesn't support EISA :-).

If it meant I could kill de4x5, then I would be all for adding EISA 
support to tulip... :)

	Jeff




  reply	other threads:[~2003-08-30 19:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <wrpad9r79g6.fsf@hina.wild-wind.fr.eu.org>
2003-08-30 17:50 ` [PATCH][2.6] de4x5 cleanup Jeff Garzik
2003-08-30 19:04   ` Marc Zyngier
2003-08-30 19:16     ` Jeff Garzik [this message]
2003-08-30 21:22       ` Marc Zyngier
2003-08-31  9:31       ` de2104x (was Re: [PATCH][2.6] de4x5 cleanup) Marc Zyngier

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=3F50F805.9090805@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@osdl.org \
    --cc=linux-net@vger.kernel.org \
    --cc=mzyngier@freesurf.fr \
    --cc=netdev@oss.sgi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.