Supported Processors: Difference between revisions

From Linux/Xtensa
Jump to navigation Jump to search
Line 10: Line 10:
Despite the endless possibilities provided by the configurability and extensibility of the Xtensa architecture, obtaining an open source toolchain and kernel that fully support a specific configured Xtensa core is a straightforward matter.  The process is mostly automated (scripted), avoiding any need to manually port the kernel to a new processor variant as is typical for a fixed processor architecture.  Modifications to toolchain and kernel sources are limited to a small set of configuration files, typically provided by Tensilica in the form of an ''overlay'' to be copied into the sources.  The development tools and kernel are subsequently configured and built as usual.  (Of course, you still have to port Linux to your particular board or platform.)
Despite the endless possibilities provided by the configurability and extensibility of the Xtensa architecture, obtaining an open source toolchain and kernel that fully support a specific configured Xtensa core is a straightforward matter.  The process is mostly automated (scripted), avoiding any need to manually port the kernel to a new processor variant as is typical for a fixed processor architecture.  Modifications to toolchain and kernel sources are limited to a small set of configuration files, typically provided by Tensilica in the form of an ''overlay'' to be copied into the sources.  The development tools and kernel are subsequently configured and built as usual.  (Of course, you still have to port Linux to your particular board or platform.)


In the Linux kernel for example, all configuration files are located inside the Xtensa include directory in the kernel sources (<code>arch/xtensa/include/variant/''config''/include/variant/</code>).  Adding support to the kernel for a custom configured Xtensa processor generally involves copying the appropriate configuration files into the appropriate variant directory.
In the Linux kernel for example, all configuration files are located inside the Xtensa include directory in the kernel sources (<code>arch/xtensa/variant/''config''/include/variant/</code>).  Adding support to the kernel for a custom configured Xtensa processor generally involves copying the appropriate configuration files into the appropriate variant directory. See [[Buildroot_Build_Instructions#Install_any_required_processor_specific_overlay|Buildroot Overlay Installation]] for an automated method of installing these files in both toolchain and kernel sources.
 
See [[Buildroot_Build_Instructions#Install_any_required_processor_specific_overlay|Buildroot Overlay Installation]] for an automated method of installing these files in both toolchain and kernel sources.


== Kernel and Processor Configuration ==
== Kernel and Processor Configuration ==

Revision as of 15:52, 14 March 2013

Xtensa Processor Architecture

Chip.jpg

The Xtensa processor architecture is a configurable, extensible, and synthesizable 32-bit RISC processor core. SoC and processor designers can select from a variety of options, such as instruction-set extensions, memory, cache, and interrupt configurations. Moreover, Xtensa processors can be extended with custom-defined instructions and registers, as well as custom port and queue interfaces. All Xtensa processors share a common base instruction set architecture, thereby ensuring compatibility of third party application software and development tools.

Tensilica’s Diamond Standard Series processor family consists of a number of ready-to-use synthesizable cores and is based on the Xtensa processor architecture. The Diamond Standard 233L processor contains an MMU and fully supports running Linux.

Automatic Support for Custom Xtensa Cores

Despite the endless possibilities provided by the configurability and extensibility of the Xtensa architecture, obtaining an open source toolchain and kernel that fully support a specific configured Xtensa core is a straightforward matter. The process is mostly automated (scripted), avoiding any need to manually port the kernel to a new processor variant as is typical for a fixed processor architecture. Modifications to toolchain and kernel sources are limited to a small set of configuration files, typically provided by Tensilica in the form of an overlay to be copied into the sources. The development tools and kernel are subsequently configured and built as usual. (Of course, you still have to port Linux to your particular board or platform.)

In the Linux kernel for example, all configuration files are located inside the Xtensa include directory in the kernel sources (arch/xtensa/variant/config/include/variant/). Adding support to the kernel for a custom configured Xtensa processor generally involves copying the appropriate configuration files into the appropriate variant directory. See Buildroot Overlay Installation for an automated method of installing these files in both toolchain and kernel sources.

Kernel and Processor Configuration

Because the kernel is much closer to the hardware and provides an abstraction for many architectural options, it needs to be configured and compiled for a particular platform and processor configuration. It also requires development tools configured for the particular processor. Note that a processor configuration is also often referred to as a core variant. The following list shows processor configurations included in the kernel.


Supported processors in the Linux kernel
Name Notes
Custom-configured Xtensa Vendor specific, requires overlay
Diamond 232L
Stretch S6000 Without MMU
'FSF' Default configuration for verification only