summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat
-rw-r--r--misc/buildroot/configs/README.txt4
-rw-r--r--misc/tools/README.txt2
-rwxr-xr-xnuttx/ChangeLog2
-rw-r--r--nuttx/Documentation/NXGraphicsSubsystem.html2
-rw-r--r--nuttx/Documentation/NuttX.html2
-rw-r--r--nuttx/Documentation/NuttXDemandPaging.html2
-rw-r--r--nuttx/Documentation/NuttXLinks.html2
-rw-r--r--nuttx/TODO2
-rw-r--r--nuttx/configs/mcu123-lpc214x/README.txt2
-rw-r--r--nuttx/configs/mirtoo/README.txt4
-rw-r--r--nuttx/configs/pcblogic-pic32mx/README.txt4
-rw-r--r--nuttx/configs/pic32-starterkit/README.txt4
-rw-r--r--nuttx/configs/pic32mx7mmb/README.txt4
-rw-r--r--nuttx/configs/sure-pic32mx/README.txt4
-rw-r--r--nuttx/configs/ubw32/README.txt4
15 files changed, 22 insertions, 22 deletions
diff --git a/misc/buildroot/configs/README.txt b/misc/buildroot/configs/README.txt
index f7d6a0fab..bfffff293 100644
--- a/misc/buildroot/configs/README.txt
+++ b/misc/buildroot/configs/README.txt
@@ -262,7 +262,7 @@ Q: Some of my libraries like GMP and MPFR are in non-standard locations the
checking for correct version of mpfr.h... no
configure: error: Building GCC requires GMP 4.1+ and MPFR 2.3.0+.
-A: http://tech.groups.yahoo.com/group/nuttx/message/1160
+A: https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/1160
"I think that you can specify the path to GMP and MPFR. I think that GCC
has some special configuration command line options to support this. I
@@ -361,7 +361,7 @@ Building GDB Under Cygwin
^^^^^^^^^^^^^^^^^^^^^^^^^
This can be tricking, but it has been done. See this message sequence for
- http://tech.groups.yahoo.com/group/nuttx/message/726 . Apparently there
+ https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/726 . Apparently there
are some incompatibilities with Cygwin 1.7 that require an additional
patch. See http://old.nabble.com/-RFA--windows-nat.c%3A-Cygwin%3A-Port-to-Cygwin-1.7-td27735619.html
diff --git a/misc/tools/README.txt b/misc/tools/README.txt
index 7eaa77fff..6bdedee13 100644
--- a/misc/tools/README.txt
+++ b/misc/tools/README.txt
@@ -198,7 +198,7 @@ http://uvc.de/posts/linux-kernel-configuration-tool-mconf-under-windows.html
[The remainder of the text in this section is for historical interest only]
-From http://tech.groups.yahoo.com/group/nuttx/message/2900:
+From https://groups.yahoo.com/neo/groups/nuttx/conversations/messages/2900:
"The build was quite simple:
diff --git a/nuttx/ChangeLog b/nuttx/ChangeLog
index 6c4273342..e88e4ba09 100755
--- a/nuttx/ChangeLog
+++ b/nuttx/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/nuttx/Documentation/NXGraphicsSubsystem.html b/nuttx/Documentation/NXGraphicsSubsystem.html
index 5c1c1ed81..c8c3e0b83 100644
--- a/nuttx/Documentation/NXGraphicsSubsystem.html
+++ b/nuttx/Documentation/NXGraphicsSubsystem.html
@@ -3706,7 +3706,7 @@ sudo ln -s libXext.so.6.4.0 libXext.so
<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="http://tech.groups.yahoo.com/group/nuttx/files">files</a>.
+ that can be found in NuttX <a href="https://groups.yahoo.com/neo/groups/nuttx/files">files</a>.
</small></p>
</li>
<li><p>
diff --git a/nuttx/Documentation/NuttX.html b/nuttx/Documentation/NuttX.html
index a4f4cd3a8..039c85451 100644
--- a/nuttx/Documentation/NuttX.html
+++ b/nuttx/Documentation/NuttX.html
@@ -1165,7 +1165,7 @@
</table>
<p>
- Most NuttX-related discussion occurs on the <a href="http://tech.groups.yahoo.com/group/nuttx/" target="_top"><i>Yahoo!</i> NuttX group</a>.
+ 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.
</p>
diff --git a/nuttx/Documentation/NuttXDemandPaging.html b/nuttx/Documentation/NuttXDemandPaging.html
index b5fa2f9f2..afaaacf86 100644
--- a/nuttx/Documentation/NuttXDemandPaging.html
+++ b/nuttx/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:
- <a href="http://tech.groups.yahoo.com/group/nuttx/message/213">http://tech.groups.yahoo.com/group/nuttx/message/213</a>.
+ <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?
diff --git a/nuttx/Documentation/NuttXLinks.html b/nuttx/Documentation/NuttXLinks.html
index f278d8376..1ed75096a 100644
--- a/nuttx/Documentation/NuttXLinks.html
+++ b/nuttx/Documentation/NuttXLinks.html
@@ -21,7 +21,7 @@
<li><a href="http://www.nuttx.org/Documentation/NuttX.html" target="main">Home</a></li>
<li><a href="http://sourceforge.net/projects/nuttx/develop" target="_top">SourceForge</a></li>
<li><a href="http://freshmeat.net/projects/nuttx/" target="_top">FreshMeat</a></li>
- <li><a href="http://tech.groups.yahoo.com/group/nuttx/" target="_top">Forum</a></li>
+ <li><a href="https://groups.yahoo.com/neo/groups/nuttx/info" target="_top">Forum</a></li>
<li><a href="https://www.ohloh.net/p/nuttx" target="_top">Ohloh</a></li>
<li><a href="http://www.oschina.net/p/nuttx" target="_top">OSChina</a></li>
<li><a href="http://sourceforge.net/projects/nuttx/files/" target="_top">Downloads</a></li>
diff --git a/nuttx/TODO b/nuttx/TODO
index 37e5be03c..c6145174f 100644
--- a/nuttx/TODO
+++ b/nuttx/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/nuttx/configs/mcu123-lpc214x/README.txt b/nuttx/configs/mcu123-lpc214x/README.txt
index 8ce4534ab..228499438 100644
--- a/nuttx/configs/mcu123-lpc214x/README.txt
+++ b/nuttx/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/nuttx/configs/mirtoo/README.txt b/nuttx/configs/mirtoo/README.txt
index 150017b56..80723b82f 100644
--- a/nuttx/configs/mirtoo/README.txt
+++ b/nuttx/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/nuttx/configs/pcblogic-pic32mx/README.txt b/nuttx/configs/pcblogic-pic32mx/README.txt
index 323d51d3e..5d329b672 100644
--- a/nuttx/configs/pcblogic-pic32mx/README.txt
+++ b/nuttx/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/nuttx/configs/pic32-starterkit/README.txt b/nuttx/configs/pic32-starterkit/README.txt
index 0f0a545e4..e02a593ba 100644
--- a/nuttx/configs/pic32-starterkit/README.txt
+++ b/nuttx/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/nuttx/configs/pic32mx7mmb/README.txt b/nuttx/configs/pic32mx7mmb/README.txt
index c9024461f..d48a852c1 100644
--- a/nuttx/configs/pic32mx7mmb/README.txt
+++ b/nuttx/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/nuttx/configs/sure-pic32mx/README.txt b/nuttx/configs/sure-pic32mx/README.txt
index 0c0b99427..52ba8f54e 100644
--- a/nuttx/configs/sure-pic32mx/README.txt
+++ b/nuttx/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/nuttx/configs/ubw32/README.txt b/nuttx/configs/ubw32/README.txt
index e3e2a511c..e1a0a3785 100644
--- a/nuttx/configs/ubw32/README.txt
+++ b/nuttx/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.
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-16 05:57:07 +0000