From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: omap1710 upstream ? Date: Thu, 18 May 2006 00:32:03 -0700 Message-ID: <20060518073202.GB4013@atomide.com> References: <1147890163.13483.6.camel@dwalker1.mvista.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1147890163.13483.6.camel@dwalker1.mvista.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-omap-open-source-bounces@linux.omap.com Errors-To: linux-omap-open-source-bounces@linux.omap.com To: Daniel Walker Cc: linux-omap-open-source@linux.omap.com List-Id: linux-omap@vger.kernel.org * Daniel Walker [060517 11:22]: > > I was wondering if there was any time frame when omap1710 might be > going upstream ? Is there still work that needs to be done to make it > acceptable , or is it just not a top priority ? In our tree omap1710 is mostly same as omap16xx. There are only few places where we need to check for omap1710 vs omap16xx. Most of the core omap code is in sync with mainline tree. Many device drivers are not integrated yet. Regards, Tony