Lines Matching refs:to
10 In order to compile ARM Linux, you will need a compiler capable of
11 generating ARM ELF code with GNU extensions. GCC 3.3 is known to be
15 To build ARM Linux natively, you shouldn't have to alter the ARCH = line
20 If you wish to cross-compile, then alter the following lines in the top
30 to
31 CROSS_COMPILE=<your-path-to-your-compiler-without-gcc>
35 Do a 'make config', followed by 'make Image' to build the kernel
43 Please send patches to the patch system. For more information, see
45 explanation as to what the patch does and why it is needed.
47 Bug reports should be sent to linux-arm-kernel@lists.arm.linux.org.uk,
60 which are there to reduce the clutter in the top-level directory. These
65 mach descriptions of generic ARM to specific machine interfaces
74 continue supporting these differences, it has become necessary to split
76 used to select which directories and files get included (we will use
77 $(MACHINE) to refer to the category)
80 designed to house the non-driver files for a particular machine (eg, PCI,
91 memory up to the next 32k boundary due to the size of the pages.
94 However, ARM6 and up machines allow modules to take multiples of 4k, and
107 the start, and as such, you will have to give '-o offset' to losetup.
110 Request to developers
115 allows the driver to be compiled as a loadable module without requiring
116 half the code to be compiled into the kernel image.
118 In general, try to avoid using assembler unless it is really necessary. It
119 makes drivers far less easy to port to other hardware.
125 The ST506 hard drive controllers seem to be working fine (if a little
127 A4x0's motherboard, but for it to work off a Podule just requires
128 someone with a podule to add the addresses for the IRQ mask and the
129 HDC base to the source.
132 *configure harddrive set to 2). I've got an internal 20MB and a great
146 This also seems to work OK, but hasn't been stressed much lately. It
148 could be a bit of a problem! Suggestions on the correct way to do this
154 A change was made in 2003 to the macro names for new machines.
157 e.g. Assabet. It was decided to change the implementation macros
158 to read CONFIG_MACH_ for clarity. Moreover, a retroactive fixup has
171 Due to the large number of machines which the ARM port of Linux provides
172 for, we have a method to manage this which ensures that we don't end up
179 arch/arm/mach-<class> - which contain the source files to/include/mach
184 devices, and contains the code to support the way the on-board and off-
189 controlled at runtime by passing the device tree blob to the kernel. At
191 a single multiplatform kernel build to be used for several machine types.