netdev
[Top] [All Lists]

Re: [PATCH][2.6] de4x5 cleanup

To: Jeff Garzik <jgarzik@xxxxxxxxx>
Subject: Re: [PATCH][2.6] de4x5 cleanup
From: Marc Zyngier <mzyngier@xxxxxxxxxxx>
Date: Sat, 30 Aug 2003 23:22:02 +0200
Cc: akpm@xxxxxxxx, linux-net@xxxxxxxxxxxxxxx, Maillist netdev <netdev@xxxxxxxxxxx>
In-reply-to: <3F50F805.9090805@pobox.com> (Jeff Garzik's message of "Sat, 30 Aug 2003 15:16:21 -0400")
Organization: Metropolis -- Nowhere
References: <wrpad9r79g6.fsf@hina.wild-wind.fr.eu.org> <3F50E3FD.1000703@pobox.com> <wrpn0dr55n1.fsf@hina.wild-wind.fr.eu.org> <3F50F805.9090805@pobox.com>
Reply-to: mzyngier@xxxxxxxxxxx
Sender: netdev-bounce@xxxxxxxxxxx
>>>>> "Jeff" == Jeff Garzik <jgarzik@xxxxxxxxx> 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.

<Prev in Thread] Current Thread [Next in Thread>