linux-mips
[Top] [All Lists]

Re: RFC: au1000_etc.c phylib rewrite

To: Herbert Valerio Riedel <hvr@gnu.org>
Subject: Re: RFC: au1000_etc.c phylib rewrite
From: Mark Schank <mschank@dcbnet.com>
Date: Wed, 03 May 2006 13:01:02 -0500
Cc: linux-mips@linux-mips.org
In-reply-to: <1146674056.31241.18.camel@localhost.localdomain>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <5.1.0.14.2.20060502095256.01fd4210@205.166.54.3> <5.1.0.14.2.20060501144633.025e4e20@205.166.54.3> <1146510542.16643.10.camel@localhost.localdomain> <1146510542.16643.10.camel@localhost.localdomain> <5.1.0.14.2.20060501144633.025e4e20@205.166.54.3> <5.1.0.14.2.20060502095256.01fd4210@205.166.54.3>
Sender: linux-mips-bounce@linux-mips.org
Herbert,

btw, is the CSB655 supported at all in the 2.6 linux-mips branch, I
couldn't find any mention of it in Kconfig files either?

The CSB655 makes use of some of these seeming "unused" options, but the board specific code for the CSB655 was never submitted back to linux-mips tree. I did not develop of any of this code, so I am not sure of the reason why it was not submitted back. I received the code when I purchased a CSB655/955 developers kit and have since ported portions of it forward to the 2.6.16 branch. I am willing to submit what I have done, but I don't want to step on the original developers toes. There were also several changes I had to make to generic MIPs and Linux code, and I am not sure of the proper way to handle them in the general linux-mips tree.

-Mark



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