managing_kernel_upgrades.html

ADI 公司blackfin系列的用户使用文挡。

INODES   = 1024
</pre>

<p>
To change the size of the file system, edit the <code>BLOCKS</code> variable.
</p>
</div>
</li>
<li class="level2"><div class="li"> Default files for the target root file system. These files go into the <code>/etc</code> directory:</div>
<ul>
<li class="level3"><div class="li"> <code>group</code></div>
</li>
<li class="level3"><div class="li"> <code>host.conf</code></div>
</li>
<li class="level3"><div class="li"> <code>hosts</code> - This file describes a number of hostname-to-address mappings for the TCP/IP subsystem.  It is mostly used at boot time, when no name servers are running. On small systems, this file can be used instead of a &ldquo;named&rdquo; name server.</div>
</li>
<li class="level3"><div class="li"> <code>inetd.conf</code></div>
</li>
<li class="level3"><div class="li"> <code>inittab</code> - The inittab file describes which processes are started at bootup and during normal operation (e.g. <code>/etc/init.d/boot</code>, <code>/etc/init.d/rc</code>, <code>gettys</code>...).  Init distinguishes multiple runlevels, each of which can have its own set of processes that are started. Valid runlevels are 0-6 plus A, B, and C for ondemand entries. For more information check <code>man 5 inittab</code> on a Linux based host.</div>
</li>
<li class="level3"><div class="li"> <code>issue</code></div>
</li>
<li class="level3"><div class="li"> <code>motd</code> - Message of the Day. This prints out at every login.</div>
</li>
<li class="level3"><div class="li"> <code>passwd</code></div>
</li>
<li class="level3"><div class="li"> <code>protocols</code></div>
</li>
<li class="level3"><div class="li"> <code>rc</code></div>
</li>
<li class="level3"><div class="li"> <code>services</code></div>
</li>
<li class="level3"><div class="li"> <code>TZ</code> - Time Zone</div>
</li>
<li class="level3"><div class="li"> <code>config.device</code> - the top level <code>./uClinux-dist/.config</code> file, used to select targets from the command line. This is used to modify the uClinux-distribution to allow a command line option to set up or build the new target system from a command line. If you copy an existing vendors directory, you should do this by hand, after things are configured. In this case: <code>cp uClinux-dist/.config uClinux-dist/vendors/AnalogDevices/BF533-STAMP-JFFS2/config.device</code></div>
</li>
</ul>
</li>
</ul>
</li>
<li class="level1"><div class="li"> There are other files in this directory, but they should be edited by the make system only. These files are:</div>
<ul>
<li class="level2"><div class="li"> <code>config.arch</code> - includes <code>./uClinux-dist/vendors/config/bfin/config.arch</code> which sets up all things Blackfin related, including default compiler options, and flags for when using <code>bfin-uclinux-gcc</code>. You should not modify this.</div>
</li>
<li class="level2"><div class="li"> <code>config.linux-2.6.x</code> - This is the generated make config for the kernel. When you select your platform, this will be copied into the kernel config system as <code>./uClinux-dist/linux-2.6.x/.config</code>, and <code>./uClinux-dist/linux-2.6.x/include/linux/autoconf.h</code> will automatically be re-generated.</div>
</li>
<li class="level2"><div class="li"> <code>config.uClibc</code> - This is the generated make config for the uClibc. When you select your platform, this will be copied into the uClibc config system.</div>
</li>
<li class="level2"><div class="li"> <code>config.vendor-2.6.x</code> - This is the generated make config for the user applications which is found in <code>./uClinux-dist/config/.config</code>, and controls which user applications are built. When you select your platform, this will be copied into the user config system.</div>
</li>
</ul>
</li>
<li class="level1"><div class="li"> Once the configuration is the way you want it, you can select your platforms by doing a <code>make menuconfig</code> and select <code> Vendor/Product Selection</code> &rarr; <code>Select the Product you wish to target</code><pre class="code">
( ) BF533-EZKIT
( ) BF533-STAMP
(X) BF533-STAMP-JFFS2
( ) BF537-EZKIT
</pre>

<p>
This configuration can be modified using the normal <code>Kernel/Library/Defaults Selection</code> &rarr; <code>Customize Kernel Settings</code> and <code>Customize Vendor/User Settings</code> in <code>make menuconfig</code>. Updating these settings will save the configuration data into the <code>./uClinux-dist/linux-2.6.x/.config</code>. 
</p>
</div>
</li>
</ol>

<p>
 <code>uClinux-dist/vendors/AnalogDevices/BF533-STAMP</code><code>index.html</code><code>tuxsit_small.gif</code><code>tux-wink.gif</code> 
</p>

</div>
<!-- SECTION [2923-10340] -->
<h3><a name="romfsinst" id="romfsinst">$ROMFSINST</a></h3>
<div class="level3">

<p>
When looking through various makefiles, you will notice to add various files to the target file system, the command  
</p>
<pre class="code">$ROMFSINST [options] [src] dst
</pre>

<p>
 is used. Normally, <code>$ROMFSINST</code> is defined in the top level <code>./uClinux-dist/Makefile</code> to be equal to <code>romfs-inst.sh</code>, which is in the <code>./uclinux-dist/tools</code> directory. It has the following options: 
</p>
<ul>
<li class="level1"><div class="li"> <code>-v</code> output actions performed.</div>
</li>
<li class="level1"><div class="li"> <code>-e env-var</code> only take action if env-var is set to &ldquo;y&rdquo;.</div>
</li>
<li class="level1"><div class="li"> <code>-o option</code> only take action if option is set to &ldquo;y&rdquo;.</div>
</li>
<li class="level1"><div class="li"> <code>-p perms</code> chmod style permissions for dst.</div>
</li>
<li class="level1"><div class="li"> <code>-a text</code> append text to dst.</div>
</li>
<li class="level1"><div class="li"> <code>-A pattern</code> only append text if pattern doesn&rsquo;t exist in file</div>
</li>
<li class="level1"><div class="li"> <code>-l link</code> dst is a link to &lsquo;link&rsquo;.</div>
</li>
<li class="level1"><div class="li"> <code>-s sym-link</code> dst is a sym-link to &lsquo;sym-link&rsquo;.</div>
</li>
</ul>

<p>
 If <code>src</code> is not provided, basename is run on <code>dst</code> to determine the source in the current directory.
</p>

<p>
Multiple <code>-e</code> and <code>-o</code> options are ANDed together.  To achieve an OR affect use a single <code>-e</code>/<code>-o</code> with 1 or more <code>y</code>/<code>n</code>/<code>&ldquo;&ldquo;</code> chars in the condition.
</p>

<p>
if src is a directory,  everything in it is copied recursively to dst with special files removed (currently <acronym title="Concurrent Versions System">CVS</acronym> dirs).
</p>

</div>
<!-- SECTION [10341-11530] -->
<h2><a name="saving_kernel_settings" id="saving_kernel_settings">Saving kernel settings</a></h2>
<div class="level2">

<p>
When you have a configuration that you would like to ensure is not lost, you can save the settings in the various kernel and user config files by selecting <code>Kernel/Library/Defaults Selection</code> &rarr; <code>Update Default Vendor Settings</code> in <code>make menuconfig</code>. When doing this, this should be the only option selected.   <code>$LINUXDIR</code><code>&ldquo;linux-2.6.x&rdquo;</code><code>$VENDOR</code><code>&ldquo;Analog Devices&rdquo;</code><code>$PRODUCT</code><code>&ldquo;BF533-STAMP-JFFS2&rdquo;</code><code>$TMP</code><code>-2.6.x</code> 
</p>

</div>
<!-- SECTION [11531-12113] -->
<h2><a name="recalling_kernel_settings" id="recalling_kernel_settings">Recalling kernel settings</a></h2>
<div class="level2">

<p>
 If you have made a mistake when doing <code>make menuconfig</code> it is possible to remove any changes, and go back to previously saved settings. <code>/Library/Defaults Selection</code> &rarr; <code>Default all settings (lose changes)</code> in <code>make menuconfig</code>. When doing this, this should be the only option selected.
</p>

</div>
<!-- SECTION [12114-12448] -->
<h2><a name="updating_the_kernel" id="updating_the_kernel">Updating the kernel</a></h2>
<div class="level2">

<p>
When updating from one kernel version to a new kernel version, do the following:
</p>
<ol>
<li class="level1"><div class="li"> download the new kernel version into a new directory, without overwriting your old files.</div>
</li>
<li class="level1"><div class="li"> copy the old configuration files to the new kernel version<pre class="code">
cp -R /path/from/old/kernel/uClinux-dist/vendors/AnalogDevices/BF533-STAMP-JFFS2 /path/to/new/kernel/uClinux-dist/vendors/AnalogDevices/BF533-STAMP-JFFS2
</pre>
</div>
</li>
<li class="level1"><div class="li"> do a <code>make menuconfig</code> and select the platform you just added. If you have replaced an existing platform, you should recall the kernel settings to ensure that your new settings are properly in the make system. You may be asked some questions if there are new settings that were not previously avalible in the older kernel. These should be answered, and then you should save the updated defaults to ensure that you don&rsquo;t have to answer these questions again.</div>
</li>
</ol>

</div>
<!-- SECTION [12449-] --></body>
</html>