Remove all references to the Yahoo group.

This commit is contained in:
Gregory Nutt 2018-04-15 17:15:48 -06:00
parent 949adaa4c9
commit e470846356
28 changed files with 61 additions and 92 deletions

View File

@ -12,7 +12,7 @@
<h1><big><font color="#3c34ec">
<i>NX Graphics Subsystem</i>
</font></big></h1>
<p>Last Updated: January 21, 2018</p>
<p>Last Updated: April 15, 2018</p>
</td>
</tr>
</table>
@ -3719,8 +3719,8 @@ sudo ln -s libXext.so.6.4.0 libXext.so
<p><small>
<b>NOTE</b>: There is a workaround in this case:
You can build for 32-bit execution on a 64-bit machine by adding <code>-m3</code> to the <code>CFLAGS</code> and <code>-m32 -m elf_i386</code> to the <code>LDFLAGS</code>.
See the patch file <code>0001-Quick-hacks-to-build-sim-nsh-ostest-on-x86_64-as-32-.patch</code>
that can be found in NuttX <a href="https://groups.yahoo.com/neo/groups/nuttx/files">files</a>.
The configuration/build system will do this for you;
you simply need to select <code>CONFIG_SIM_M32=y</code> in your configuration file.
</small></p>
</li>
<li><p>

View File

@ -8,7 +8,7 @@
<tr align="center" bgcolor="#e4e4e4">
<td>
<h1><big><font color="#3c34ec"><i>NuttX RTOS</i></font></big></h1>
<p>Last Updated: April 9, 2018</p>
<p>Last Updated: April 15, 2018</p>
</td>
</tr>
</table>
@ -1403,9 +1403,9 @@
</table>
<p>
Most NuttX-related discussion occurs on the <a href="https://groups.yahoo.com/neo/groups/nuttx/info" target="_top"><i>Yahoo!</i> NuttX group</a>.
You are cordially invited to <a href="http://groups.yahoo.com/group/nuttx/join" target="_top">join</a>.
I make a special effort to answer any questions and provide any help that I can.
Most NuttX-related discussion occurs on the <a href="https://groups.google.com/forum/#!forum/nuttx"><i>Google</i> NuttX group</a>.
You are cordially invited to join.
In most cases, I make a special effort to answer any questions and provide any help that I can.
</p>
<table width ="100%">

View File

@ -128,8 +128,6 @@
<p>
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:
<a href="https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/213">https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/213</a>.
</p>
<p>
What kind of platforms can support NuttX on-demang paging?

View File

@ -8,7 +8,7 @@
<tr align="center" bgcolor="#e4e4e4">
<td>
<h1><big><font color="#3c34ec"><i>NuttX README Files</i></font></big></h1>
<p>Last Updated: April 9, 2018</p>
<p>Last Updated: April 15, 2018</p>
</td>
</tr>
</table>

15
TODO
View File

@ -1720,8 +1720,6 @@ o Libraries (libc/, libm/)
providing patches, but we found it easier just to switch the
math library."
Ref: https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/7805
UPDATE: 2015-09-01: A fix for the noted problems with asin()
has been applied.
2016-07-30: Numerous fixes and performance improvements from
@ -2073,11 +2071,7 @@ o Graphics Subsystem (graphics/)
Title: WIDE-FONT SUPPORT
Description: Wide fonts are not currently supported by the NuttX graphics sub-
system. There is some discussion here:
https://groups.yahoo.com/neo/groups/nuttx/conversations/topics/3507
http://www.nuttx.org/doku.php?id=wiki:graphics:wide-fonts
system.
Status: Open
Priority: Low for many, but I imagine higher in countries that use wide fonts
@ -2137,9 +2131,7 @@ o Other drivers (drivers/)
Title: ADD SUPPORT FOR CONTROL-C
Description: Add support for control-C interrupts and perhaps other
interrupts generated from a keyboard. See this thread for
additional thoughts:
https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/15761
interrupts generated from a keyboard.
Status: Open
Priority: Low. This would make working with tasks at the NSH terminal
more like working with processes via a Bash shell. That is
@ -2286,8 +2278,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: https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/1261
On suggested change is:
One suggested change is:
ldr r1, [r0, #(4*REG_CPSR)] /* Fetch the stored CPSR value */
msr spsr_cxsf, r1 /* Set the CPSR */

View File

@ -5,7 +5,7 @@
* Copyright (C) 2015 Filament - www.filament.com
* Author: Matt Thompson <mthompson@hexwave.com>
* Author: Alan Carvalho de Assis <acassis@gmail.com>
* Author: Gregory Nutt <spudarnia@yahoo.com>
* Author: Gregory Nutt <gnutt@nuttx.org>
*
* References:
* SAMD/SAML Series Data Sheet

View File

@ -3,7 +3,7 @@
*
* Copyright (C) 2016 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>
* Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@yahoogroups.com>
* Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@googlegroups.com>
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions

View File

@ -3,7 +3,7 @@
#
# Copyright (C) 2017 Gregory Nutt. All rights reserved.
# Author: Gregory Nutt <gnutt@nuttx.org>
# Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@yahoogroups.com>
# Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@googlegroups.com>
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions

View File

@ -3,7 +3,7 @@
#
# Copyright (C) 2016, 2017 Gregory Nutt. All rights reserved.
# Author: Gregory Nutt <gnutt@nuttx.org>
# Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@yahoogroups.com>
# Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@googlegroups.com>
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions

View File

@ -4,7 +4,7 @@
#
# Copyright (C) 2016 Gregory Nutt. All rights reserved.
# Author: Gregory Nutt <gnutt@nuttx.org>
# Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@yahoogroups.com>
# Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@googlegroups.com>
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions

View File

@ -3,7 +3,7 @@
*
* Copyright (C) 2016 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>
* Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@yahoogroups.com>
* Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@googlegroups.com>
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions

View File

@ -3,7 +3,7 @@
*
* Copyright (C) 2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>
* Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@yahoogroups.com>
* Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@googlegroups.com>
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions

View File

@ -3,7 +3,7 @@
#
# Copyright (C) 2012 Gregory Nutt. All rights reserved.
# Author: Gregory Nutt <gnutt@nuttx.org>
# Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@yahoogroups.com>
# Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@googlegroups.com>
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions

View File

@ -3,7 +3,7 @@
*
* Copyright (C) 2016, 2018 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>
* Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@yahoogroups.com>
* Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@googlegroups.com>
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions

View File

@ -3,7 +3,7 @@
*
* Copyright (C) 2016 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>
* Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@yahoogroups.com>
* Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@googlegroups.com>
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions

View File

@ -3,7 +3,7 @@
*
* Copyright (C) 2016 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>
* Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@yahoogroups.com>
* Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@googlegroups.com>
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions

View File

@ -3,7 +3,7 @@
*
* Copyright (C) 2016, 2018 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>
* Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@yahoogroups.com>
* Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@googlegroups.com>
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions

View File

@ -3,7 +3,7 @@
*
* Copyright (C) 2016-2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>
* Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@yahoogroups.com>
* Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@googlegroups.com>
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions

View File

@ -3,7 +3,7 @@
*
* Copyright (C) 2016 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>
* Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@yahoogroups.com>
* Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@googlegroups.com>
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions

View File

@ -3,7 +3,7 @@
*
* Copyright (C) 2016 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>
* Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@yahoogroups.com>
* Alan Carvalho de Assis acassis@gmail.com [nuttx] <nuttx@googlegroups.com>
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions

View File

@ -139,10 +139,9 @@ LPC21ISP (Linux)
----------------
(ca. 2008)
I use the lpc21isp tool to load NuttX into FLASH. That tool is available
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.
I use the lpc21isp tool to load NuttX into FLASH. In the older version
1.60 of lpc21isp for Linux, I had to make several changes. This changesi
are shown in lpc21ips-1.60.diff.
I use the script lpc21isp.sh to perform the actual download. You will
probably have to make some changes to this script in order to use it.

View File

@ -388,9 +388,7 @@ Toolchains
Another option is the mips-elf toolchain used with the Pinguino project. This
is a relatively current mips-elf GCC and should provide free C++ support as
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:
https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/1821
http://wiki.pinguino.cc/index.php/Main_Page#Download .
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,10 +424,9 @@ Toolchains
Rename: kseg1_datamem to kseg1_data_mem
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 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.
for non-NuttX code that resides in the unused Microchip libraries. You will
have to solve at least this undefined symbol problem if you want to used thei
XC32 toolchain.
Windows Native Toolchains
-------------------------

View File

@ -222,9 +222,7 @@ Toolchains
Another option is the mips-elf toolchain used with the Pinguino project. This
is a relatively current mips-elf GCC and should provide free C++ support as
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:
https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/1821
http://wiki.pinguino.cc/index.php/Main_Page#Download .
See also configs/mirtoo/README.txt. There is an experimental (untested)
configuration for the Mirtoo platform in that directory.
@ -249,10 +247,9 @@ Toolchains
Rename: kseg1_datamem to kseg1_data_mem
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 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.
for non-NuttX code that resides in the unused Microchip libraries. You will
have to solve at least this undefined symbol problem if you want to used the
XC32 toolchain.
Windows Native Toolchains
-------------------------

View File

@ -438,9 +438,7 @@ Toolchains
Another option is the mips-elf toolchain used with the Pinguino project. This
is a relatively current mips-elf GCC and should provide free C++ support as
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:
https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/1821
http://wiki.pinguino.cc/index.php/Main_Page#Download .
See also configs/mirtoo/README.txt. There is an experimental (untested)
configuration for the Mirtoo platform in that directory.
@ -465,10 +463,9 @@ Toolchains
Rename: kseg1_datamem to kseg1_data_mem
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 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.
for non-NuttX code that resides in the unused Microchip libraries. You will
have to solve at least this undefined symbol problem if you want to used the
XC32 toolchain.
Windows Native Toolchains
-------------------------

View File

@ -156,9 +156,6 @@ Toolchains
Pinguino project. This is a relatively current mips-elf GCC and should
provide free C++ support as 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:
https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/1821
It should be a simple matter to adapt to other toolchains by modifying the
Make.defs file include ineach configuration.
@ -229,10 +226,9 @@ Toolchains
Rename: kseg1_datamem to kseg1_data_mem
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 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.
for non-NuttX code that resides in the unused Microchip libraries. You will
have to solve at least this undefined symbol problem if you want to used the
XC32 toolchain.
Update: There have since been several successful uses of XC32 toolchains with
NuttX. XC32 is still not supported for this board, but you can see the README.txt

View File

@ -257,20 +257,20 @@
*/
#ifndef CONFIG_STM32F4DISBB
# define GPIO_USART2_RX GPIO_USART2_RX_1 /* PA3 */
# define GPIO_USART2_TX GPIO_USART2_TX_1 /* PA2 */
# define GPIO_USART2_RX GPIO_USART2_RX_1 /* PA3, P1 pin 13 */
# define GPIO_USART2_TX GPIO_USART2_TX_1 /* PA2, P1 pin 14 */
#endif
/* USART3:
*
* Used in pseudoterm configuration and also with the BT860 HCI UART.
* RTS/CTS Flow control support is need by the HCI UART.
* RTS/CTS Flow control support is needed by the HCI UART.
*/
#define GPIO_USART3_TX GPIO_USART3_TX_1 /* PB10 */
#define GPIO_USART3_RX GPIO_USART3_RX_1 /* PB11 */
#define GPIO_USART3_CTS GPIO_USART3_CTS_1 /* PB13 */
#define GPIO_USART3_RTS GPIO_USART3_RTS_1 /* PB14 */
#define GPIO_USART3_TX GPIO_USART3_TX_1 /* PB10, P1 pin 34 (also MP45DT02 CLK_IN) */
#define GPIO_USART3_RX GPIO_USART3_RX_1 /* PB11, P1 pin 35 */
#define GPIO_USART3_CTS GPIO_USART3_CTS_1 /* PB13, P1 pin 37 */
#define GPIO_USART3_RTS GPIO_USART3_RTS_1 /* PB14, P1 pin 38 */
/* USART6:
*
@ -278,8 +278,8 @@
* for USART6. This is the preferred serial console for use with the STM32F4DIS-BB.
*/
#define GPIO_USART6_RX GPIO_USART6_RX_1 /* PC7 */
#define GPIO_USART6_TX GPIO_USART6_TX_1 /* PC6 */
#define GPIO_USART6_RX GPIO_USART6_RX_1 /* PC7 (also I2S3_MCK and P2 pin 48) */
#define GPIO_USART6_TX GPIO_USART6_TX_1 /* PC6 (also P2 pin 47) */
/* PWM
*

View File

@ -293,9 +293,7 @@ Toolchains
Another option is the mips-elf toolchain used with the Penguino project. This
is a relatively current mips-elf GCC and should provide free C++ support as
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:
https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/1821
http://wiki.pinguino.cc/index.php/Main_Page#Download .
See also configs/mirtoo/README.txt. There is an experimental (untested)
configuration for the Mirtoo platform in that directory.
@ -320,10 +318,9 @@ Toolchains
Rename: kseg1_datamem to kseg1_data_mem
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 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.
for non-NuttX code that resides in the unused Microchip libraries. You will
have to solve at least this undefined symbol problem if you want to used the
XC32 toolchain.
Windows Native Toolchains
-------------------------

View File

@ -231,9 +231,7 @@ Toolchains
Another option is the mips-elf toolchain used with the Pinguino project. This
is a relatively current mips-elf GCC and should provide free C++ support as
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:
https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/1821
http://wiki.pinguino.cc/index.php/Main_Page#Download .
See also configs/mirtoo/README.txt. There is an experimental (untested)
configuration for the Mirtoo platform in that directory.
@ -259,10 +257,9 @@ Toolchains
Rename: kseg1_datamem to kseg1_data_mem
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 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.
for non-NuttX code that resides in the unused Microchip libraries. You will
have to solve at least this undefined symbol problem if you want to used the
XC32 toolchain.
Windows Native Toolchains
-------------------------