sergiotarxz/nuttx
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fix all occurrences of "the the" in documentation and comments

Browse Source
This commit is contained in:
Gregory Nutt 2013-08-27 09:40:19 -06:00
parent 0053ed9c37
commit f19af5572d
30 changed files with 36 additions and 36 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
configs/demo9s12ne64/README.txt
View File

@ -327,7 +327,7 @@ HCS12/DEMO9S12NEC64-specific Configuration Options
CONFIG_HCS12_NONBANKED - Indicates that the target systems does not
support banking. Only short calls are made; one fixed page is
presented the the paging window. Only 48Kb of FLASH is usable
presented in the paging window. Only 48Kb of FLASH is usable
in this configuration: pages 3e, 3d, then 3f will appear as a
contiguous address space in memory.

2
configs/ea3131/src/up_fillpage.c
View File

@ -198,7 +198,7 @@ struct pg_source_s
FAR struct mtd_dev_s *mtd;
/* This the the device geometry */
/* This the device geometry */
#ifdef CONFIG_DEBUG
FAR struct mtd_geometry_s geo;

2
configs/ea3152/src/up_fillpage.c
View File

@ -198,7 +198,7 @@ struct pg_source_s
FAR struct mtd_dev_s *mtd;
/* This the the device geometry */
/* This the device geometry */
#ifdef CONFIG_DEBUG
FAR struct mtd_geometry_s geo;

2
configs/eagle100/README.txt
View File

@ -84,7 +84,7 @@ CodeSourcery on Linux
If you select the CodeSourcery toolchain, the make system will assume that you
are running a Windows version of the toolchain. If you are running under Linux,
the the make will probably fail. The fix is to edit your Make.defs file and
the make will probably fail. The fix is to edit your Make.defs file and
use something like:
CROSSDEV = arm-none-eabi-

4
configs/freedom-kl25z/README.txt
View File

@ -139,10 +139,10 @@ mbed
1. Connect the KL25Z to the host PC using the USB connector labeled
SDA.
2. A new file system will appear call MBED; open it with Windows
2. A new file system will appear called MBED; open it with Windows
Explorer (assuming that you are using Windows).
3. Drag and drop nuttx.bin into the MBED window. This will load the
nuttx.bin binary into the the KL25Z. the MBED window will close
nuttx.bin binary into the KL25Z. The MBED window will close
then re-open and the KL25Z will be running the new code.
Using the Freescale SDA debugger is essentially the same. That

2
configs/lincoln60/src/up_buttons.c
View File

@ -211,7 +211,7 @@ xcpt_t up_irqbutton(int id, xcpt_t irqhandler)
}
else
{
/* Disable then then detach the the old interrupt handler */
/* Disable then detach the old interrupt handler */
up_disable_irq(irq);
(void)irq_detach(irq);

2
configs/lpc4330-xplorer/src/up_buttons.c
View File

@ -210,7 +210,7 @@ xcpt_t up_irqbutton(int id, xcpt_t irqhandler)
}
else
{
/* Disable then then detach the the old interrupt handler */
/* Disable then detach the old interrupt handler */
up_disable_irq(irq);
(void)irq_detach(irq);

2
configs/mikroe-stm32f4/README.txt
View File

@ -772,7 +772,7 @@ Where <subdir> is one of the following:
In the normal case (just 'make'), make will attempt to build both user-
and kernel-mode blobs more or less interleaved. This actual works!
However, for me it is very confusing so I prefer the above make command:
Make the user-space binaries first (pass1), then make the the kernel-space
Make the user-space binaries first (pass1), then make the kernel-space
binaries (pass2)
NOTES:

4
configs/mikroe-stm32f4/src/up_touchscreen.c
View File

@ -266,7 +266,7 @@ static int tc_poll(FAR struct file *filep, struct pollfd *fds, bool setup);
* Private Data
****************************************************************************/
/* This the the vtable that supports the character driver interface */
/* This the vtable that supports the character driver interface */
static const struct file_operations tc_fops =
{
@ -723,7 +723,7 @@ static int tc_waitsample(FAR struct tc_dev_s *priv,
}
}
/* Re-acquire the the semaphore that manages mutually exclusive access to
/* Re-acquire the semaphore that manages mutually exclusive access to
* the device structure. We may have to wait here. But we have our sample.
* Interrupts and pre-emption will be re-enabled while we wait.
*/

2
configs/mirtoo/README.txt
View File

@ -575,7 +575,7 @@ Analog Input
19 PGED3/VREF+/CVREF+/AN0/C3INC/RPA0/CTED1/PMD7/RA0 AIN PGA117 Vout
--- ------------------------------------------------ ----------------------------
The PGA117 driver can be enabled by setting the following the the nsh
The PGA117 driver can be enabled by setting the following the nsh
configuration:
CONFIG_ADC=y : Enable support for analog input devices

2
configs/mirtoo/src/up_adc.c
View File

@ -62,7 +62,7 @@
* 19 PGED3/VREF+/CVREF+/AN0/C3INC/RPA0/CTED1/PMD7/RA0 AIN PGA117 Vout
--- ------------------------------------------------ ----------------------------
*
* The PGA117 driver can be enabled by setting the following the the nsh
* The PGA117 driver can be enabled by setting the following the nsh
* configuration:
*
* CONFIG_ADC=y : Enable support for analog input devices

2
configs/mirtoo/src/up_leds.c
View File

@ -146,7 +146,7 @@ static const struct led_setting_s g_ledoffvalues[LED_NVALUES] =
{LED_OFF, LED_NC, 0},
};
/* If CONFIG_ARCH_LEDS is not defined, the the user can control the LEDs in
/* If CONFIG_ARCH_LEDS is not defined, then the user can control the LEDs in
* any way. The following array simply maps the PIC32MX_MIRTOO_LEDn
* index values to the correct LED pin configuration.
*/

2
configs/ne64badge/README.txt
View File

@ -434,7 +434,7 @@ HCS12/NE64BADGE-specific Configuration Options
CONFIG_HCS12_NONBANKED - Indicates that the target systems does not
support banking. Only short calls are made; one fixed page is
presented the the paging window. Only 48Kb of FLASH is usable
presented in the paging window. Only 48Kb of FLASH is usable
in this configuration: pages 3e, 3d, then 3f will appear as a
contiguous address space in memory.

2
configs/olimex-lpc1766stk/src/up_buttons.c
View File

@ -214,7 +214,7 @@ xcpt_t up_irqbutton(int id, xcpt_t irqhandler)
}
else
{
/* Disable then then detach the the old interrupt handler */
/* Disable then detach the old interrupt handler */
up_disable_irq(irq);
(void)irq_detach(irq);

2
configs/olimex-lpc1766stk/src/up_ssp.c
View File

@ -163,7 +163,7 @@ static void ssp_cdirqsetup(int irq, xcpt_t irqhandler)
}
else
{
/* Disable then then detach the the old interrupt handler */
/* Disable then detach the old interrupt handler */
up_disable_irq(irq);
(void)irq_detach(irq);

6
configs/open1788/README.txt
View File

@ -230,7 +230,7 @@ Using OpenOCD with the Olimex ARM-USB-OCD
Open1788 board.
/usr/local/share/openocd/scripts/target/lpc1788.cfg
This is the configuration file for the the LPC1788 target.
This is the configuration file for the LPC1788 target.
It just sets up a few parameters then sources lpc17xx.cfg
/usr/local/share/openocd/scripts/target/lpc17xx.cfg
@ -373,7 +373,7 @@ CONFIGURATION
In the normal case (just 'make'), make will attempt to build both user-
and kernel-mode blobs more or less interleaved. This actual works!
However, for me it is very confusing so I prefer the above make command:
Make the user-space binaries first (pass1), then make the the kernel-space
Make the user-space binaries first (pass1), then make the kernel-space
binaries (pass2)
NOTES:
@ -417,7 +417,7 @@ CONFIGURATION
System.map - Symbols in the kernel-space ELF file
Loading these .elf files with OpenOCD is tricky. It appears to me
that when nuttx_user.elf is loaded, it destroys the the nuttx image
that when nuttx_user.elf is loaded, it destroys the nuttx image
in FLASH. But loading the nuttx ELF does not harm the nuttx_user.elf
in FLASH. Conclusion: Always load nuttx_user.elf before nuttx.

2
configs/open1788/src/lpc17_buttons.c
View File

@ -238,7 +238,7 @@ xcpt_t up_irqbutton(int id, xcpt_t irqhandler)
}
else
{
/* Disable then then detach the the old interrupt handler */
/* Disable then detach the old interrupt handler */
up_disable_irq(irq);
(void)irq_detach(irq);

2
configs/pic32-starterkit/README.txt
View File

@ -240,7 +240,7 @@ PIN CONFIGURATIONS SIGNAL NAME ON-BOARD CONNE
MEB Connector
=============
The following table summarizes how the pins brought the the MEB through the
The following table summarizes how the pins brought the MEB through the
J2 on the Ethernet Starter Kit are mapped. This connect is J2 on the Ethernet
Starter Kit and J3 on the MEB.

2
configs/pic32-starterkit/src/up_leds.c
View File

@ -153,7 +153,7 @@ static const struct led_setting_s g_ledoffvalues[LED_NVALUES] =
{LED_OFF, LED_NC, LED_NC, LED_OFF},
};
/* If CONFIG_ARCH_LEDS is not defined, the the user can control the LEDs in
/* If CONFIG_ARCH_LEDS is not defined, then the user can control the LEDs in
* any way. The following array simply maps the PIC32MX_STARTERKIT_LEDn
* index values to the correct LED pin configuration.
*/

2
configs/pic32mx7mmb/README.txt
View File

@ -670,7 +670,7 @@ Where <subdir> is one of the following:
NOTE: The SD card should *not* be mounted under NSH *and* exported
by the mass storage device!!! That can result in corruption of the
SD card format. This is the sequence of commands that you should
used to work the the SD card safely:
use to work with the SD card safely:
mount -t vfat /dev/mmcsd0 /mnt/sdcard : Mount the SD card initially
...

2
configs/pic32mx7mmb/src/up_leds.c
View File

@ -156,7 +156,7 @@ static const struct led_setting_s g_ledoffvalues[LED_NVALUES] =
{LED_OFF, LED_NC, LED_NC, LED_OFF},
};
/* If CONFIG_ARCH_LEDS is not defined, the the user can control the LEDs in
/* If CONFIG_ARCH_LEDS is not defined, then the user can control the LEDs in
* any way. The following array simply maps the PIC32MX_PIC32MX7MMB_LEDn
* index values to the correct LED pin configuration.
*/

2
configs/pic32mx7mmb/src/up_spi.c
View File

@ -171,7 +171,7 @@ uint8_t pic32mx_spi1status(FAR struct spi_dev_s *dev, enum spi_dev_e devid)
{
ret = SPI_STATUS_PRESENT;
/* A high value indicates the the card is write protected. */
/* A high value indicates that the card is write protected. */
if (pic32mx_gpioread(GPIO_SD_WP))
{

4
configs/pic32mx7mmb/src/up_touchscreen.c
View File

@ -249,7 +249,7 @@ static int tc_poll(FAR struct file *filep, struct pollfd *fds, bool setup);
* Private Data
****************************************************************************/
/* This the the vtable that supports the character driver interface */
/* This the vtable that supports the character driver interface */
static const struct file_operations tc_fops =
{
@ -610,7 +610,7 @@ static int tc_waitsample(FAR struct tc_dev_s *priv,
}
}
/* Re-acquire the the semaphore that manages mutually exclusive access to
/* Re-acquire the semaphore that manages mutually exclusive access to
* the device structure. We may have to wait here. But we have our sample.
* Interrupts and pre-emption will be re-enabled while we wait.
*/

2
configs/sam3u-ek/README.txt
View File

@ -516,7 +516,7 @@ Configurations
In the normal case (just 'make'), make will attempt to build both user-
and kernel-mode blobs more or less interleaved. This actual works!
However, for me it is very confusing so I prefer the above make command:
Make the user-space binaries first (pass1), then make the the kernel-space
Make the user-space binaries first (pass1), then make the kernel-space
binaries (pass2)
NOTES:

4
configs/sama5d3x-ek/README.txt
View File

@ -401,7 +401,7 @@ Creating and Using NORBOOT
(gdb) mon go # And jump into NOR flash
The norboot program can also be configured to jump directly into
NOR FLASH with out requiring the the final halt and go, but since I
NOR FLASH without requiring the final halt and go, but since I
have been debugging the early boot sequence, the above sequence has
been most convenient for me.
@ -489,7 +489,7 @@ Serial Consoles
PB28 RXD1 PIO_USART1_RXD
PB26 CTS1 PIO_USART1_CTS
NOTE: Debug TX and RX pins also go the the ADM3312EARU, but I am
NOTE: Debug TX and RX pins also go to the ADM3312EARU, but I am
uncertain of the functionality.
-------------------------------

2
configs/stm32f4discovery/README.txt
View File

@ -1134,7 +1134,7 @@ Where <subdir> is one of the following:
In the normal case (just 'make'), make will attempt to build both user-
and kernel-mode blobs more or less interleaved. This actual works!
However, for me it is very confusing so I prefer the above make command:
Make the user-space binaries first (pass1), then make the the kernel-space
Make the user-space binaries first (pass1), then make the kernel-space
binaries (pass2)
NOTES:

2
configs/stm32f4discovery/elf/setenv.sh
View File

@ -69,7 +69,7 @@ export TOOLCHAIN_BIN="/cygdrive/c/Program Files (x86)/CodeSourcery/Sourcery G++
# toolchain.
#export TOOLCHAIN_BIN="${WD}/../misc/buildroot/build_arm_nofpu/staging_dir/bin"
# This the the Cygwin path to the location where I built genromfs. If you use
# This the Cygwin path to the location where I built genromfs. If you use
# the buildroot toolchain, then genromfs can probably be found in TOOLCHAIN_DIR
export GENROMFS_PATH="${WD}/../misc/buildroot/build_arm_nofpu/staging_dir/bin"

2
configs/stm32f4discovery/posix_spawn/setenv.sh
View File

@ -69,7 +69,7 @@ export TOOLCHAIN_BIN="/cygdrive/c/Program Files (x86)/CodeSourcery/Sourcery G++
# toolchain.
#export TOOLCHAIN_BIN="${WD}/../misc/buildroot/build_arm_nofpu/staging_dir/bin"
# This the the Cygwin path to the location where I built genromfs. If you use
# This the Cygwin path to the location where I built genromfs. If you use
# the buildroot toolchain, then genromfs can probably be found in TOOLCHAIN_DIR
export GENROMFS_PATH="${WD}/../misc/buildroot/build_arm_nofpu/staging_dir/bin"

2
configs/sure-pic32mx/src/pic32mx_spi.c
View File

@ -238,7 +238,7 @@ uint8_t pic32mx_spi2status(FAR struct spi_dev_s *dev, enum spi_dev_e devid)
{
ret = SPI_STATUS_PRESENT;
/* It seems that a high value indicates the the card is write
/* It seems that a high value indicates the card is write
* protected.
*/

2
configs/ubw32/src/up_leds.c
View File

@ -153,7 +153,7 @@ static const struct led_setting_s g_ledoffvalues[LED_NVALUES] =
{LED_OFF, LED_NC, LED_NC, LED_OFF},
};
/* If CONFIG_ARCH_LEDS is not defined, the the user can control the LEDs in
/* If CONFIG_ARCH_LEDS is not defined, then the user can control the LEDs in
* any way. The following array simply maps the PIC32MX_UBW32_LEDn
* index values to the correct LED pin configuration.
*/