How is barebox OMAP specific architecture code organized?
To understand the architecture of barebox source code for OMAP processors, we need to understand a bit on OMAP itself. A typical Texas Instrument’s Open Multimedia Application Processor (OMAP) solution is built around ARM core with multiple on-the-silicon peripherals. It also has a TI Digital Signal Processor(DSP) and few hardware accelerators to cater to computing intensive applications such as encoder/decoders. See http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=11988&contentId=4638 for further details. Essentially, OMAP is modular with on-silicon peripherals being reused across multiple OMAP versions. Barebox code organization is driven by this fact. Motivation for code organization is driven from: • Clear distinction between architecture and board features. • Code should be re-usable accross OMAP variants AND board variants. Code is Organized into three main directories: • arch/arm/mach-omap -contains files for ALL peripherals which are present
