From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: [ANNOUNCE] TI DaVinci git tree available Date: Wed, 17 May 2006 09:58:54 -0700 Message-ID: <1147885134.8739.70.camel@vence.internal.net> References: <1147826617.8739.32.camel@vence.internal.net> <446B44B9.2000900@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <446B44B9.2000900@gmail.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: Dirk Behme Cc: "linux-omap-open-source@linux.omap.com" List-Id: linux-omap@vger.kernel.org On Wed, 2006-05-17 at 17:43 +0200, Dirk Behme wrote: > Kevin Hilman wrote: > > The kernel git tree[1] for the TI DaVinci platform is now available > > What are the pros and cons for having one tree vs. two trees > for OMAP1 & OMAP2 (& OMAP3?) & DaVinci in the long term? It may be a good idea long term, in fact I almost released this tree as a branch of the OMAP tree instead of Linus' tree. As I thought about it though, there's very little shared code between the two trees, so I assumed it would be more of a burden on the OMAP community. So in the end, I decided to wait and see what type of development community sprouts up around DaVinci and go from there. If the OMAP community is interested in absorbing the DaVinci support, I think long-term maintenance would be easier. I'm not fixed on one way or the other, and could easily be pursuaded to rebase the DaVinci tree. For kicks, I rebased locally, and there's a patch adding DaVinci support to todays OMAP tree available here: http://source.mvista.com/~khilman/davinci/ Some existing areas of overlap I can think of off the top of my head: - CONFIG_DEBUG_LL patch to kernel/printk.c - AIC23 code: DaVinci has AIC33 and I have a minor patch to support AIC33 - There's also hack to the 8250.c serial ISR that used to be needed but is no longer needed on DaVinci. It seems some mainline fixes have removed the need for that. I'm curious if it's still necessary on OMAP. Kevin