From: Manish Lachwani <mlachwani@mvista.com>
To: TheNop <TheNop@gmx.net>,
Linux/MIPS Development <linux-mips@linux-mips.org>
Subject: Re: Titan ethernet driver broken
Date: Thu, 18 Nov 2004 15:43:40 -0800 [thread overview]
Message-ID: <419D33AC.8090307@mvista.com> (raw)
In-Reply-To: <419D25A7.2090506@gmx.net>
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
>
next prev parent reply other threads:[~2004-11-18 23:43 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 [this message]
2004-11-20 9:54 ` Ralf Baechle
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=419D33AC.8090307@mvista.com \
--to=mlachwani@mvista.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox