From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Thu, 18 Nov 2004 23:43:47 +0000 (GMT) Received: from gateway-1237.mvista.com ([IPv6:::ffff:12.44.186.158]:65006 "EHLO hermes.mvista.com") by linux-mips.org with ESMTP id ; Thu, 18 Nov 2004 23:43:42 +0000 Received: from mvista.com (prometheus.mvista.com [10.0.0.139]) by hermes.mvista.com (Postfix) with ESMTP id 9695118608; Thu, 18 Nov 2004 15:43:40 -0800 (PST) Message-ID: <419D33AC.8090307@mvista.com> Date: Thu, 18 Nov 2004 15:43:40 -0800 From: Manish Lachwani User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.2) Gecko/20040308 X-Accept-Language: en-us, en MIME-Version: 1.0 To: TheNop , Linux/MIPS Development Subject: Re: Titan ethernet driver broken 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> In-Reply-To: <419D25A7.2090506@gmx.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 6366 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: mlachwani@mvista.com Precedence: bulk X-list: linux-mips Well, you dont need to configure kernel based on the chip revision. You can determine the chip revision (on bootup) by reading the processor id (PRID) and the CPU Mask register. Then, check the version number in the driver and do the copy (for IP header alignment) if the version is 1.0 or 1.1 Thanks Manish Lachwani TheNop wrote: > Manish Lachwani wrote: > >> Hello ! >> >> Thanks for sending this. I have one question regarding the Yosemite >> board that you have. What is the version of the Titan chip on the >> board? Is it 1.0, 1.1 or 1.2? >> >> This is because 1.0 and 1.1 have a problem where the IP header is not >> aligned on the Rx side. As a result, there was an extra copy involved >> in the driver, i.e. titan_ge_slowpath. The latest version of the >> driver only support Titan chip revision 1.2 in which this problem is >> fixed >> >> Thanks >> Manish Lachwani >> >> >> > 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? > > Best regards > TheNop >