blob: d3e5df9fb36bd139a4a7e93840ae974181a8e2d8 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
|
menu "Platform options"
comment "Memory settings"
config NIOS2_MEM_BASE
hex "Memory base address"
default "0x00000000"
help
This is the physical address of the memory that the kernel will run
from. This address is used to link the kernel and setup initial memory
management. You should take the raw memory address without any MMU
or cache bits set.
Please not that this address is used directly so you have to manually
do address translation if it's connected to a bridge.
comment "Device tree"
config NIOS2_DTB_AT_PHYS_ADDR
bool "DTB at physical address"
default n
help
When enabled you can select a physical address to load the dtb from.
Normally this address is passed by a bootloader such as u-boot but
using this you can use a devicetree without a bootloader.
This way you can store a devicetree in NOR flash or an onchip rom.
Please note that this address is used directly so you have to manually
do address translation if it's connected to a bridge. Also take into
account that when using an MMU you'd have to ad 0xC0000000 to your
address
config NIOS2_DTB_PHYS_ADDR
hex "DTB Address"
depends on NIOS2_DTB_AT_PHYS_ADDR
default "0xC0000000"
help
Physical address of a dtb blob.
config NIOS2_DTB_SOURCE_BOOL
bool "Compile and link device tree into kernel image"
default n
help
This allows you to specify a dts (device tree source) file
which will be compiled and linked into the kernel image.
config NIOS2_DTB_SOURCE
string "Device tree source file"
depends on NIOS2_DTB_SOURCE_BOOL
default ""
help
Absolute path to the device tree source (dts) file describing your
system.
comment "Nios II instructions"
config NIOS2_HW_MUL_SUPPORT
bool "Enable MUL instruction"
default n
help
Set to true if you configured the Nios II to include the MUL
instruction. This will enable the -mhw-mul compiler flag.
config NIOS2_HW_MULX_SUPPORT
bool "Enable MULX instruction"
default n
help
Set to true if you configured the Nios II to include the MULX
instruction. Enables the -mhw-mulx compiler flag.
config NIOS2_HW_DIV_SUPPORT
bool "Enable DIV instruction"
default n
help
Set to true if you configured the Nios II to include the DIV
instruction. Enables the -mhw-div compiler flag.
config NIOS2_FPU_SUPPORT
bool "Custom floating point instr support"
default n
help
Enables the -mcustom-fpu-cfg=60-1 compiler flag.
config NIOS2_CI_SWAB_SUPPORT
bool "Byteswap custom instruction"
default n
help
Use the byteswap (endian converter) Nios II custom instruction provided
by Altera and which can be enabled in QSYS builder. This accelerates
endian conversions in the kernel (e.g. ntohs).
config NIOS2_CI_SWAB_NO
int "Byteswap custom instruction number" if NIOS2_CI_SWAB_SUPPORT
default 0
help
Number of the instruction as configured in QSYS Builder.
comment "Cache settings"
config CUSTOM_CACHE_SETTINGS
bool "Custom cache settings"
help
This option allows you to tweak the cache settings used during early
boot (where the information from device tree is not yet available).
There should be no reason to change these values. Linux will work
perfectly fine, even if the Nios II is configured with smaller caches.
Say N here unless you know what you are doing.
config NIOS2_DCACHE_SIZE
hex "D-Cache size" if CUSTOM_CACHE_SETTINGS
range 0x200 0x10000
default "0x800"
help
Maximum possible data cache size.
config NIOS2_DCACHE_LINE_SIZE
hex "D-Cache line size" if CUSTOM_CACHE_SETTINGS
range 0x10 0x20
default "0x20"
help
Minimum possible data cache line size.
config NIOS2_ICACHE_SIZE
hex "I-Cache size" if CUSTOM_CACHE_SETTINGS
range 0x200 0x10000
default "0x1000"
help
Maximum possible instruction cache size.
endmenu
|
