Hi Fernando, as Hauke pointed out already, RIOT supports Ethernet devices in general but still needs support for the specific hardware used. For your device this would mean implementing the interfaces defined in netdev2.h [1] and netdev2_eth.h [2]. If you are willing to take on this task we're happy to support you with any questions arising and you can take a look how it is done for other existing Ethernet devices like the enc28j60 [3].
Best, Thomas [1] https://github.com/RIOT-OS/RIOT/blob/master/drivers/include/net/netdev2.h [2] https://github.com/RIOT-OS/RIOT/blob/master/drivers/include/net/netdev2_eth.h [3] https://github.com/RIOT-OS/RIOT/tree/master/drivers/enc28j60 > On Mar 21, 2016, at 10:49 AM, Hauke Petersen <hauke.peter...@fu-berlin.de> > wrote: > > Hi, > > we do have support for ethernet, but we don't have a device driver for the > lpc1768 phy, yet. Feel free to write one :-) > > Cheers, > Hauke > > > On 18.03.2016 20:50, Fernando Alberione wrote: >>> On 2016-03-18 13:05, Thomas Eichinger wrote: >>> Hi Fernando, >>> >>> the mbed-lpc1768 according to [1] doesn't have any network interfaces >>> as far as I see. Because of this there are no network drivers >>> implemented and ifconfig doesn't have anything to show. Do you use it >>> with any kind of extension board? >> Hi Thomas, >> >> Thanks for answering. >> >> I wanted to run the example using the mbed-lpc1768 ethernet device. It >> already has an integrated phy, so we just connected an rj-45 jack. >> >> Do you have support for ethernet devices in your stack? >> >> Regards, >> >> >> _______________________________________________ >> devel mailing list >> devel@riot-os.org >> https://lists.riot-os.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
