Difference: WebHome (1 vs. 24)

Revision 2430 Sep 2010 - Main.PeterPearse

Line: 1 to 1
 
META TOPICPARENT

Welcome to the LinuxKernel web

ARM Linux Kernel

Line: 12 to 12
 Note that with the 2.6.x kernels you need a more recent version of module-init-tools package. More information on these tools is available on Rusty's pages.

Setting up kernel sources

Changed:
<
<		The latest sources are available from http://www.kernel.org, you can also use one of the mirror sites. You should read the Changelog file for details on differences between kernel versions.It is recommended that new development, i.e. any work liable to result in a set of patches, be based against this tree.
>
>		The latest sources are available from http://www.kernel.org, you can also use one of the mirror sites. You should read the Changelog file for details on differences between kernel versions.It is recommended that new development, i.e. any work liable to result in a set of patches, be based against this tree or the git .
 A version of the kernel tested against ARM Ltd. platforms (RealView Versatile and RealView Integrator) is accessible on the following pages. Sources and binaries on this page are updated against successive releases of the main kernel.org tree, and may contain changes that have not yet been integrated into the main tree.

Revision 2329 Sep 2010 - Main.PeterPearse

Line: 1 to 1
 
META TOPICPARENT

Welcome to the LinuxKernel web

ARM Linux Kernel

Line: 12 to 12
 Note that with the 2.6.x kernels you need a more recent version of module-init-tools package. More information on these tools is available on Rusty's pages.

Setting up kernel sources

Changed:
<
<		The latest sources are available from http://www.kernel.org, you can also use one of the mirror sites. You should read the Changelog file for details on differences between kernel versions.
>
>		The latest sources are available from http://www.kernel.org, you can also use one of the mirror sites. You should read the Changelog file for details on differences between kernel versions.It is recommended that new development, i.e. any work liable to result in a set of patches, be based against this tree.
 A version of the kernel tested against ARM Ltd. platforms (RealView Versatile and RealView Integrator) is accessible on the following pages. Sources and binaries on this page are updated against successive releases of the main kernel.org tree, and may contain changes that have not yet been integrated into the main tree.

ARM kernel patches which have not yet been merged upstream (or are in the review process) are available from the following http://www.linux-arm.org/git GIT tree.
Added:
>
>		Patches are submitted both to the kernel main tree and to the linaro kernel tree. ARM kernel patches may be present in the linaro tree before acceptance into the main kernel tree.
 

Vendor Patchsets

Some vendors that sell chips with embedded ARM cores have associated patches available for specific versions of the Linux kernel. Typically you apply these by unpacking the kernel, changing directory into the unpacked kernel and executing something like 'patch -p1 </path/to/patchfile.patch'

Revision 2227 Sep 2010 - Main.PhilippeRobin

Line: 1 to 1
 
META TOPICPARENT

Welcome to the LinuxKernel web

ARM Linux Kernel

Line: 16 to 16
 A version of the kernel tested against ARM Ltd. platforms (RealView Versatile and RealView Integrator) is accessible on the following pages. Sources and binaries on this page are updated against successive releases of the main kernel.org tree, and may contain changes that have not yet been integrated into the main tree.
Changed:
<
<		Expand on this once we have the GIT tree and notes on browsing the tree via the web interface.
>
>		ARM kernel patches which have not yet been merged upstream (or are in the review process) are available from the following http://www.linux-arm.org/git GIT tree.
 

Vendor Patchsets

Some vendors that sell chips with embedded ARM cores have associated patches available for specific versions of the Linux kernel. Typically you apply these by unpacking the kernel, changing directory into the unpacked kernel and executing something like 'patch -p1 </path/to/patchfile.patch'
Line: 61 to 61
 
  • The following link provides some documentation on how to build kernels.
  • Wookey published the following document describing how to port the Linux kernel to a new ARM based platform.
  • Document on Memory Barriers: PDF
Changed:
<
<		There is also additional information in other sections of this Wiki: LinuxDevTools, Resume Writing Services reverse phone detective jump higher Electronic Cigarette earth4energy grow taller
>
>		There is also additional information in other sections of this Wiki: LinuxDevTools
 
META FILEATTACHMENTattr="" autoattached="1" comment="" date="1139312268" name="gorman_linux_vm.pdf" path="gorman_linux_vm.pdf" size="8719549" user="Main.PhilippeRobin" version="1"
META FILEATTACHMENTattr="" autoattached="1" comment="" date="1139311738" name="aleph-porting.pdf" path="aleph-porting.pdf" size="125209" user="Main.PhilippeRobin" version="1"

Revision 2128 Aug 2010 - Main.DavidBieber

Line: 1 to 1
 
META TOPICPARENT

Welcome to the LinuxKernel web

ARM Linux Kernel

Line: 61 to 61
 
  • The following link provides some documentation on how to build kernels.
  • Wookey published the following document describing how to port the Linux kernel to a new ARM based platform.
  • Document on Memory Barriers: PDF
Changed:
<
<		There is also additional information in other sections of this Wiki: LinuxDevTools, Resume Writing Services
>
>		There is also additional information in other sections of this Wiki: LinuxDevTools, Resume Writing Services reverse phone detective jump higher Electronic Cigarette earth4energy grow taller
 
META FILEATTACHMENTattr="" autoattached="1" comment="" date="1139312268" name="gorman_linux_vm.pdf" path="gorman_linux_vm.pdf" size="8719549" user="Main.PhilippeRobin" version="1"
META FILEATTACHMENTattr="" autoattached="1" comment="" date="1139311738" name="aleph-porting.pdf" path="aleph-porting.pdf" size="125209" user="Main.PhilippeRobin" version="1"

Revision 2010 Aug 2010 - Main.ResumeWriting

Line: 1 to 1
 
META TOPICPARENT

Welcome to the LinuxKernel web

ARM Linux Kernel

Line: 61 to 61
 
  • The following link provides some documentation on how to build kernels.
  • Wookey published the following document describing how to port the Linux kernel to a new ARM based platform.
  • Document on Memory Barriers: PDF
Changed:
<
<		There is also additional information in other sections of this Wiki: LinuxDevTools, LinuxFilesystem, LinuxBootLoader and LinuxPlatform.
>
>		There is also additional information in other sections of this Wiki: LinuxDevTools, Resume Writing Services
 
META FILEATTACHMENTattr="" autoattached="1" comment="" date="1139312268" name="gorman_linux_vm.pdf" path="gorman_linux_vm.pdf" size="8719549" user="Main.PhilippeRobin" version="1"
META FILEATTACHMENTattr="" autoattached="1" comment="" date="1139311738" name="aleph-porting.pdf" path="aleph-porting.pdf" size="125209" user="Main.PhilippeRobin" version="1"

Revision 1923 Jun 2010 - Main.PhilippeRobin

Line: 1 to 1
 
META TOPICPARENT

Welcome to the LinuxKernel web

ARM Linux Kernel

Summary

Changed:
<
<		System requirements
Setting up kernel sources
Vendor Patchsets
Configuration
Building the kernel
Porting the kernel to a new platform
Power Management
Resume services
>
>		System requirements
Setting up kernel sources
Vendor Patchsets
Configuration
Building the kernel
Porting the kernel to a new platform
Android Platform
Power Management
Resume services
 

System requirements

Linux kernel sources will use anywhere from 40Mb to 80Mb of file system space on the host development platform. On the target platform, the binary kernel image and included modules should require in the order of 2Mb, depending on functionality selected when configuring the kernel. You will need to have suitable versions of the GNU compiler and other tools used to configure and build the kernel (make etc.). You can find more information on the development tools on the following LinuxDevTools page.
Line: 45 to 45
 The Linux kernel assumes that the boot loader has initialised the platform and stored identification of the platform ID (cf. arch/arm/tools/mach-types in the kernel tree) and boot parameters in specific registers. The platform number is needed by the kernel before starting its execution and the CMDLINE should also be set by the boot loader. When starting the kernel directly from a debugger, these register values need to be set from within the debugger.

Changed:
<
<

Porting the kernel to a new platform

>
>

Porting the kernel to new platforms

 
Changed:
<
<		The following page provides information on the main steps to port Linux to a new ARM platform. There are other resources referenced on this site/page in the community detailing some of these steps. This is by no means complete so feel free to add more information as appropriate.
>
>		The following page provides information on the main steps to port Linux to a new ARM platform. Additional resources are referenced on this site/page in the community detailing some of these steps. This is by no means complete so feel free to add more information as appropriate.

Building Linux for Android platforms

The following page describes the various steps to build Android for ARM RealView platforms.
 

Additional information

Line: 58 to 63
 
  • Document on Memory Barriers: PDF
There is also additional information in other sections of this Wiki: LinuxDevTools, LinuxFilesystem, LinuxBootLoader and LinuxPlatform.
Deleted:
<
<		-- TWikiGuest? - 20 Jan 2006
 
META FILEATTACHMENTattr="" autoattached="1" comment="" date="1139312268" name="gorman_linux_vm.pdf" path="gorman_linux_vm.pdf" size="8719549" user="Main.PhilippeRobin" version="1"
META FILEATTACHMENTattr="" autoattached="1" comment="" date="1139311738" name="aleph-porting.pdf" path="aleph-porting.pdf" size="125209" user="Main.PhilippeRobin" version="1"

Revision 1817 Mar 2010 - Main.JassyBroot

Line: 1 to 1
 
META TOPICPARENT

Welcome to the LinuxKernel web

ARM Linux Kernel

Summary

Changed:
<
<		System requirements
Setting up kernel sources
Vendor Patchsets
Configuration
Building the kernel
Porting the kernel to a new platform
Power Management
Additional information
>
>		System requirements
Setting up kernel sources
Vendor Patchsets
Configuration
Building the kernel
Porting the kernel to a new platform
Power Management
Resume services
 

System requirements

Linux kernel sources will use anywhere from 40Mb to 80Mb of file system space on the host development platform. On the target platform, the binary kernel image and included modules should require in the order of 2Mb, depending on functionality selected when configuring the kernel. You will need to have suitable versions of the GNU compiler and other tools used to configure and build the kernel (make etc.). You can find more information on the development tools on the following LinuxDevTools page.
Changed:
<
<		Note that with the 2.6.x kernels you need a more recent version of module-init-tools package. More information on these tools is available on Rusty's pages.
>
>		Note that with the 2.6.x kernels you need a more recent version of module-init-tools package. More information on these tools is available on Rusty's pages.
 

Setting up kernel sources

The latest sources are available from http://www.kernel.org, you can also use one of the mirror sites. You should read the Changelog file for details on differences between kernel versions.
Changed:
<
<		A version of the kernel tested against ARM Ltd. platforms (RealView Versatile and RealView Integrator) is accessible on the following pages. Sources and binaries on this page are updated against successive releases of the main kernel.org tree, and may contain changes that have not yet been integrated into the main tree.
>
>		A version of the kernel tested against ARM Ltd. platforms (RealView Versatile and RealView Integrator) is accessible on the following pages. Sources and binaries on this page are updated against successive releases of the main kernel.org tree, and may contain changes that have not yet been integrated into the main tree.
 Expand on this once we have the GIT tree and notes on browsing the tree via the web interface.

Vendor Patchsets

Changed:
<
<		Some vendors that sell chips with embedded ARM cores have associated patches available for specific versions of the Linux kernel. Typically you apply these by unpacking the kernel, changing directory into the unpacked kernel and executing something like 'patch -p1 </path/to/patchfile.patch'
>
>		Some vendors that sell chips with embedded ARM cores have associated patches available for specific versions of the Linux kernel. Typically you apply these by unpacking the kernel, changing directory into the unpacked kernel and executing something like 'patch -p1 </path/to/patchfile.patch'
 Please, refer to the Platform Info page on this site for pointers and information on individual boards.

Configuration

The configuration process allows users to select features to be included in the kernel image. This usually requires knowledge of the hardware platform and environment you will use to run Linux. Current kernels have graphical configuration utilities and usually provide help sections for most of the configuration options. All the selected options are kept in a .config file located at the base of your source tree.
Changed:
<
<		Make sure that you backup existing .config file before it is being edited and modified by any configuration utility. If you are using a distribution from a vendor, the default configuration files are usually included in the 
or a dedicated directory. You can use these configuration files as a starting point for your customisations.
>
>		Make sure that you backup existing .config file before it is being edited and modified by any configuration utility. If you are using a distribution from a vendor, the default configuration files are usually included in the 
or a dedicated directory. You can use these configuration files as a starting point for your customisations.
 With 2.6.x kernels there are few main front-end programs which can be used to configure the kernel: config, oldconfig, menuconfig, and xconfig.
Line: 45 to 38
 qconf.jpg
 Building the kernel
Changed:
<
<		The kernel is built by doing a 'make Image' or 'make bzImage'. The resulting kernel image should be in the arch/arm/boot directory. You can use these images to load them either in RAM or Flash memory to be executed.
>
>		The kernel is built by doing a 'make Image' or 'make bzImage'. The resulting kernel image should be in the arch/arm/boot directory. You can use these images to load them either in RAM or Flash memory to be executed.
 The build process also produces a vmlinux file is which contains debugging information associated to the kernel image. This file can be loaded from a debugger (when or after the kernel starts its execution) to perform symbolic debug.
Revision 1710 Dec 2009 - Main.PhilippeRobin
Line: 1 to 1
 
META TOPICPARENT
 Welcome to the LinuxKernel web
 ARM Linux Kernel
Line: 62 to 62
 
  • Opersys provide some note on building Linux systems.
  • The following link provides some documentation on how to build kernels.
  • Wookey published the following document describing how to port the Linux kernel to a new ARM based platform.
Added:
>
>
  • Document on Memory Barriers: PDF
 There is also additional information in other sections of this Wiki: LinuxDevTools, LinuxFilesystem, LinuxBootLoader and LinuxPlatform.
Revision 1603 Jul 2008 - Main.TurhanOz
Line: 1 to 1
 
META TOPICPARENT
 Welcome to the LinuxKernel web
 ARM Linux Kernel
Line: 10 to 10
 Configuration
Building the kernel
Porting the kernel to a new platform
Added:
>
>		Power Management
 Additional information
 System requirements
Revision 1514 Oct 2007 - Main.HristoErinin
Line: 1 to 1
 
META TOPICPARENT
 Welcome to the LinuxKernel web
 ARM Linux Kernel
Line: 38 to 38
 
  • config presents a series of questions to be answered sequentially. In case of error, you must begin the process from the beginning. Pressing <Enter> will accept the default entry (usually labelled in upper case).
  • oldconfig read the defaults from an existing .config and rewrite necessary links and files. Use this option if you've made minor changes to source files or need to script the rebuild process.
Changed:
<
<
  • menuconfig is a front-end based on ncurses. Make sure that you have ncurses libraries installed on you host platform to use this utility. Use the arrow keys to navigate the menu. Press <Enter> to select sub-menus. Press the highlighted letter on each option to jump directly to that option. To build an option directly into the kernel, press <Y>. To disable an option entirely, press <N>. To build an option as a loadable module, press . You can also access content-specific help screens by pressing <?> on each page or selecting <HELP> from the lower menu.
>
>
  • menuconfig is a front-end based on ncurses. Make sure that you have ncurses libraries installed on you host platform to use this utility. Use the arrow keys to navigate the menu. Press <Enter> to select sub-menus. Press the highlighted letter on each option to jump directly to that option. To build an option directly into the kernel, press <Y>. To disable an option entirely, press <N>. To build an option as a loadable module, press <M>. You can also access content-specific help screens by pressing <?> on each page or selecting <HELP> from the lower menu.
 
  • xconfig is a graphical front-end using qconf by Roman Zippel and provide a more intuitive and customizable interface. It requires the Qt and X libraries to build and use. An online help is automatically displayed for each kernel configuration option and dependencies for each module is also displayed (c.f. qconf snapshot below).
qconf.jpg
Line: 53 to 53
 
 Porting the kernel to a new platform
Changed:
<
<		The following page provide information on the main steps to port Linux to a new ARM platform. There are other resource referenced on this site/page in the community detailing some of these steps. This is by no means complete so feel free to add more information as appropriate.
>
>		The following page provides information on the main steps to port Linux to a new ARM platform. There are other resources referenced on this site/page in the community detailing some of these steps. This is by no means complete so feel free to add more information as appropriate.
 
 Additional information
Revision 1426 Oct 2006 - Main.PhilippeRobin
Line: 1 to 1
 
META TOPICPARENT
 Welcome to the LinuxKernel web
 ARM Linux Kernel
Line: 53 to 53
 
 Porting the kernel to a new platform
Changed:
<
<		The following page LinuxNewPlatformPort provides information on the main steps to port Linux to a new ARM platform. There are other resource referenced on this site/page in the community detailing some of these steps. This is by no means complete so feel free to add more information as appropriate.
>
>		The following page provide information on the main steps to port Linux to a new ARM platform. There are other resource referenced on this site/page in the community detailing some of these steps. This is by no means complete so feel free to add more information as appropriate.
 
 Additional information
Revision 1326 Oct 2006 - Main.PhilippeRobin
Line: 1 to 1
 
META TOPICPARENT
 Welcome to the LinuxKernel web
 ARM Linux Kernel
Added:
>
>
 Summary
System requirements
Setting up kernel sources
Vendor Patchsets
Configuration
Building the kernel
Porting the kernel to a new platform
Additional information
 
 System requirements
Linux kernel sources will use anywhere from 40Mb to 80Mb of file system space on the host development platform. On the target platform, the binary kernel image and included modules should require in the order of 2Mb, depending on functionality selected when configuring the kernel. You will need to have suitable versions of the GNU compiler and other tools used to configure and build the kernel (make etc.). You can find more information on the development tools on the following LinuxDevTools page.
Line: 41 to 50
 The Linux kernel assumes that the boot loader has initialised the platform and stored identification of the platform ID (cf. arch/arm/tools/mach-types in the kernel tree) and boot parameters in specific registers. The platform number is needed by the kernel before starting its execution and the CMDLINE should also be set by the boot loader. When starting the kernel directly from a debugger, these register values need to be set from within the debugger.
Added:
>
>
 Porting the kernel to a new platform
The following page LinuxNewPlatformPort provides information on the main steps to port Linux to a new ARM platform. There are other resource referenced on this site/page in the community detailing some of these steps. This is by no means complete so feel free to add more information as appropriate.
 
 Additional information
Revision 1207 Jun 2006 - Main.PhilippeRobin
Line: 1 to 1
 
META TOPICPARENT
 Welcome to the LinuxKernel web
 ARM Linux Kernel
Line: 18 to 18
 
 Vendor Patchsets
Some vendors that sell chips with embedded ARM cores have associated patches available for specific versions of the Linux kernel. Typically you apply these by unpacking the kernel, changing directory into the unpacked kernel and executing something like 'patch -p1 </path/to/patchfile.patch'
Changed:
<
<
>
>		Please, refer to the Platform Info page on this site for pointers and information on individual boards.
 
 Configuration
The configuration process allows users to select features to be included in the kernel image. This usually requires knowledge of the hardware platform and environment you will use to run Linux. Current kernels have graphical configuration utilities and usually provide help sections for most of the configuration options. All the selected options are kept in a .config file located at the base of your source tree.
Revision 1108 May 2006 - Main.LucasVillaReal
Line: 1 to 1
 
META TOPICPARENT
 Welcome to the LinuxKernel web
 ARM Linux Kernel
Line: 42 to 42
 The Linux kernel assumes that the boot loader has initialised the platform and stored identification of the platform ID (cf. arch/arm/tools/mach-types in the kernel tree) and boot parameters in specific registers. The platform number is needed by the kernel before starting its execution and the CMDLINE should also be set by the boot loader. When starting the kernel directly from a debugger, these register values need to be set from within the debugger.
 Additional information
Changed:
<
<
>
>
 
  • Opersys provide some note on building Linux systems.
  • The following link provides some documentation on how to build kernels.
  • Wookey published the following document describing how to port the Linux kernel to a new ARM based platform.
Revision 1008 May 2006 - Main.AndyGreen
Line: 1 to 1
 
META TOPICPARENT
 Welcome to the LinuxKernel web
 ARM Linux Kernel
Line: 15 to 15
 Expand on this once we have the GIT tree and notes on browsing the tree via the web interface.
Added:
>
>
 Vendor Patchsets
Some vendors that sell chips with embedded ARM cores have associated patches available for specific versions of the Linux kernel. Typically you apply these by unpacking the kernel, changing directory into the unpacked kernel and executing something like 'patch -p1 </path/to/patchfile.patch'
 
 Configuration
The configuration process allows users to select features to be included in the kernel image. This usually requires knowledge of the hardware platform and environment you will use to run Linux. Current kernels have graphical configuration utilities and usually provide help sections for most of the configuration options. All the selected options are kept in a .config file located at the base of your source tree.
Line: 46 to 51
 There is also additional information in other sections of this Wiki: LinuxDevTools, LinuxFilesystem, LinuxBootLoader and LinuxPlatform.
-- TWikiGuest? - 20 Jan 2006
Changed:
<
<
>
>
META FILEATTACHMENTattr="" autoattached="1" comment="" date="1139312268" name="gorman_linux_vm.pdf" path="gorman_linux_vm.pdf" size="8719549" user="Main.PhilippeRobin" version="1"
 
META FILEATTACHMENTattr="" autoattached="1" comment="" date="1139311738" name="aleph-porting.pdf" path="aleph-porting.pdf" size="125209" user="Main.PhilippeRobin" version="1"
META FILEATTACHMENTattr="" autoattached="1" comment="" date="1137764806" name="qconf.jpg" path="qconf.jpg" size="43372" user="Main.PhilippeRobin" version="1"
Deleted:
<
<
META FILEATTACHMENTattachment="gorman_linux_vm.pdf" attr="" comment="" date="1139312268" name="gorman_linux_vm.pdf" path="H:\trf\gorman_linux_vm.pdf" size="8719549" stream="H:\trf\gorman_linux_vm.pdf" user="Main.PhilippeRobin" version="1"
Revision 907 Feb 2006 - Main.PhilippeRobin
Line: 1 to 1
 
META TOPICPARENT
 Welcome to the LinuxKernel web
 ARM Linux Kernel
Line: 38 to 38
 
 Additional information
  • Linux Device Driver Third Edition, by Jonathan Corbet, Alessandro Rubini, and Greg Kroah-Hartman.
Added:
>
>
 
  • Opersys provide some note on building Linux systems.
  • The following link provides some documentation on how to build kernels.
  • Wookey published the following document describing how to port the Linux kernel to a new ARM based platform.
Line: 47 to 48
 -- TWikiGuest? - 20 Jan 2006
Changed:
<
<
META FILEATTACHMENTattachment="qconf.jpg" attr="" comment="" date="1137764806" name="qconf.jpg" path="qconf.jpg" size="43372" stream="qconf.jpg" user="Main.PhilippeRobin" version="1"
>
>
META FILEATTACHMENTattr="" autoattached="1" comment="" date="1139311738" name="aleph-porting.pdf" path="aleph-porting.pdf" size="125209" user="Main.PhilippeRobin" version="1"
META FILEATTACHMENTattr="" autoattached="1" comment="" date="1137764806" name="qconf.jpg" path="qconf.jpg" size="43372" user="Main.PhilippeRobin" version="1"
META FILEATTACHMENTattachment="gorman_linux_vm.pdf" attr="" comment="" date="1139312268" name="gorman_linux_vm.pdf" path="H:\trf\gorman_linux_vm.pdf" size="8719549" stream="H:\trf\gorman_linux_vm.pdf" user="Main.PhilippeRobin" version="1"
Revision 803 Feb 2006 - Main.PhilippeRobin
Line: 1 to 1
 
META TOPICPARENT
 Welcome to the LinuxKernel web
 ARM Linux Kernel
Revision 720 Jan 2006 - Main.PhilippeRobin
Line: 1 to 1
 
META TOPICPARENT
 Welcome to the LinuxKernel web
 ARM Linux Kernel
Line: 37 to 37
 The Linux kernel assumes that the boot loader has initialised the platform and stored identification of the platform ID (cf. arch/arm/tools/mach-types in the kernel tree) and boot parameters in specific registers. The platform number is needed by the kernel before starting its execution and the CMDLINE should also be set by the boot loader. When starting the kernel directly from a debugger, these register values need to be set from within the debugger.
 Additional information
Added:
>
>
  • Linux Device Driver Third Edition, by Jonathan Corbet, Alessandro Rubini, and Greg Kroah-Hartman.
 * Opersys provide some note on building Linux systems. * The following link provides some documentation on how to build kernels. * Wookey published the following document describing how to port the Linux kernel to a new ARM based platform.
There is also additional information in other sections of this Wiki: LinuxDevTools, LinuxFilesystem, LinuxBootLoader and LinuxPlatform.
Changed:
<
<		-- TWikiGuest? - 22 Aug 2005
>
>		-- TWikiGuest? - 20 Jan 2006
META FILEATTACHMENTattachment="qconf.jpg" attr="" comment="" date="1137764806" name="qconf.jpg" path="qconf.jpg" size="43372" stream="qconf.jpg" user="Main.PhilippeRobin" version="1"
Revision 619 Jan 2006 - TWikiGuest
Line: 1 to 1
Added:
>
>
META TOPICPARENT
 
 Welcome to the LinuxKernel web
Added:
>
>
 ARM Linux Kernel
 
Changed:
<
<
 Available Information
  • ...
  • ...
  • ...

(advanced search)
>
>
 System requirements
Linux kernel sources will use anywhere from 40Mb to 80Mb of file system space on the host development platform. On the target platform, the binary kernel image and included modules should require in the order of 2Mb, depending on functionality selected when configuring the kernel. You will need to have suitable versions of the GNU compiler and other tools used to configure and build the kernel (make etc.). You can find more information on the development tools on the following LinuxDevTools page.
Note that with the 2.6.x kernels you need a more recent version of module-init-tools package. More information on these tools is available on Rusty's pages.
 Setting up kernel sources
The latest sources are available from http://www.kernel.org, you can also use one of the mirror sites. You should read the Changelog file for details on differences between kernel versions.
A version of the kernel tested against ARM Ltd. platforms (RealView Versatile and RealView Integrator) is accessible on the following pages. Sources and binaries on this page are updated against successive releases of the main kernel.org tree, and may contain changes that have not yet been integrated into the main tree.
Expand on this once we have the GIT tree and notes on browsing the tree via the web interface.
 Configuration
The configuration process allows users to select features to be included in the kernel image. This usually requires knowledge of the hardware platform and environment you will use to run Linux. Current kernels have graphical configuration utilities and usually provide help sections for most of the configuration options. All the selected options are kept in a .config file located at the base of your source tree.
Make sure that you backup existing .config file before it is being edited and modified by any configuration utility. If you are using a distribution from a vendor, the default configuration files are usually included in the 
or a dedicated directory. You can use these configuration files as a starting point for your customisations.
With 2.6.x kernels there are few main front-end programs which can be used to configure the kernel: config, oldconfig, menuconfig, and xconfig.
* config presents a series of questions to be answered sequentially. In case of error, you must begin the process from the beginning. Pressing <Enter> will accept the default entry (usually labelled in upper case). * oldconfig read the defaults from an existing .config and rewrite necessary links and files. Use this option if you've made minor changes to source files or need to script the rebuild process. * menuconfig is a front-end based on ncurses. Make sure that you have ncurses libraries installed on you host platform to use this utility. Use the arrow keys to navigate the menu. Press <Enter> to select sub-menus. Press the highlighted letter on each option to jump directly to that option. To build an option directly into the kernel, press <Y>. To disable an option entirely, press <N>. To build an option as a loadable module, press . You can also access content-specific help screens by pressing <?> on each page or selecting <HELP> from the lower menu. * xconfig is a graphical front-end using qconf by Roman Zippel and provide a more intuitive and customizable interface. It requires the Qt and X libraries to build and use. An online help is automatically displayed for each kernel configuration option and dependencies for each module is also displayed (c.f. qconf snapshot below).
qconf.jpg
 Building the kernel
The kernel is built by doing a 'make Image' or 'make bzImage'. The resulting kernel image should be in the arch/arm/boot directory. You can use these images to load them either in RAM or Flash memory to be executed.
The build process also produces a vmlinux file is which contains debugging information associated to the kernel image. This file can be loaded from a debugger (when or after the kernel starts its execution) to perform symbolic debug.
The Linux kernel assumes that the boot loader has initialised the platform and stored identification of the platform ID (cf. arch/arm/tools/mach-types in the kernel tree) and boot parameters in specific registers. The platform number is needed by the kernel before starting its execution and the CMDLINE should also be set by the boot loader. When starting the kernel directly from a debugger, these register values need to be set from within the debugger.
 Additional information
* Opersys provide some note on building Linux systems. * The following link provides some documentation on how to build kernels. * Wookey published the following document describing how to port the Linux kernel to a new ARM based platform.
There is also additional information in other sections of this Wiki: LinuxDevTools, LinuxFilesystem, LinuxBootLoader and LinuxPlatform.
-- TWikiGuest? - 22 Aug 2005
Revision 528 Mar 2005 - TWikiContributor
Line: 1 to 1
Changed:
<
<		Welcome to the home of Foswiki.LinuxKernel. This is a web-based collaboration area for ...
>
>
 Welcome to the LinuxKernel web
 
Changed:
<
<
  • MeetingMinutes?
>
>
 Available Information
  • ...
  • ...
  • ...
 
Changed:
<
<
 Site Tools of the LinuxKernel? Web
Notes:
  • You are currently in the LinuxKernel web. The color code for this web is this background, so you know where you are.
  • If you are not familiar with the Foswiki collaboration platform, please visit WelcomeGuest first.
WebDescription of WebUsed to...Links
 
Web color Main
Welcome to Foswiki... Users, Groups...see who is registered on this site
Web color System
Welcome, Registration, and other StartingPoints; Foswiki history & Wiki style; All the docs......discover Foswiki details, and how to start your own site.
Web color LinuxBootLoader
Linux Boot Loader Web...collaborate on Linux Boot Loader
Web color LinuxDevTools
Linux Development Tools Web...collaborate on Linux Development Tools
Web color LinuxFilesystem
Linux Filesystem Web...collaborate on Linux Filesystem
Web color LinuxKernel
Linux Kernel Web...collaborate on Linux Kernel
Web color LinuxPlatform
Linux Platform Web...collaborate on Linux Platform
Web color LinuxReference
reference documentation...collaborate on
Web color Sandbox
Sandbox test area with all features enabled....experiment in an unrestricted hands-on web.
You can use color coding by web for identification and reference. This table is updated automatically based on WebPreferences settings of the individual webs. Contact [email protected] if you need a separate collaboration web for your team. See also AdminToolsCategory.
Legend:Go to the home of the webrecentchangesSee recent changes in the web
searchtopicSearch the webnotifySubscribe to get notified of changes by e-mail
>
>

(advanced search)
Revision 414 Apr 2002 - PeterThoeny
Line: 1 to 1
 Welcome to the home of Foswiki.LinuxKernel. This is a web-based collaboration area for ...
  • MeetingMinutes?
Changed:
<
<
 Maintenance of the LinuxKernel? web
  • WebChanges: Find out recent modifications to the LinuxKernel? web.
  • WebIndex: Display all LinuxKernel? topics in alphabetical order. See also the faster WebTopicList
  • WebNotify: Subscribe to be automatically notified when something changes in the LinuxKernel? web.
  • WebStatistics: View access statistics of the LinuxKernel? web.
  • WebPreferences: Preferences of the LinuxKernel? web.
>
>
 Site Tools of the LinuxKernel? Web
 Notes:
Changed:
<
<
  • You are currently in the LinuxKernel? web. The color code for this web is a (SPECIFY COLOR) background, so you know where you are.
  • If you are not familiar with the Foswiki collaboration tool, please visit WelcomeGuest in the Foswiki.TWiki web first.
>
>
  • You are currently in the LinuxKernel web. The color code for this web is this background, so you know where you are.
  • If you are not familiar with the Foswiki collaboration platform, please visit WelcomeGuest first.
 
WebDescription of WebUsed to...Links
 
Web color Main
Welcome to Foswiki... Users, Groups...see who is registered on this site
Web color System
Welcome, Registration, and other StartingPoints; Foswiki history & Wiki style; All the docs......discover Foswiki details, and how to start your own site.
Web color LinuxBootLoader
Linux Boot Loader Web...collaborate on Linux Boot Loader
Web color LinuxDevTools
Linux Development Tools Web...collaborate on Linux Development Tools
Web color LinuxFilesystem
Linux Filesystem Web...collaborate on Linux Filesystem
Web color LinuxKernel
Linux Kernel Web...collaborate on Linux Kernel
Web color LinuxPlatform
Linux Platform Web...collaborate on Linux Platform
Web color LinuxReference
reference documentation...collaborate on
Web color Sandbox
Sandbox test area with all features enabled....experiment in an unrestricted hands-on web.
You can use color coding by web for identification and reference. This table is updated automatically based on WebPreferences settings of the individual webs. Contact [email protected] if you need a separate collaboration web for your team. See also AdminToolsCategory.
Legend:Go to the home of the webrecentchangesSee recent changes in the web
searchtopicSearch the webnotifySubscribe to get notified of changes by e-mail
Revision 307 Apr 2002 - PeterThoeny
Line: 1 to 1
 Welcome to the home of Foswiki.LinuxKernel. This is a web-based collaboration area for ...
  • MeetingMinutes?
Line: 18 to 18
 
  • You are currently in the LinuxKernel? web. The color code for this web is a (SPECIFY COLOR) background, so you know where you are.
  • If you are not familiar with the Foswiki collaboration tool, please visit WelcomeGuest in the Foswiki.TWiki web first.
Changed:
<
<
Warning: Can't find topic TWiki.TWikiWebsTable
>
>
WebDescription of WebUsed to...Links
 
Web color Main
Welcome to Foswiki... Users, Groups...see who is registered on this site
Web color System
Welcome, Registration, and other StartingPoints; Foswiki history & Wiki style; All the docs......discover Foswiki details, and how to start your own site.
Web color LinuxBootLoader
Linux Boot Loader Web...collaborate on Linux Boot Loader
Web color LinuxDevTools
Linux Development Tools Web...collaborate on Linux Development Tools
Web color LinuxFilesystem
Linux Filesystem Web...collaborate on Linux Filesystem
Web color LinuxKernel
Linux Kernel Web...collaborate on Linux Kernel
Web color LinuxPlatform
Linux Platform Web...collaborate on Linux Platform
Web color LinuxReference
reference documentation...collaborate on
Web color Sandbox
Sandbox test area with all features enabled....experiment in an unrestricted hands-on web.
You can use color coding by web for identification and reference. This table is updated automatically based on WebPreferences settings of the individual webs. Contact [email protected] if you need a separate collaboration web for your team. See also AdminToolsCategory.
Legend:Go to the home of the webrecentchangesSee recent changes in the web
searchtopicSearch the webnotifySubscribe to get notified of changes by e-mail
Revision 224 Nov 2001 - PeterThoeny
Line: 1 to 1
 Welcome to the home of Foswiki.LinuxKernel. This is a web-based collaboration area for ...
  • MeetingMinutes?
Line: 8 to 8
 
  • WebChanges: Find out recent modifications to the LinuxKernel? web.
Changed:
<
<
  • WebIndex: Display all LinuxKernel? topics in alphabetical order.
>
>
 
  • WebNotify: Subscribe to be automatically notified when something changes in the LinuxKernel? web.
  • WebStatistics: View access statistics of the LinuxKernel? web.
  • WebPreferences: Preferences of the LinuxKernel? web.
Revision 108 Aug 2001 - PeterThoeny
Line: 1 to 1
Added:
>
>		Welcome to the home of Foswiki.LinuxKernel. This is a web-based collaboration area for ...
  • MeetingMinutes?
 Maintenance of the LinuxKernel? web
  • WebChanges: Find out recent modifications to the LinuxKernel? web.
  • WebIndex: Display all LinuxKernel? topics in alphabetical order.
  • WebNotify: Subscribe to be automatically notified when something changes in the LinuxKernel? web.
  • WebStatistics: View access statistics of the LinuxKernel? web.
  • WebPreferences: Preferences of the LinuxKernel? web.
Notes:
  • You are currently in the LinuxKernel? web. The color code for this web is a (SPECIFY COLOR) background, so you know where you are.
  • If you are not familiar with the Foswiki collaboration tool, please visit WelcomeGuest in the Foswiki.TWiki web first.
Warning: Can't find topic TWiki.TWikiWebsTable
View topic | History: r24 < r23 < r22 < r21 | More topic actions...
 
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback
This page took 26.09 joules of energy to render (zen6 : 15.48 secs : 6 sessions : 0.84 amps) More Info