linux-mips
[Top] [All Lists]

Re: Titan ethernet driver broken

To: TheNop <TheNop@gmx.net>
Subject: Re: Titan ethernet driver broken
From: Ralf Baechle <ralf@linux-mips.org>
Date: Sat, 20 Nov 2004 10:54:46 +0100
Cc: linux-mips@linux-mips.org
In-reply-to: <419D25A7.2090506@gmx.net>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <419D03DE.8090403@gmx.net> <419D04AA.50508@mvista.com> <419D171E.5040507@gmx.net> <419D173E.6050602@mvista.com> <419D1A2D.5000009@gmx.net> <419D1F76.6010603@gmx.net> <419D20C9.10909@mvista.com> <419D25A7.2090506@gmx.net>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4.1i
On Thu, Nov 18, 2004 at 11:43:51PM +0100, TheNop wrote:

> I use the chip version 1.1.
> Now I have the problem, that I can not use the newest code,  until 1.2 
> version of the chip is available.
> Is it possible to make the code usable for all chip version by choosing 
> the version at the kernel configuration?

Titan 1.2 is available since quite a while - the dust on my board is
proof ;-)  Since Titan 1.0 and 1.0 were shipped in very low numbers to
early customers only and will never be available in volume production the
support for them was removed.  As I recall there were at least these
problems with Titan 1.0 and 1.1 in Linux:

  - Linux uses the prefetch prepare for store operation.
  - Coherency mode 5 which is mandatory for good performance and any kind
    of sanity on SMP is now being used.
  - The problem with the third ethernet port which Manish just had
    described.

You can dig through XCVS, WebCVS or the linux-cvs archive to find where
I broke backward compatibility.

  Ralf

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