From: Ralf Baechle <ralf@linux-mips.org>
To: TheNop <TheNop@gmx.net>
Cc: linux-mips@linux-mips.org
Subject: Re: Titan ethernet driver broken
Date: Sat, 20 Nov 2004 10:54:46 +0100 [thread overview]
Message-ID: <20041120095445.GA12870@linux-mips.org> (raw)
In-Reply-To: <419D25A7.2090506@gmx.net>
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
next prev parent reply other threads:[~2004-11-20 9:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 20:19 Titan ethernet driver broken TheNop
2004-11-18 20:23 ` Manish Lachwani
2004-11-18 21:41 ` TheNop
2004-11-18 21:42 ` Manish Lachwani
2004-11-18 21:54 ` TheNop
2004-11-18 22:17 ` TheNop
2004-11-18 22:23 ` Manish Lachwani
2004-11-18 22:43 ` TheNop
2004-11-18 23:43 ` Manish Lachwani
2004-11-20 9:54 ` Ralf Baechle [this message]
2004-11-21 7:26 ` Manish Lachwani
2004-11-19 17:32 ` Manish Lachwani
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=20041120095445.GA12870@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=TheNop@gmx.net \
--cc=linux-mips@linux-mips.org \
/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.