Gregory Nutt 33085cb309 Networking: The network device list was protected by a re-entrant semaphore. With the recent change to support network device callback, the network stack needs to access the network device list too. Some drivers, however, run the network stack from the interrupt level -- this is bad but a fact in the current state. Of course,those drivers are unable to take the semaphore and will assert. ... The solution here is to eliminate the device devices semaphore altogether. This eliminates netdev_semtake() and netdev_semgive() and replaces them with net_lock() and net_unlock() which have larger scope as needed for this purpose.		2015-05-31 08:34:03 -06:00
..
Kconfig	Networking: Fix issues with UDP packet length and checksum calculations when IPv6 is selected	2015-01-23 09:33:18 -06:00
Make.defs	IPv6: Separate function that converts prefix lengths to a netmask	2015-02-06 08:11:09 -06:00
net_chksum.c	Networking: Fix issues with UDP packet length and checksum calculations when IPv6 is selected	2015-01-23 09:33:18 -06:00
net_dsec2tick.c	…
net_dsec2timeval.c	Suffer the consequences of moving struct timeval to its correct location	2015-02-15 15:18:35 -06:00
net_ipv6_maskcmp.c	Remove inclusion of some un-necessary header files.	2015-02-06 08:50:53 -06:00
net_ipv6_pref2mask.c	Remove inclusion of some un-necessary header files.	2015-02-06 08:50:53 -06:00
net_lock.c	UDP Networking: Misc fixes to get the last changes working + cleanup	2015-05-29 14:32:56 -06:00
net_timeval2dsec.c	Networking: setsockopt() fails when setting timeouts to values less that an 100 msec. That is because the timeout is limited to stops of 1 decisecond and because the conversion of structure timeval was truncating the microsecond remainder. The utility net_timeval2dsec now accespts and option to determin how it handles the remainder: truncate, discarding the remainder, use the remainder to round to the closed decisecond value, or use any non-zero remainder to the next larger whole decisecond value.	2015-05-29 07:17:15 -06:00
utils.h	Networking: The network device list was protected by a re-entrant semaphore. With the recent change to support network device callback, the network stack needs to access the network device list too. Some drivers, however, run the network stack from the interrupt level -- this is bad but a fact in the current state. Of course,those drivers are unable to take the semaphore and will assert.	2015-05-31 08:34:03 -06:00