Samsung V1.3.0 manuale d’uso

Linux RFS v1.3.0 Porting Guide May 20-2008, Version 1.13[...]

[...]

Copyright notice Copyright 200 ⓒ 8 Flash Software Group, Samsung Electronics, Co., Ltd.. All rights reserved. Trademarks RFS is trademark of Flash Software G roup, Samsun g Electronics Co., Ltd.. in Korea and other countries Restrictions on Use and Transfer All software and documents of R FS are commercial s oftwa re. Therefore, you must install,[...]

II Linux RFS v1.3.0 Porting Guide Preface SEC-FSG-RFS1.2-POG This document is a portin g guide of RFS developed by Flash Soft ware Group, Memory Division, Samsung Electronics. It describes Linux RFS porting proce d ure to user's target platform. Purpose This document is RFS Port ing Guid e. This document explains the defin ition, architecture,[...]

Related Documents - RFS v1.3.0 Programmer’s Guide, Samsung Electronics, Co., Ltd. - LinuStoreII Utility Guide, Samsung Electron ic s Co., Ltd. - LinuStoreII Porting Guide, Samsung El ectronics Co., Ltd. History Version Date Comment Author 0.1 2006.01.05 Initial Flash Software Group 0.8 2006.01. 13 1 st draft Flash Software Group 1.4 2006.02.13 Re[...]

IV Linux RFS v1.3.0 Porting Guide Table of Contents 1 Introduction ......................................................................................... 1 1.1 Overview ........................................................................................ 1 1.2 Features ..........................................................................[...]

Tables Table 1 Host System Requirements ......................................................................... 4 Table 2 RFS Static Memory Usage (in bytes) .............................................................. 6 Table 3 Hardware informat ion o f OMAP2420 .............................................................. 6 V L i n u x R F S [...]

VI Linux RFS v1.3.0 Porting Guide Figures Figure 1-1 Linux RFS Archi tecture .......................................................................... 2 Figure 2-1 Directory Structure of Linux RFS Pack age .................................................... 4 Figure 2-2 Linux RFS Source File s (Annotated on the Source Tree) ......................[...]

1 Introduction This chapter describe s the overview and system a r c h i t e c t u r e o f R F S . I t a l s o c o v e r s t h e information about low-level flash memory partitions . 1.1 Overview Linux RFS (Linux Robust FAT File System) is a FAT c o m p a t i b l e f i l e s y s t e m t o u s e OneNAND/NAND flash memory as storage on any con sumer [...]

2 Linux RFS v1.3.0 Porting Guide Figure 1-1 Linux RFS Architecture  File Systems Linux file system for flash devi ces is managed by two f ile systems: CRAMFS and RFS. Both of these file systems run under Li nux VFS (Virtual File System). • CRAMFS: This is a read-only file system included in a stan dard Linux kernel distribution. CRAMFS is used[...]

4. Writing the sector data to the mod ified page These sequences of operations are not atomic, so a write request to this block device driver is prone to data corruption. For this reason , read-only file systems such as CRAMFS are adequate to run on top of this block device d river. • STL Block Device Driver: This block device driver is used to p[...]

4 Linux RFS v1.3.0 Porting Guide 2 Prerequisites This chapter explains the host/target system envi ronment for p orting RFS to your target system. Host is Linux PC environment and target can be any kind of con sumer device using OneNAND flash memory. 2.1 Host Environment The following table shows the host syst em requ irements for con figuring and [...]

 fs – RFS file system module  drivers - XSR block device driver module  tools - Utilities to manipulate RFS  scripts - RFS Package Installation scripts  Include – includes header files 2.2.2 Source Files List This section gives sho rt description of source fi les listed in the ‘rfs’ and ‘xsr’ directory. The source files i[...]

6 Linux RFS v1.3.0 Porting Guide Most of the sources are platform-independent co des except PAM. Please refer the “XSR Porting Guide” for more deta iled information. Bef ore going into detail ab out RFS customiza tion according to target requ irement, next section will explain about objects that Linu x RFS will create during make (or build) ste[...]

3 Po r t i n g L i n u x R F S This chapter describe s porting overview, hard ware configuration fo r OneNAND, Linux RFS initialization and port ing p rocedure with OMAP 2420 target board. 3.1 Porting Overview This section describe s Linux RFS porting procedure briefly. The procedure is divided into 5 steps as shown in the following figure. Hardwar[...]

8 Linux RFS v1.3.0 Porting Guide If you are using Linux kernel 2.4.xx specify ‘kernel type’ as 24. If you are using Linux kernel 2.6.xx specify ‘kernel type’ as 26. Shell> cd $(TOP_DIR) Shell> $(RFS_TOP_DIR)/scripts/rfs_install.sh 24 3.2.2 Kernel Configuration for RFS 3.2.2.1 Menu Configuration of Kernel for RFS As shown below, you sh[...]

Figure 3-3 File system screen of Kerne l menu Figure 3-3 shows the detailed RFS configuration. 1. The first is FAT32 and l ong file name support 2. The second is direct I/O support. But, this fe ature is experimental and should not be used in production environ ment . 3. The third is debugging me ssage option ☞ NOTE You have to execute the ‘mkr[...]

10 Linux RFS v1.3.0 Porting Guide Figure 3-4 Code maturity level  You should set the make option for “COM PRESSE D ROM FILE SYSTEM (CRAMFS)” in file system option during make menuconfig bec ause the root f ile system is managed by CRAMFS.[...]

Figure 3-5 CRMAFS OPTION Settings Now, you can proceed to build the kernel and the kernel module s. Before start ing build process your kernel cross compile path ‘C ROSS_COMPILE = ’ must be set in $(KERNEL_TOP_DIR)/Makefile. To build the kernel , type the following commands in sequence. shell> cd $(KERNEL_TOP_DIR) shell> make clean shell&[...]

12 Linux RFS v1.3.0 Porting Guide After all of these steps, you will have the kernel image ‘uImage’. For usage of OneNAND device on your target, please refe r to ftools utility guide. 3.3 Using the NLS (Native Language Support ) The FAT Filesystem can deal with filenames in native language character sets. These ch aracter sets are stored in so-[...]

Figure 3-7 NLS(Native Language Supp ort) configur ation And you should select the codepage s like the default codepage and other code pages to be used at the target. Then, the codepages will be compiled as built-in or module. For example, if you set the default cod epage to “cp949” for Korean, you have to select “Codepage 949” at this menu.[...]

14 Linux RFS v1.3.0 Porting Guide Figure 3-8 RFS Filesystem configuration for F A T16 If you decide to build RFS Filesyste m as FAT 16 type, you always make the filenames with the native language in the 8.3 format regard less of NLS support. Wh y is this possible? The NLS is used for the conversion the filename s with the native language to/from Un[...]

If you didn’t select the ‘FAT32 & long file name’ when you built the kernel image, this command will succe ss an d RFS is able to support filenames with the native language in the 8.3 format. If you selected the NLS support and the default codepage, this command will success if only the default codepage is configured and built. For exampl[...]

16 Linux RFS v1.3.0 Porting Guide Appendix I. Description of FAT Configuration Option z CONFIG_RFS_FS Description Configuration option for RFS Behavioral description This option should be set for RFS suppo rt. Additional notice None z CONFIG_RFS_VFAT Description To avoid the patent problems related to Window FAT file sy stem, RFS can be built witho[...]

This option has the name of the default codepage. Behavioral description This option is valid if only the CONFIG_R FS _NLS is turned on. When the mount option ‘codepage’ of the RFS Filesystem is not set, th is value can be used for mounting and for the conversion of the filename with this character set. Additional notice None z CONFIG_RFS_FAT_D[...]

18 Linux RFS v1.3.0 Porting Guide This option enables RFS to use a iget4() interface i nstead of a iget_locked() interface. If your kernel supports a iget_locked() interface, you can disable it. Additional notice For MontaVista Linux P ro 3.1, you shou ld disable this option. F or CEE 3.1, this option should be enabled. Default is enable. z CONFIG_[...]