1 =======================================
2 FUJITSU FR-V LINUX KERNEL CONFIGURATION
3 =======================================
9 The most important setting is in the "MMU support options" tab (the first
10 presented in the configuration tools available):
14 This options allows selection of normal, MMU-requiring linux, and uClinux
15 (which doesn't require an MMU and doesn't have inter-process protection).
17 There are a number of settings in the "Processor type and features" section of
18 the kernel configuration that need to be considered.
22 The register and instruction sets at the core of the processor. This can
23 only be set to "FR40x/45x/55x" at the moment - but this permits usage of
24 the kernel with MB93091 CB10, CB11, CB30, CB41, CB60, CB70 and CB451
25 CPU boards, and with the MB93093 PDK board.
29 This option allows a choice of basic system. This governs the peripherals
30 that are expected to be available.
34 This specifies the type of motherboard being used, and the peripherals
35 upon it. Currently only "MB93090-MB00" can be set here.
37 (*) "Default cache-write mode"
39 This controls the initial data cache write management mode. By default
40 Write-Through is selected, but Write-Back (Copy-Back) can also be
41 selected. This can be changed dynamically once the kernel is running (see
44 There are some architecture specific configuration options in the "General
45 Setup" section of the kernel configuration too:
47 (*) "Reserve memory uncached for (PCI) DMA"
49 This requests that a uClinux kernel set aside some memory in an uncached
50 window for the use as consistent DMA memory (mainly for PCI). At least a
51 megabyte will be allocated in this way, possibly more. Any memory so
52 reserved will not be available for normal allocations.
54 (*) "Kernel support for ELF-FDPIC binaries"
56 This enables the binary-format driver for the new FDPIC ELF binaries that
57 this platform normally uses. These binaries are totally relocatable -
58 their separate sections can relocated independently, allowing them to be
59 shared on uClinux where possible. This should normally be enabled.
61 (*) "Kernel image protection"
63 This makes the protection register governing access to the core kernel
64 image prohibit access by userspace programs. This option is available on
67 There are also a number of settings in the "Kernel Hacking" section of the
68 kernel configuration especially for debugging a kernel on this
69 architecture. See the "gdbstub.txt" file for information about those.
72 ======================
73 DEFAULT CONFIGURATIONS
74 ======================
76 The kernel sources include a number of example default configurations:
80 Default configuration for the MB93091-VDK with both CPU board and
81 MB93090-MB00 motherboard running uClinux.
84 (*) defconfig-mb93091-fb
86 Default configuration for the MB93091-VDK with CPU board,
87 MB93090-MB00 motherboard, and DAV board running uClinux.
88 Includes framebuffer driver.
93 Default configuration for the MB93093-PDK board running uClinux.
96 (*) defconfig-cb70-standalone
98 Default configuration for the MB93091-VDK with only CB70 CPU board
99 running uClinux. This will use the CB70's DM9000 for network access.
104 Default configuration for the MB93091-VDK with both CB451 CPU board and
105 MB93090-MB00 motherboard running MMU linux.
107 (*) defconfig-mmu-audio
109 Default configuration for the MB93091-VDK with CB451 CPU board, DAV
110 board, and MB93090-MB00 motherboard running MMU linux. Includes
115 Default configuration for the MB93091-VDK with CB451 CPU board, DAV
116 board, and MB93090-MB00 motherboard running MMU linux. Includes
119 (*) defconfig-mmu-standalone
121 Default configuration for the MB93091-VDK with only CB451 CPU board