Applications Processors Crossreference
From Texas Instruments Embedded Processors Wiki
Translate this page to
This page is specifically intended to answer questions from the Linux kernel developer community regarding where kernel patches for various TI SoC should be submitted.
| Device | Brand | Superset device | Mach folder | Treated as | Features | Public source | Mailing list |
|---|---|---|---|---|---|---|---|
| OMAP3530 | OMAP | OMAP3530 | omap2 | OMAP3 | ARM Cortex-A8, L2CACHE, ISP, NEON, SGX, IVA | linux-omap | linux-omap |
| OMAP3525 | OMAP | OMAP3530 | omap2 | OMAP3 | ARM Cortex-A8, L2CACHE, ISP, NEON, IVA | linux-omap | linux-omap |
| OMAP3515 | OMAP | OMAP3530 | omap2 | OMAP3 | ARM Cortex-A8, L2CACHE, ISP, NEON, SGX | linux-omap | linux-omap |
| OMAP3503 | OMAP | OMAP3530 | omap2 | OMAP3 | ARM Cortex-A8, L2CACHE, ISP, NEON | linux-omap | linux-omap |
| AM3517 | Sitara | AM3517 | omap2 | OMAP3 | ARM Cortex-A8, L2CACHE, ISP, NEON, SGX | linux-omap | linux-omap |
| AM3505 | Sitara | AM3517 | omap2 | OMAP3 | ARM Cortex-A8, L2CACHE, ISP, NEON | linux-omap | linux-omap |
| OMAP-L138 | OMAP | OMAP-L138 | davinci | DA8XX | ARM9, C674x | linux-davinci | davinci-linux |
| OMAP-L137 | OMAP | OMAP-L137 | davinci | DA8XX | ARM9, C674x | linux-davinci | davinci-linux |
| DM365 | DaVinci | DM365 | davinci | DAVINCI | ARM9 | linux-davinci | davinci-linux |
| DM357 | DaVinci | DM6446 | davinci | DAVINCI | ARM9 | linux-davinci | davinci-linux |
| DM355 | DaVinci | DM355 | davinci | DAVINCI | ARM9 | linux-davinci | davinci-linux |
| DM6467 | DaVinci | DM6467 | davinci | DAVINCI | ARM9, C64x+ | linux-davinci | davinci-linux |
| DM6446 | DaVinci | DM6446 | davinci | DAVINCI | ARM9, C64x+ | linux-davinci | davinci-linux |
| DM6443 | DaVinci | DM6446 | davinci | DAVINCI | ARM9, C64x+ | linux-davinci | davinci-linux |
| DM6441 | DaVinci | DM6446 | davinci | DAVINCI | ARM9, C64x+ | linux-davinci | davinci-linux |
Frequently Asked Questions
- Why are OMAP3 devices in the 'omap2' mach folder?
- OMAP2 and OMAP3 share a significant number of compatible peripherals and the maintainer chose this to maximize code reuse.
- Will the same kernel git trees and mailing lists continue to be used?
- Yes. No merging or splitting of the trees is planned at this point. This is really up to the external public maintainers (Tony and Kevin).
- Why are the OMAP-L1x devices maintained in the linux-davinci tree?
- The part numbers are based on the target markets, whereas the kernel tree decisions are based on the legacy of the technology used to create the devices. The OMAP-L1x devices are derived from DaVinci technology and cores.
- Where do I find the status of the drivers in the public git trees?
Precedence:
- Discussion on patch to add OMAP36x that references discussion on adding OMAP35x
- Patch to add OMAP35x support
- Announcement on linux-omap mailing list
Leave a Comment
