Eric Lee / smarc-ti-linux-kernel

Download as
Browse Code ยป

Commit 0466dcbeda72e6a2753cd7e81f0a190054bd2233

Authored by Jesper Juhl
Committed by Linus Torvalds
1 parent 724d4c0306
Exists in master and in 20 other branches dlt-processor-sdk-linux-03.00.00.04, newt-ti-linux-3.12.y, processor-sdk-linux-01.00.00, processor-sdk-linux-02.00.01, smarc-ti-linux-3.12.10, smarc-ti-linux-3.12.y, smarc-ti-linux-3.14.y, smarc-ti-linux-3.15.y, smarc-ti-lsk-linux-4.1.y, smarct3x-processor-sdk-04.01.00.06, smarct3x-processor-sdk-linux-02.00.01, smarct3x-processor-sdk-linux-03.00.00.04, smarct4x-800-processor-sdk-linux-02.00.01, smarct4x-processor-sdk-04.01.00.06, smarct4x-processor-sdk-linux-02.00.01, smarct4x-processor-sdk-linux-03.00.00.04, ti-linux-3.12.y, ti-linux-3.14.y, ti-linux-3.15.y, ti-lsk-linux-4.1.y

Update version number references in README 

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>

Showing 1 changed file with 21 additions and 21 deletions Side-by-side Diff

1   - Linux kernel release 2.6.xx <http://kernel.org/>
  1 + Linux kernel release 3.x <http://kernel.org/>
2 2  
3   -These are the release notes for Linux version 2.6. Read them carefully,
  3 +These are the release notes for Linux version 3. Read them carefully,
4 4 as they tell you what this is all about, explain how to install the
5 5 kernel, and what to do if something goes wrong.
6 6  
7 7  
... ... @@ -62,10 +62,10 @@
62 62 directory where you have permissions (eg. your home directory) and
63 63 unpack it:
64 64  
65   - gzip -cd linux-2.6.XX.tar.gz | tar xvf -
  65 + gzip -cd linux-3.X.tar.gz | tar xvf -
66 66  
67 67 or
68   - bzip2 -dc linux-2.6.XX.tar.bz2 | tar xvf -
  68 + bzip2 -dc linux-3.X.tar.bz2 | tar xvf -
69 69  
70 70  
71 71 Replace "XX" with the version number of the latest kernel.
72 72  
73 73  
74 74  
... ... @@ -75,15 +75,15 @@
75 75 files. They should match the library, and not get messed up by
76 76 whatever the kernel-du-jour happens to be.
77 77  
78   - - You can also upgrade between 2.6.xx releases by patching. Patches are
  78 + - You can also upgrade between 3.x releases by patching. Patches are
79 79 distributed in the traditional gzip and the newer bzip2 format. To
80 80 install by patching, get all the newer patch files, enter the
81   - top level directory of the kernel source (linux-2.6.xx) and execute:
  81 + top level directory of the kernel source (linux-3.x) and execute:
82 82  
83   - gzip -cd ../patch-2.6.xx.gz | patch -p1
  83 + gzip -cd ../patch-3.x.gz | patch -p1
84 84  
85 85 or
86   - bzip2 -dc ../patch-2.6.xx.bz2 | patch -p1
  86 + bzip2 -dc ../patch-3.x.bz2 | patch -p1
87 87  
88 88 (repeat xx for all versions bigger than the version of your current
89 89 source tree, _in_order_) and you should be ok. You may want to remove
90 90  
... ... @@ -91,9 +91,9 @@
91 91 failed patches (xxx# or xxx.rej). If there are, either you or me has
92 92 made a mistake.
93 93  
94   - Unlike patches for the 2.6.x kernels, patches for the 2.6.x.y kernels
  94 + Unlike patches for the 3.x kernels, patches for the 3.x.y kernels
95 95 (also known as the -stable kernels) are not incremental but instead apply
96   - directly to the base 2.6.x kernel. Please read
  96 + directly to the base 3.x kernel. Please read
97 97 Documentation/applying-patches.txt for more information.
98 98  
99 99 Alternatively, the script patch-kernel can be used to automate this
... ... @@ -107,14 +107,14 @@
107 107 an alternative directory can be specified as the second argument.
108 108  
109 109 - If you are upgrading between releases using the stable series patches
110   - (for example, patch-2.6.xx.y), note that these "dot-releases" are
111   - not incremental and must be applied to the 2.6.xx base tree. For
112   - example, if your base kernel is 2.6.12 and you want to apply the
113   - 2.6.12.3 patch, you do not and indeed must not first apply the
114   - 2.6.12.1 and 2.6.12.2 patches. Similarly, if you are running kernel
115   - version 2.6.12.2 and want to jump to 2.6.12.3, you must first
116   - reverse the 2.6.12.2 patch (that is, patch -R) _before_ applying
117   - the 2.6.12.3 patch.
  110 + (for example, patch-3.x.y), note that these "dot-releases" are
  111 + not incremental and must be applied to the 3.x base tree. For
  112 + example, if your base kernel is 3.0 and you want to apply the
  113 + 3.0.3 patch, you do not and indeed must not first apply the
  114 + 3.0.1 and 3.0.2 patches. Similarly, if you are running kernel
  115 + version 3.0.2 and want to jump to 3.0.3, you must first
  116 + reverse the 3.0.2 patch (that is, patch -R) _before_ applying
  117 + the 3.0.3 patch.
118 118 You can read more on this in Documentation/applying-patches.txt
119 119  
120 120 - Make sure you have no stale .o files and dependencies lying around:
... ... @@ -126,7 +126,7 @@
126 126  
127 127 SOFTWARE REQUIREMENTS
128 128  
129   - Compiling and running the 2.6.xx kernels requires up-to-date
  129 + Compiling and running the 3.x kernels requires up-to-date
130 130 versions of various software packages. Consult
131 131 Documentation/Changes for the minimum version numbers required
132 132 and how to get updates for these packages. Beware that using
133 133  
... ... @@ -142,11 +142,11 @@
142 142 Using the option "make O=output/dir" allow you to specify an alternate
143 143 place for the output files (including .config).
144 144 Example:
145   - kernel source code: /usr/src/linux-2.6.N
  145 + kernel source code: /usr/src/linux-3.N
146 146 build directory: /home/name/build/kernel
147 147  
148 148 To configure and build the kernel use:
149   - cd /usr/src/linux-2.6.N
  149 + cd /usr/src/linux-3.N
150 150 make O=/home/name/build/kernel menuconfig
151 151 make O=/home/name/build/kernel
152 152 sudo make O=/home/name/build/kernel modules_install install