Boards which run Zephyr like Arduino 101 and quark_se_c1000_devboard typically do not have an ethernet port (but has USB port). It would be helpful (for testing zephyr / linux network stack interoperablity etc) to enumerate the zephyr board as a network card onto a Linux host.
So on the host side the Zephyr device should come up as a network interface (one of either ECM or EEM USB class), so that we can can assign an IP using ifconfig.
On the device side, we need a class driver, which should interface to the low/level interface of zephyr network stack. Basically it should be able to hand-off packets from the USB side to zephyr network stack and vice versa.
Reported by Jithu Joseph:
Boards which run Zephyr like Arduino 101 and quark_se_c1000_devboard typically do not have an ethernet port (but has USB port). It would be helpful (for testing zephyr / linux network stack interoperablity etc) to enumerate the zephyr board as a network card onto a Linux host.
So on the host side the Zephyr device should come up as a network interface (one of either ECM or EEM USB class), so that we can can assign an IP using ifconfig.
On the device side, we need a class driver, which should interface to the low/level interface of zephyr network stack. Basically it should be able to hand-off packets from the USB side to zephyr network stack and vice versa.
(Imported from Jira ZEP-1279)