arch/arm/arm.rst

9 ---------------------
17   in the top level Makefile.  However, if you don't have the ARM Linux ELF
21   If you wish to cross-compile, then alter the following lines in the top
22   level make file::
36     CROSS_COMPILE=<your-path-to-your-compiler-without-gcc>
40     CROSS_COMPILE=arm-linux-
48 ---------------
54   Bug reports should be sent to linux-arm-kernel@lists.arm.linux.org.uk,
64 -------------
66   Several new include directories have been created under include/asm-arm,
67   which are there to reduce the clutter in the top-level directory.  These
71    `arch-*`	machine/platform specific header files
72    `hardware`	driver-internal ARM specific data structures/definitions
73    `mach`	descriptions of generic ARM to specific machine interfaces
74    `proc-*`	processor dependent header files (currently only two
79 Machine/Platform support
80 ------------------------
82   The ARM tree contains support for a lot of different machine types.  To
84   machine-specific parts by directory.  For this, the machine category is
86   $(MACHINE) to refer to the category)
88   To this end, we now have arch/arm/mach-$(MACHINE) directories which are
89   designed to house the non-driver files for a particular machine (eg, PCI,
91   machines, there should be a corresponding arch/arm/mach-$(MACHINE)/include/mach
96 -------
99   each module on an ARM2/ARM250/ARM3 machine when is loaded will take
109 ----------------
116   the start, and as such, you will have to give '-o offset' to losetup.
120 ---------------------
132 -----------------
142   big external 5.25" FH 64MB drive (who could ever want more :-) ).
146   last week :-)
154 -----------
162 ---------------------------------
175 ---------------------
176   The initial entry into the kernel is via head.S, which uses machine
177   independent code.  The machine is selected by the value of 'r1' on
184   We group machine (or platform) support code into machine classes.  A
187   classes are given directories - arch/arm/mach-<class> - which contain
188   the source files and include/mach/ to support the machine class.
191   devices, and contains the code to support the way the on-board and off-
193   machine specific "personality."
195   For platforms that support device tree (DT), the machine selection is
197   compile-time, support for the machine type must be selected.  This allows for
198   a single multiplatform kernel build to be used for several machine types.
200   For platforms that do not use device tree, this machine selection is
201   controlled by the machine type ID, which acts both as a run-time and a
202   compile-time code selection method.  You can register a new machine via the
207   Note: Please do not register a machine type for DT-only platforms.  If your
208   platform is DT-only, you do not need a registered machine type.
210 ---