Driver Source File Structure

The driver component source tree is organized as follows:

• the 'top level' containing files related to component definition and all files related to the build of all drivers

• the generic driver class with one directory per driver class (ethernet, timer, uart, ...)

• the chip class below each driver class with one directory per chip

• the family directory below which you will find all family specific drivers organized by class.

Figure 10-1 New Driver Source Tree

The new driver source tree can either be created within the ChorusOS source tree, or in another location. If you create it in the ChorusOS source tree, it will automatically be part of the standard DRV component of ChorusOS (see "Building a ChorusOS System Image with a New BSP/DRV Component"). However, if you create it elsewhere then you will need to add a new MYDRV component when you configure your system image in your build_dir:

% cd build_dir
% configure -b $TOOLS $KERNEL -s $DRV $BSP $MYDRV