Saehie ParK e6dbd3d903 Networking: Fix network device name assignment logic for the case of the local loopback device. There is only one local loopback network device and it is unnumbered

2015-08-25 20:03:25 -06:00

..

Kconfig

Fix references to the no-longer-existent misc/ directory in comments, README files, and documentation

2015-06-28 08:08:57 -06:00

Make.defs

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

netdev_carrier.c

…

netdev_count.c

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

netdev_default.c

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

netdev_findbyaddr.c

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

netdev_findbyname.c

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

netdev_foreach.c

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

netdev_ioctl.c

Networking: Fix some compilation issues noted with network is build with CONFIG_BUILD_KERNEL

2015-07-05 11:18:56 -06:00

netdev_register.c

Networking: Fix network device name assignment logic for the case of the local loopback device. There is only one local loopback network device and it is unnumbered

2015-08-25 20:03:25 -06:00

netdev_rxnotify.c

net/: Lots of build problems introduced into multiple NIC support. Many places where conditional logic based on CONFIG_NETDEV_MULTINIC is confused with CONFIG_NET_MULTILINK. Lots of code changed with IPv6 that was never compiled with MULTINIC enabled. Still some problem with parameter passing.

2015-02-09 18:15:34 -06:00

netdev_txnotify.c

Extend device specific callbacks to ICMPv6 and ARP. Fix some IPv6 compilation errors that have crept in

2015-05-27 11:39:44 -06:00

netdev_unregister.c

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

netdev_verify.c

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

netdev.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