TI DaVinci git tree available
The kernel git tree[1] for the TI DaVinci platform is now available at
This kernel is currently based on 2.6.17-rc4 and will follow the mainline kernel.
This is currently a minimal kernel with only serial and ethernet support, but drivers will be added one by one as I forward port them from the 2.6.10-based MontaVista product.
Included in the tree is a default config (via 'make davinci_dm644x_defconfig') that should boot.
There are some known issues[2] as well as some areas that could use updating to the newer kernel and updates for the Linux Driver model.
Patches are welcome!
Like the OMAP site, TI is maintaining a Linux site for DaVinci at
http://linux.davincidsp.com/ Mailing-list subscription info can be found there.
Signature · 13 lines
Kevin Hilman <[email protected]> MontaVista Software, Inc. [1] For those new to git, there is an overview, tutorial and man pages available at http://www.kernel.org/git/ [2] Known issues: Something has changed in the 8250 serial driver since 2.6.10 which causes some problems on the serial console. Interrupts seem to be lost such that the driver seems to be a few characters behind what you're typing. This is still under investigation, but any help appreciated.
Quoted 1 line · Kevin Hilman
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?
Dirk
Quoted 5 lines · Dirk Behme
Quoted 1 line · Kevin Hilman
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
Quoted 16 lines · Kevin Hilman
Quoted 5 lines · Dirk Behme
Quoted 1 line · Kevin Hilman
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.
Quoted 4 lines
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/
Let's wait and see then. If we have lots of drivers to share then it makes sense to have them in the same tree. But for few drivers, let's just work them out and try to have them integrated into the mainline tree.
Quoted 3 lines
Some existing areas of overlap I can think of off the top of my head:
-
CONFIG_DEBUG_LLpatch tokernel/printk.c
Hmmm, what are you using for CONFIG_DEBUG_LL then?
Quoted 2 lines
- AIC23 code: DaVinci has AIC33 and I have a minor patch to support AIC33
Let's try to get that integrated to the mainline tree.
Quoted 3 lines
- 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.
I assume you mean this chunk?
@@ -1372,7 +1372,8 @@
DEBUG_INTR("end.\n");- return IRQ_RETVAL(handled); + //return IRQ_RETVAL(handled); + return IRQ_HANDLED; /* FIXME: iir status not ready on 1510 */
}
I'll see if things work now without that.
Regards,
Tony
Quoted 22 lines · Tony Lindgren
Quoted 16 lines · Kevin Hilman
Quoted 5 lines · Dirk Behme
Quoted 1 line · Kevin Hilman
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.
Quoted 4 lines
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/
Quoted 4 lines
Let's wait and see then. If we have lots of drivers to share then it makes sense to have them in the same tree. But for few drivers, let's just work them out and try to have them integrated into the mainline tree.
So you're leaning towards keeping the trees separate? It would
incentivize pushing things upstream. In any case, I've attached a
patch which adds core DaVinci support to todays OMAP tree. You can see that there no changes to common files (except Makefile/Kconfig) and will not affect OMAP.
Quoted 5 lines
Quoted 3 lines
Some existing areas of overlap I can think of off the top of my head:
-
CONFIG_DEBUG_LLpatch tokernel/printk.cHmmm, what are you using for
CONFIG_DEBUG_LLthen?
The change to kernel/printk.c is not in mainline, so I've borrowed the one from the OMAP tree.
Quoted 4 lines
Quoted 2 lines
- AIC23 code: DaVinci has AIC33 and I have a minor patch to support AIC33
Let's try to get that integrated to the mainline tree.
I don't think the existing aic23 code is in mainline yet, is it?
Quoted 7 lines
Quoted 3 lines
- 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.
I assume you mean this chunk?
Review line 1377
Quoted 7 lines
(quoted diff) +2
-1@@ -1372,7 +1372,8 @@ DEBUG_INTR("end.\n"); - return IRQ_RETVAL(handled); + //return IRQ_RETVAL(handled); + return IRQ_HANDLED; /* FIXME: iir status not ready on 1510 */ }
Yeah, that's what I"m referring to.
Quoted 2 lines
I'll see if things work now without that.
DaVinci doesn't seem to need it anymore.
I remembered one other driver that will be shared and that's the Mentor high-speed usb driver which is the same on 243x and DaVinci.
Kevin