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

Update comments and README

This commit is contained in:
Gregory Nutt 2014-11-24 07:25:40 -06:00
parent 8de38d719a
commit 6a3a2f466c
3 changed files with 16 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ChangeLog
View File

@ -9052,7 +9052,7 @@
netdev_txnotify.c which, in turn, for changes to arp/arp_send.c, netdev_txnotify.c which, in turn, for changes to arp/arp_send.c,
icmp/icmp_ping.c, socket/net_sendfile.c, recvfrom.c, sendto.c, icmp/icmp_ping.c, socket/net_sendfile.c, recvfrom.c, sendto.c,
tcp/tcp_send_buffered.c, and tcp_send_unbuffered.c (2014-11-23). tcp/tcp_send_buffered.c, and tcp_send_unbuffered.c (2014-11-23).
* arch/arm/src/kl/chip/kl_i2c.h: "I2C header file for the Freescale KL * arch/arm/src/kl/chip/kl_i2c.h: I2C header file for the Freescale KL
family. From Alan Carvalho de Assis (2014-11-23). family. From Alan Carvalho de Assis (2014-11-23).
* include/nuttx/fs/fs.h: Fix typo in confiditional compilation. From * include/nuttx/fs/fs.h: Fix typo in conditional compilation. From
Alan Carvalho de Assis (2014-11-23). Alan Carvalho de Assis (2014-11-23).

15
configs/sama5d3-xplained/README.txt
View File

@ -2907,7 +2907,17 @@ Configurations
the warning in the section "Information Common to All Configurations" the warning in the section "Information Common to All Configurations"
for further information. for further information.
3. You will almost certainly need to adapt this configuration to 3. This configuration executes out of SDRAM flash and is loaded into
SDRAM from NAND, Serial DataFlash, SD card or from a TFTPC sever via
U-Boot or BareBox. Data also is positioned in SDRAM.
I did most testing with nuttx.bin on an SD card. These are the
commands that I used to boot NuttX from the SD card:
U-Boot> fatload mmc 0 0x20008000 nuttx.bin
U-Boot> go 0x20008040
4. You will almost certainly need to adapt this configuration to
work in your network environment. I did all testing with a work in your network environment. I did all testing with a
single 10.0.0.xx network and a 4+1 port switch: single 10.0.0.xx network and a 4+1 port switch:
@ -2915,7 +2925,8 @@ Configurations
- Target GMAC IP: 10.0.0.2 - Target GMAC IP: 10.0.0.2
- Target EMAC IP: 10.0.0.3 - Target EMAC IP: 10.0.0.3
Host, EMAC, and GMAC were all connected using a switch. Host PC, EMAC, and GMAC were all connected using an Ethernet
switch to the same 255.255.255.0 network.
STATUS: STATUS:

3
net/netdev/netdev_findbyaddr.c
View File

@ -184,8 +184,7 @@ FAR struct net_driver_s *netdev_findbyaddr(const net_ipaddr_t ripaddr)
} }
#else #else
/* If there is only a single, registered network interface, then the /* If there is only a single, registered network interface, then the
* decision is pretty easy. Use that device and its default router * decision is pretty easy.
* address.
*/ */
return g_netdevices; return g_netdevices;