From: Marc Zyngier <mzyngier@freesurf.fr>
To: Jeff Garzik <jgarzik@pobox.com>
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 23:22:02 +0200 [thread overview]
Message-ID: <wrphe3y6dtx.fsf@hina.wild-wind.fr.eu.org> (raw)
In-Reply-To: <3F50F805.9090805@pobox.com> (Jeff Garzik's message of "Sat, 30 Aug 2003 15:16:21 -0400")
>>>>> "Jeff" == Jeff Garzik <jgarzik@pobox.com> writes:
Jeff> Well, 2.6 tulip intentionally doesn't work at all on 21040 and
Jeff> 21041 :) That's what de2104x driver is for. Can you give that a
Jeff> beating, and verify that it works for you?
Last time I checked, I had ugly Oopses on one of my alpha boxes
(AS-255), but that whas a few month ago, and I had other stuff to fix
at the moment. I'll give it a go tomorrow.
Jeff> If it meant I could kill de4x5, then I would be all for adding
Jeff> EISA support to tulip... :)
I'm afraid this would introduce a lot of the ugly crap that is
currently in de4x5 (21040 is seen through an EISA to PCI bridge, with
a sparse mapping)... I'll have a look at what we can do without
introduce too many hacks.
If de2104x behaves correctly, another solution would be to turn de4x5
to be EISA only. That would be a good way to finally kill it ;-).
Thanks,
M.
--
Places change, faces change. Life is so very strange.
next prev parent reply other threads:[~2003-08-30 21:22 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
2003-08-30 21:22 ` Marc Zyngier [this message]
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=wrphe3y6dtx.fsf@hina.wild-wind.fr.eu.org \
--to=mzyngier@freesurf.fr \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-net@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).