From: Kevin Hilman <khilman@mvista.com>
To: Dirk Behme <dirk.behme@googlemail.com>
Cc: "linux-omap-open-source@linux.omap.com"
<linux-omap-open-source@linux.omap.com>
Subject: Re: [ANNOUNCE] TI DaVinci git tree available
Date: Wed, 17 May 2006 09:58:54 -0700 [thread overview]
Message-ID: <1147885134.8739.70.camel@vence.internal.net> (raw)
In-Reply-To: <446B44B9.2000900@gmail.com>
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
next prev parent reply other threads:[~2006-05-17 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 0:43 [ANNOUNCE] TI DaVinci git tree available Kevin Hilman
2006-05-17 15:43 ` Dirk Behme
2006-05-17 16:58 ` Kevin Hilman [this message]
2006-05-26 23:21 ` Tony Lindgren
2006-05-27 0:19 ` Kevin Hilman
-- strict thread matches above, loose matches on Subject: below --
2006-05-27 13:59 Woodruff, Richard
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=1147885134.8739.70.camel@vence.internal.net \
--to=khilman@mvista.com \
--cc=dirk.behme@googlemail.com \
--cc=linux-omap-open-source@linux.omap.com \
/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