diff --git a/ChangeLog b/ChangeLog index 6c42733427d..e88e4ba0958 100755 --- a/ChangeLog +++ b/ChangeLog @@ -1278,7 +1278,7 @@ board (Contributed by Dave Marples). * sched/sem_wait.c and sem_waitirq.c: Eliminate a race condition that can occur when a semaphore wait is interrupt by a signal. - (see email thread: http://tech.groups.yahoo.com/group/nuttx/message/530) + (see email thread: https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/530) * drivers/mtd/at45db.c: Add a driver for the Atmel AT45DB161D 4Mbit SPI FLASH part (untested on initial check-in). * arch/arm/src/lm3s and arch/arm/include/lm3s: Corrections for the diff --git a/Documentation/NXGraphicsSubsystem.html b/Documentation/NXGraphicsSubsystem.html index 5c1c1ed812a..c8c3e0b83b1 100644 --- a/Documentation/NXGraphicsSubsystem.html +++ b/Documentation/NXGraphicsSubsystem.html @@ -3706,7 +3706,7 @@ sudo ln -s libXext.so.6.4.0 libXext.so NOTE: There is a workaround in this case: You can build for 32-bit execution on a 64-bit machine by adding -m3 to the CFLAGS and -m32 -m elf_i386 to the LDFLAGS. See the patch file 0001-Quick-hacks-to-build-sim-nsh-ostest-on-x86_64-as-32-.patch - that can be found in NuttX files. + that can be found in NuttX files.

  • diff --git a/Documentation/NuttX.html b/Documentation/NuttX.html index a4f4cd3a8ab..39777f9ab25 100644 --- a/Documentation/NuttX.html +++ b/Documentation/NuttX.html @@ -1165,7 +1165,7 @@

    - Most NuttX-related discussion occurs on the Yahoo! NuttX group. + Most NuttX-related discussion occurs on the Yahoo! NuttX group. You are cordially invited to join. I make a special effort to answer any questions and provide any help that I can.

    @@ -2310,6 +2310,7 @@ nsh> on-board LED and button support and a serial console available on LEUART0. A single configuration is available using the NuttShell NSH and the LEUART0 serial console. + DMA and USART-based SPI supported are included, but not fully tested.

    Refer to the EFM32 Gecko Starter Kit README.txt file for further information. diff --git a/Documentation/NuttXDemandPaging.html b/Documentation/NuttXDemandPaging.html index b5fa2f9f2a4..afaaacf8626 100644 --- a/Documentation/NuttXDemandPaging.html +++ b/Documentation/NuttXDemandPaging.html @@ -129,7 +129,7 @@ This document summarizes the design of NuttX on-demand paging. This feature permits embedded MCUs with some limited RAM space to execute large programs from some non-random access media. This feature was first discussed in this email thread: - http://tech.groups.yahoo.com/group/nuttx/message/213. + https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/213.

    What kind of platforms can support NuttX on-demang paging? diff --git a/Documentation/NuttXLinks.html b/Documentation/NuttXLinks.html index f278d8376b3..1ed75096ab3 100644 --- a/Documentation/NuttXLinks.html +++ b/Documentation/NuttXLinks.html @@ -21,7 +21,7 @@

  • Home
  • SourceForge
  • FreshMeat
    • -
  • Forum
    • +
  • Forum
  • Ohloh
  • OSChina
  • Downloads
    • diff --git a/README.txt b/README.txt index 23b190bc454..9510637ceac 100644 --- a/README.txt +++ b/README.txt @@ -150,6 +150,24 @@ Downloading from Repositories https://sourceforge.net/p/nuttx/git + Configuring the Cone + + Set your identity: + + git config --global user.name "My Name" + git config --global user.email my.name@example.com + + Colorized diffs are much easier to read: + + git config --global color.branch auto + git config --global color.diff auto + git config --global color.interactive auto + git config --global color.status auto + + Checkout other settings + + git config --list + Cloning NuttX Inside Cygwin If you are cloning the NuttX repository, it is recommended to avoid diff --git a/TODO b/TODO index 37e5be03cc3..c6145174f6a 100644 --- a/TODO +++ b/TODO @@ -1406,7 +1406,7 @@ o ARM (arch/arm/) interrupt, the stack pointer may increment and possibly overflow. This can happen only under conditions of continuous interrupts. - See this email thread: http://tech.groups.yahoo.com/group/nuttx/message/1261 + See this email thread: https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/1261 On suggested change is: ldr r1, [r0, #(4*REG_CPSR)] /* Fetch the stored CPSR value */ diff --git a/configs/Kconfig b/configs/Kconfig index dad113ed322..9941eaf6368 100755 --- a/configs/Kconfig +++ b/configs/Kconfig @@ -985,7 +985,7 @@ config BOARD_CUSTOM_BUTTONS bool "Custom board buttons" default n select ARCH_HAVE_BUTTONS - select ARCH__BUTTONS + select ARCH_BUTTONS config BOARD_CUSTOM_IRQBUTTONS bool "Custom Board IRQ buttons" diff --git a/configs/efm32-g8xx-stk/README.txt b/configs/efm32-g8xx-stk/README.txt index ade1f7c6e9c..958e35c0f48 100644 --- a/configs/efm32-g8xx-stk/README.txt +++ b/configs/efm32-g8xx-stk/README.txt @@ -48,6 +48,8 @@ STATUS (probably because UART0 is used with the board controller???). Pins are not available for other U[S]ARTs on the board. + DMA and USART-based SPI supported are included, but not yet tested. + 2014-10-29: Calibrated the delays loops. 2014-10-29: The start-up time is long -- about a second. I have traced diff --git a/configs/mcu123-lpc214x/README.txt b/configs/mcu123-lpc214x/README.txt index 8ce4534ab98..22849943886 100644 --- a/configs/mcu123-lpc214x/README.txt +++ b/configs/mcu123-lpc214x/README.txt @@ -146,7 +146,7 @@ LPC21ISP (Linux) (ca. 2008) I use the lpc21isp tool to load NuttX into FLASH. That tool is available -in the files section at http://tech.groups.yahoo.com/group/lpc21isp/. In +in the files section at https://groups.yahoo.com/neo/groups/lpc21isp/info. In the older version 1.60 of lpc21isp for Linux, I had to make several changes. This changes are shown in lpc21ips-1.60.diff. diff --git a/configs/mirtoo/README.txt b/configs/mirtoo/README.txt index 150017b56f9..80723b82f06 100644 --- a/configs/mirtoo/README.txt +++ b/configs/mirtoo/README.txt @@ -390,7 +390,7 @@ Toolchains well. This toolchain can be downloded from the Pinguino website: http://wiki.pinguino.cc/index.php/Main_Page#Download . There is some general information about using the Pinguino mips-elf toolchain in this thread: - http://tech.groups.yahoo.com/group/nuttx/message/1821 + https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/1821 Support for the Pinguino mips-elf toolchain has been included in the Mirtoo configurations. Use one of these configuration options to select the Pinguino @@ -426,7 +426,7 @@ Toolchains Even then, there are more warnings from the linker and some undefined symbols for non-NuttX code that resides in the unused Microchip libraries. See this - email thread at http://tech.groups.yahoo.com/group/nuttx/message/1458 for more + email thread at https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/1458 for more information. You will have to solve at least this undefined symbol problem if you want to used the XC32 toolchain. diff --git a/configs/pcblogic-pic32mx/README.txt b/configs/pcblogic-pic32mx/README.txt index 323d51d3e82..5d329b6725d 100644 --- a/configs/pcblogic-pic32mx/README.txt +++ b/configs/pcblogic-pic32mx/README.txt @@ -220,7 +220,7 @@ Toolchains well. This toolchain can be downloded from the Pinguino website: http://wiki.pinguino.cc/index.php/Main_Page#Download . There is some general information about using the Pinguino mips-elf toolchain in this thread: - http://tech.groups.yahoo.com/group/nuttx/message/1821 + https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/1821 See also configs/mirtoo/README.txt. There is an experimental (untested) configuration for the Mirtoo platform in that directory. @@ -246,7 +246,7 @@ Toolchains Even then, there are more warnings from the linker and some undefined symbols for non-NuttX code that resides in the unused Microchip libraries. See this - email thread at http://tech.groups.yahoo.com/group/nuttx/message/1458 for more + email thread at https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/1458 for more information. You will have to solve at least this undefined symbol problem if you want to used the XC32 toolchain. diff --git a/configs/pic32-starterkit/README.txt b/configs/pic32-starterkit/README.txt index 0f0a545e43d..e02a593ba3d 100644 --- a/configs/pic32-starterkit/README.txt +++ b/configs/pic32-starterkit/README.txt @@ -436,7 +436,7 @@ Toolchains well. This toolchain can be downloded from the Pinguino website: http://wiki.pinguino.cc/index.php/Main_Page#Download . There is some general information about using the Pinguino mips-elf toolchain in this thread: - http://tech.groups.yahoo.com/group/nuttx/message/1821 + https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/1821 See also configs/mirtoo/README.txt. There is an experimental (untested) configuration for the Mirtoo platform in that directory. @@ -462,7 +462,7 @@ Toolchains Even then, there are more warnings from the linker and some undefined symbols for non-NuttX code that resides in the unused Microchip libraries. See this - email thread at http://tech.groups.yahoo.com/group/nuttx/message/1458 for more + email thread at https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/1458 for more information. You will have to solve at least this undefined symbol problem if you want to used the XC32 toolchain. diff --git a/configs/pic32mx7mmb/README.txt b/configs/pic32mx7mmb/README.txt index c9024461f63..d48a852c1a8 100644 --- a/configs/pic32mx7mmb/README.txt +++ b/configs/pic32mx7mmb/README.txt @@ -204,7 +204,7 @@ Toolchains well. This toolchain can be downloded from the Pinguino website: http://wiki.pinguino.cc/index.php/Main_Page#Download . There is some general information about using the Pinguino mips-elf toolchain in this thread: - http://tech.groups.yahoo.com/group/nuttx/message/1821 + https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/1821 See also configs/mirtoo/README.txt. There is an experimental (untested) configuration for the Mirtoo platform in that directory. @@ -230,7 +230,7 @@ Toolchains Even then, there are more warnings from the linker and some undefined symbols for non-NuttX code that resides in the unused Microchip libraries. See this - email thread at http://tech.groups.yahoo.com/group/nuttx/message/1458 for more + email thread at https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/1458 for more information. You will have to solve at least this undefined symbol problem if you want to used the XC32 toolchain. diff --git a/configs/sure-pic32mx/README.txt b/configs/sure-pic32mx/README.txt index 0c0b994270a..52ba8f54e9c 100644 --- a/configs/sure-pic32mx/README.txt +++ b/configs/sure-pic32mx/README.txt @@ -291,7 +291,7 @@ Toolchains well. This toolchain can be downloded from the Penguino website: http://wiki.pinguino.cc/index.php/Main_Page#Download . There is some general information about using the Penguino mips-elf toolchain in this thread: - http://tech.groups.yahoo.com/group/nuttx/message/1821 + https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/1821 See also configs/mirtoo/README.txt. There is an experimental (untested) configuration for the Mirtoo platform in that directory. @@ -317,7 +317,7 @@ Toolchains Even then, there are more warnings from the linker and some undefined symbols for non-NuttX code that resides in the unused Microchip libraries. See this - email thread at http://tech.groups.yahoo.com/group/nuttx/message/1458 for more + email thread at https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/1458 for more information. You will have to solve at least this undefined symbol problem if you want to used the XC32 toolchain. diff --git a/configs/ubw32/README.txt b/configs/ubw32/README.txt index e3e2a511c65..e1a0a3785c8 100644 --- a/configs/ubw32/README.txt +++ b/configs/ubw32/README.txt @@ -229,7 +229,7 @@ Toolchains well. This toolchain can be downloded from the Pinguino website: http://wiki.pinguino.cc/index.php/Main_Page#Download . There is some general information about using the Pinguino mips-elf toolchain in this thread: - http://tech.groups.yahoo.com/group/nuttx/message/1821 + https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/1821 See also configs/mirtoo/README.txt. There is an experimental (untested) configuration for the Mirtoo platform in that directory. @@ -256,7 +256,7 @@ Toolchains Even then, there are more warnings from the linker and some undefined symbols for non-NuttX code that resides in the unused Microchip libraries. See this - email thread at http://tech.groups.yahoo.com/group/nuttx/message/1458 for more + email thread at https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/1458 for more information. You will have to solve at least this undefined symbol problem if you want to used the XC32 toolchain.