Difference between revisions of "Malta Linux Repository"

From LinuxMIPS
Jump to: navigation, search
m (MaltaLinuxRepository moved to Malta Linux Repository: MediaWiki doesn't need SillyNames(tm))
m (tidy up)
Line 1: Line 1:
MIPS Technologies Inc (MTI) is maintaining an additional repository containing a stable and tested kernel with focus on hardware support for MIPS Technologies' synthesizable cores and the Malta evaluation board. There kernels have undergone a range of conformance and soaktesting on the Malta platform, to provide 'stable' kernels with some degree of confidence. This code is now maintained on the <code>linux-mti-*</code> branches in the repository: http://www.linux-mips.org/git?p=linux-mti.git;a=summary, or you can clone it from git://www.linux-mips.org/pub/scm/linux-mti.git.
+
MIPS Technologies Inc (MTI) is maintaining an additional repository containing a stable and tested kernel with focus on hardware support for MIPS Technologies' synthesizable cores and the [[Malta]] evaluation board. There kernels have undergone a range of conformance and soaktesting on the Malta platform, to provide 'stable' kernels with some degree of confidence. This code is now maintained on the <code>linux-mti-*</code> branches in the repository: http://www.linux-mips.org/git?p=linux-mti.git;a=summary, or you can clone it from git://www.linux-mips.org/pub/scm/linux-mti.git.
  
 
Tarballs of particular releases are also available: http://www.linux-mips.org/pub/linux/mips/mti-stable/v2.6/.
 
Tarballs of particular releases are also available: http://www.linux-mips.org/pub/linux/mips/mti-stable/v2.6/.
Line 24: Line 24:
 
     git-clone git://ftp.linux-mips.org/pub/scm/linux-mti.git
 
     git-clone git://ftp.linux-mips.org/pub/scm/linux-mti.git
 
     git-checkout -b my-linux-mti-x.x.x.y-z linux-mti-x.x.x.y-z
 
     git-checkout -b my-linux-mti-x.x.x.y-z linux-mti-x.x.x.y-z
 
  
 
Where x.x.x.y-z is either the tag name, or branch of the kernel you want. For example linux-mti-2.6.19.1-14 is the tag for 2.6.19 patch level 1 and the MIPS build or patch level is 14.
 
Where x.x.x.y-z is either the tag name, or branch of the kernel you want. For example linux-mti-2.6.19.1-14 is the tag for 2.6.19 patch level 1 and the MIPS build or patch level is 14.
Line 33: Line 32:
 
     cd linux-mti
 
     cd linux-mti
 
     git-checkout -b my-linux-mti-2.6.19.1-14  linux-mti-2.6.19.1-14
 
     git-checkout -b my-linux-mti-2.6.19.1-14  linux-mti-2.6.19.1-14
 
 
  
 
Additional MTI generated configuration files can be found with the <code>malta_defconfig</code> in the MIPS configs directory:  
 
Additional MTI generated configuration files can be found with the <code>malta_defconfig</code> in the MIPS configs directory:  
 
<code> arch/mips/configs/malta_*config</code>. To use one of these configurations copy it to the root of your checked out linux kernel tree and run <code>make oldconfig</code>.  
 
<code> arch/mips/configs/malta_*config</code>. To use one of these configurations copy it to the root of your checked out linux kernel tree and run <code>make oldconfig</code>.  
 
  
 
     cp arch/mips/configs/malta_smtcconfig .config
 
     cp arch/mips/configs/malta_smtcconfig .config
 
     make oldconfig
 
     make oldconfig
 
  
 
In order to build the kernel, you will probably have to specify the prefix of your cross-compilation toolchain.  For example:
 
In order to build the kernel, you will probably have to specify the prefix of your cross-compilation toolchain.  For example:
 
  
 
     make CROSS_COMPILE=mipsisa32r2el-linux-
 
     make CROSS_COMPILE=mipsisa32r2el-linux-
 
  
 
Note that the trailing '-' in the example above is a part of the prefix, not a typo.
 
Note that the trailing '-' in the example above is a part of the prefix, not a typo.
  
 
If you want to submit changes back to linux-mips.org, you need to read http://www.linux-mips.org/wiki/The_perfect_patch page.
 
If you want to submit changes back to linux-mips.org, you need to read http://www.linux-mips.org/wiki/The_perfect_patch page.

Revision as of 15:54, 15 February 2008

MIPS Technologies Inc (MTI) is maintaining an additional repository containing a stable and tested kernel with focus on hardware support for MIPS Technologies' synthesizable cores and the Malta evaluation board. There kernels have undergone a range of conformance and soaktesting on the Malta platform, to provide 'stable' kernels with some degree of confidence. This code is now maintained on the linux-mti-* branches in the repository: http://www.linux-mips.org/git?p=linux-mti.git;a=summary, or you can clone it from git://www.linux-mips.org/pub/scm/linux-mti.git.

Tarballs of particular releases are also available: http://www.linux-mips.org/pub/linux/mips/mti-stable/v2.6/.

MTI aims to keep the linux-mti-* branches reasonably up to date with the latest available stable branch, or at most one version behind. This aiming to balance being modern and up-to-date with some degree of stability and reliability.

The kernel branches are labeled with the kernel version number, patch and the MTI build number, e.g.linux-mti-2.6.19.1-0. The current available kernels are:

Kernel version linux-mti tag Notes
2.6.19.1 linux-mti-2.6.19.1-14 [link to changelog...]

How to check out the linux-mti kernels

The following two commands will get you a local repository with the the tag or branch checked out into a local branch for you to work on.

   git-clone git://ftp.linux-mips.org/pub/scm/linux-mti.git
   git-checkout -b my-linux-mti-x.x.x.y-z linux-mti-x.x.x.y-z

Where x.x.x.y-z is either the tag name, or branch of the kernel you want. For example linux-mti-2.6.19.1-14 is the tag for 2.6.19 patch level 1 and the MIPS build or patch level is 14.

For example:

   git-clone git://ftp.linux-mips.org/pub/scm/linux-mti.git
   cd linux-mti
   git-checkout -b my-linux-mti-2.6.19.1-14  linux-mti-2.6.19.1-14

Additional MTI generated configuration files can be found with the malta_defconfig in the MIPS configs directory: arch/mips/configs/malta_*config. To use one of these configurations copy it to the root of your checked out linux kernel tree and run make oldconfig.

   cp arch/mips/configs/malta_smtcconfig .config
   make oldconfig

In order to build the kernel, you will probably have to specify the prefix of your cross-compilation toolchain. For example:

   make CROSS_COMPILE=mipsisa32r2el-linux-

Note that the trailing '-' in the example above is a part of the prefix, not a typo.

If you want to submit changes back to linux-mips.org, you need to read http://www.linux-mips.org/wiki/The_perfect_patch page.