joel16/android_kernel_sony_msm8994
1
0
Fork 0
mirror of https://github.com/joel16/android_kernel_sony_msm8994.git synced 2024-11-27 14:11:04 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update version number references in README

Browse Source 
When 3.0 is released I believe the README should reflect the new
numbering.

Signed-off-by: Jesper Juhl <jj@chaosbits.net>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
Jesper Juhl 2011-07-01 12:46:56 +02:00 committed by Linus Torvalds
parent 724d4c0306
commit 0466dcbeda
1 changed files with 21 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

42
README
View File

@ -1,6 +1,6 @@
Linux kernel release 2.6.xx <http://kernel.org/> Linux kernel release 3.x <http://kernel.org/>
These are the release notes for Linux version 2.6. Read them carefully, These are the release notes for Linux version 3. Read them carefully,
as they tell you what this is all about, explain how to install the as they tell you what this is all about, explain how to install the
kernel, and what to do if something goes wrong. kernel, and what to do if something goes wrong.
@ -62,10 +62,10 @@ INSTALLING the kernel source:
directory where you have permissions (eg. your home directory) and directory where you have permissions (eg. your home directory) and
unpack it: unpack it:
gzip -cd linux-2.6.XX.tar.gz | tar xvf - gzip -cd linux-3.X.tar.gz | tar xvf -
or or
bzip2 -dc linux-2.6.XX.tar.bz2 | tar xvf - bzip2 -dc linux-3.X.tar.bz2 | tar xvf -
Replace "XX" with the version number of the latest kernel. Replace "XX" with the version number of the latest kernel.
@ -75,15 +75,15 @@ INSTALLING the kernel source:
files. They should match the library, and not get messed up by files. They should match the library, and not get messed up by
whatever the kernel-du-jour happens to be. whatever the kernel-du-jour happens to be.
- You can also upgrade between 2.6.xx releases by patching. Patches are - You can also upgrade between 3.x releases by patching. Patches are
distributed in the traditional gzip and the newer bzip2 format. To distributed in the traditional gzip and the newer bzip2 format. To
install by patching, get all the newer patch files, enter the install by patching, get all the newer patch files, enter the
top level directory of the kernel source (linux-2.6.xx) and execute: top level directory of the kernel source (linux-3.x) and execute:
gzip -cd ../patch-2.6.xx.gz | patch -p1 gzip -cd ../patch-3.x.gz | patch -p1
or or
bzip2 -dc ../patch-2.6.xx.bz2 | patch -p1 bzip2 -dc ../patch-3.x.bz2 | patch -p1
(repeat xx for all versions bigger than the version of your current (repeat xx for all versions bigger than the version of your current
source tree, _in_order_) and you should be ok. You may want to remove source tree, _in_order_) and you should be ok. You may want to remove
@ -91,9 +91,9 @@ INSTALLING the kernel source:
failed patches (xxx# or xxx.rej). If there are, either you or me has failed patches (xxx# or xxx.rej). If there are, either you or me has
made a mistake. made a mistake.
Unlike patches for the 2.6.x kernels, patches for the 2.6.x.y kernels Unlike patches for the 3.x kernels, patches for the 3.x.y kernels
(also known as the -stable kernels) are not incremental but instead apply (also known as the -stable kernels) are not incremental but instead apply
directly to the base 2.6.x kernel. Please read directly to the base 3.x kernel. Please read
Documentation/applying-patches.txt for more information. Documentation/applying-patches.txt for more information.
Alternatively, the script patch-kernel can be used to automate this Alternatively, the script patch-kernel can be used to automate this
@ -107,14 +107,14 @@ INSTALLING the kernel source:
an alternative directory can be specified as the second argument. an alternative directory can be specified as the second argument.
- If you are upgrading between releases using the stable series patches - If you are upgrading between releases using the stable series patches
(for example, patch-2.6.xx.y), note that these "dot-releases" are (for example, patch-3.x.y), note that these "dot-releases" are
not incremental and must be applied to the 2.6.xx base tree. For not incremental and must be applied to the 3.x base tree. For
example, if your base kernel is 2.6.12 and you want to apply the example, if your base kernel is 3.0 and you want to apply the
2.6.12.3 patch, you do not and indeed must not first apply the 3.0.3 patch, you do not and indeed must not first apply the
2.6.12.1 and 2.6.12.2 patches. Similarly, if you are running kernel 3.0.1 and 3.0.2 patches. Similarly, if you are running kernel
version 2.6.12.2 and want to jump to 2.6.12.3, you must first version 3.0.2 and want to jump to 3.0.3, you must first
reverse the 2.6.12.2 patch (that is, patch -R) _before_ applying reverse the 3.0.2 patch (that is, patch -R) _before_ applying
the 2.6.12.3 patch. the 3.0.3 patch.
You can read more on this in Documentation/applying-patches.txt You can read more on this in Documentation/applying-patches.txt
- Make sure you have no stale .o files and dependencies lying around: - Make sure you have no stale .o files and dependencies lying around:
@ -126,7 +126,7 @@ INSTALLING the kernel source:
SOFTWARE REQUIREMENTS SOFTWARE REQUIREMENTS
Compiling and running the 2.6.xx kernels requires up-to-date Compiling and running the 3.x kernels requires up-to-date
versions of various software packages. Consult versions of various software packages. Consult
Documentation/Changes for the minimum version numbers required Documentation/Changes for the minimum version numbers required
and how to get updates for these packages. Beware that using and how to get updates for these packages. Beware that using
@ -142,11 +142,11 @@ BUILD directory for the kernel:
Using the option "make O=output/dir" allow you to specify an alternate Using the option "make O=output/dir" allow you to specify an alternate
place for the output files (including .config). place for the output files (including .config).
Example: Example:
kernel source code: /usr/src/linux-2.6.N kernel source code: /usr/src/linux-3.N
build directory: /home/name/build/kernel build directory: /home/name/build/kernel
To configure and build the kernel use: To configure and build the kernel use:
cd /usr/src/linux-2.6.N cd /usr/src/linux-3.N
make O=/home/name/build/kernel menuconfig make O=/home/name/build/kernel menuconfig
make O=/home/name/build/kernel make O=/home/name/build/kernel
sudo make O=/home/name/build/kernel modules_install install sudo make O=/home/name/build/kernel modules_install install