public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
* omap1710 upstream ?
@ 2006-05-17 18:22 Daniel Walker
  2006-05-18  7:32 ` Tony Lindgren
  0 siblings, 1 reply; 3+ messages in thread
From: Daniel Walker @ 2006-05-17 18:22 UTC (permalink / raw)
  To: tony; +Cc: linux-omap-open-source


	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 ?

Daniel

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: omap1710 upstream ?
  2006-05-17 18:22 omap1710 upstream ? Daniel Walker
@ 2006-05-18  7:32 ` Tony Lindgren
  2006-05-18 13:34   ` Daniel Walker
  0 siblings, 1 reply; 3+ messages in thread
From: Tony Lindgren @ 2006-05-18  7:32 UTC (permalink / raw)
  To: Daniel Walker; +Cc: linux-omap-open-source

* Daniel Walker <dwalker@mvista.com> [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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: omap1710 upstream ?
  2006-05-18  7:32 ` Tony Lindgren
@ 2006-05-18 13:34   ` Daniel Walker
  0 siblings, 0 replies; 3+ messages in thread
From: Daniel Walker @ 2006-05-18 13:34 UTC (permalink / raw)
  To: Tony Lindgren; +Cc: linux-omap-open-source

On Thu, 2006-05-18 at 00:32 -0700, Tony Lindgren wrote:
> * Daniel Walker <dwalker@mvista.com> [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.

The one thing I notice that's missing is the defconfig . The only
upstream defconfig is 1610 .

Daniel

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2006-05-18 13:34 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-05-17 18:22 omap1710 upstream ? Daniel Walker
2006-05-18  7:32 ` Tony Lindgren
2006-05-18 13:34   ` Daniel Walker

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox