OrgApache/incubator-nuttx
OrgApache
/
incubator-nuttx
mirror of https://github.com/apache/incubator-nuttx.git
1
0
Fork 0
Code Issues Releases Wiki Activity

New Kconfig convention: Extra indentation in comments will render as HTML preformatted text

This commit is contained in:
Gregory Nutt 2013-04-22 09:10:58 -06:00
parent 65fec0683a
commit 803a860d34
4 changed files with 40 additions and 40 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
arch/arm/Kconfig
View File

@ -188,7 +188,7 @@ config ARMV7M_USEBASEPRI
depends on ARCH_CORTEXM3 || ARCH_CORTEXM4
---help---
Use the BASEPRI register to enable and disable able interrupts. By
default, the PRIMASK register is used for this purpose. This
default, the PRIMASK register is used for this purpose. This
usually results in hardfaults that are properly handling by the
RTOS. Using the BASEPRI register will avoid these hardfault.
That is needed primarily for integration with some toolchains.

2
arch/arm/src/lpc17xx/Kconfig
View File

@ -540,7 +540,7 @@ config SDIO_WIDTH_D1_ONLY
---help---
Select 1-bit transfer mode. This may be selected to force the driver
operate with only a single data line (the default is to use all
4 SD data lines).Default: 4-bit transfer mode.
4 SD data lines).Default: 4-bit transfer mode.
endmenu

8
arch/mips/src/pic32mx/Kconfig
View File

@ -1076,8 +1076,8 @@ config PIC32MX_FETHIO
---help---
Ethernet I/O Pin Selection bit:
1 = Default Ethernet I/O Pins
0 = Alternate Ethernet I/O Pins
1 = Default Ethernet I/O Pins
0 = Alternate Ethernet I/O Pins
config PIC32MX_FMIIEN
int "Ethernet MII"
@ -1085,8 +1085,8 @@ config PIC32MX_FMIIEN
---help---
Ethernet MII Enable bit
1 = MII enabled
0 = RMII enabled
1 = MII enabled
0 = RMII enabled
endmenu

68
arch/z80/src/z180/Kconfig
View File

@ -55,26 +55,26 @@ config Z180_BANKAREA_VIRTBASE
NuttX Memory Organization:
Common Area 0: This area holds the common NuttX code that is
directly call-able from all application threads. Common Area
always starts at virtual address 0x0000 and extends to the
Bank Area
Common Area 0: This area holds the common NuttX code that is
directly call-able from all application threads. Common Area
always starts at virtual address 0x0000 and extends to the
Bank Area
Base Area: This area holds the common NuttX data (including the
share-able heap) that is accessible from all applications and
extends to Common Area 1.
Base Area: This area holds the common NuttX data (including the
share-able heap) that is accessible from all applications and
extends to Common Area 1.
NOTE: That is execution from RAM, the common NuttX code and
data may be contiguous and lie in the same region (either
Common Area 0 or the Bank Area). The two regions above would
apply in a ROM'ed system, where Common Area 1 is ROM and the
Base Area is RAM.
NOTE: That is execution from RAM, the common NuttX code and
data may be contiguous and lie in the same region (either
Common Area 0 or the Bank Area). The two regions above would
apply in a ROM'ed system, where Common Area 1 is ROM and the
Base Area is RAM.
Common Area 1: This area holds the code and data that is unique
to a particular task. his area extends to the end of the virtual
address space. All tasks share the same virtual Common Area 2
virtual address (but each has a unique mapping to different,
underlying physical addresses).
Common Area 1: This area holds the code and data that is unique
to a particular task. his area extends to the end of the virtual
address space. All tasks share the same virtual Common Area 2
virtual address (but each has a unique mapping to different,
underlying physical addresses).
config Z180_BANKAREA_PHYSBASE
hex "Physical Start of Bank Area"
@ -93,26 +93,26 @@ config Z180_COMMON1AREA_VIRTBASE
NuttX Memory Organization:
Common Area 0: This area holds the common NuttX code that is
directly call-able from all application threads. Common Area
always starts at virtual address 0x0000 and extends to the
Bank Area
Common Area 0: This area holds the common NuttX code that is
directly call-able from all application threads. Common Area
always starts at virtual address 0x0000 and extends to the
Bank Area
Base Area: This area holds the common NuttX data (including the
share-able heap) that is accessible from all applications and
extends to Common Area 1.
Base Area: This area holds the common NuttX data (including the
share-able heap) that is accessible from all applications and
extends to Common Area 1.
NOTE: That is execution from RAM, the common NuttX code and
data may be contiguous and lie in the same region (either
Common Area 0 or the Bank Area). The two regions above would
apply in a ROM'ed system, where Common Area 1 is ROM and the
Base Area is RAM.
NOTE: That is execution from RAM, the common NuttX code and
data may be contiguous and lie in the same region (either
Common Area 0 or the Bank Area). The two regions above would
apply in a ROM'ed system, where Common Area 1 is ROM and the
Base Area is RAM.
Common Area 1: This area holds the code and data that is unique
to a particular task. his area extends to the end of the virtual
address space. All tasks share the same virtual Common Area 2
virtual address (but each has a unique mapping to different,
underlying physical addresses).
Common Area 1: This area holds the code and data that is unique
to a particular task. his area extends to the end of the virtual
address space. All tasks share the same virtual Common Area 2
virtual address (but each has a unique mapping to different,
underlying physical addresses).
config Z180_PHYSHEAP_START
hex "Physical Start of Free Memory"