| To: | mzyngier@xxxxxxxxxxx |
|---|---|
| Subject: | Re: [PATCH][2.6] de4x5 cleanup |
| From: | Jeff Garzik <jgarzik@xxxxxxxxx> |
| Date: | Sat, 30 Aug 2003 15:16:21 -0400 |
| Cc: | akpm@xxxxxxxx, linux-net@xxxxxxxxxxxxxxx, Maillist netdev <netdev@xxxxxxxxxxx> |
| In-reply-to: | <wrpn0dr55n1.fsf@hina.wild-wind.fr.eu.org> |
| Organization: | none |
| References: | <wrpad9r79g6.fsf@hina.wild-wind.fr.eu.org> <3F50E3FD.1000703@pobox.com> <wrpn0dr55n1.fsf@hina.wild-wind.fr.eu.org> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021213 Debian/1.2.1-2.bunk |
Marc Zyngier wrote:
"Jeff" == Jeff Garzik <jgarzik@xxxxxxxxx> writes: 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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Bonding-devel] Re: [bonding][2/3] Synchronizing 2.4-2.6, Ben Greear |
|---|---|
| Next by Date: | Re: [PATCH][2.6] de4x5 cleanup, Marc Zyngier |
| Previous by Thread: | Re: [PATCH][2.6] de4x5 cleanup, Marc Zyngier |
| Next by Thread: | Re: [PATCH][2.6] de4x5 cleanup, Marc Zyngier |
| Indexes: | [Date] [Thread] [Top] [All Lists] |