mbed-os

Commit Graph

Author	SHA1	Message	Date
jeromecoutant	6391b7f2fa	TARGET_STM_EMAC astyle	2018-06-27 15:00:51 +02:00
Mika Leppänen	de72090d26	Changed STM emac driver to loop RX frame reading	2018-05-23 12:24:06 +03:00
Kevin Bracey	fbd920777b	Add extra labels for Freescale & STM EMAC drivers Just checking "does the chip have an EMAC" doesn't work - there are targets using those chips which do not have an Ethernet connector and don't provide the necessary surrounding infrastructure (eg DISCO_F429ZI, not providing the board emac config call, and HEXIWEAR not providing PHY info). Make the targets that actually do want EMAC define their own local Freescale_EMAC and STM_EMAC labels, and move the drivers into the corresponding TARGET_ directories, removing the #ifdefs.	2018-05-23 12:24:06 +03:00

Author

SHA1

Message

Date

jeromecoutant

6391b7f2fa

TARGET_STM_EMAC astyle

2018-06-27 15:00:51 +02:00

Mika Leppänen

de72090d26

Changed STM emac driver to loop RX frame reading

2018-05-23 12:24:06 +03:00

Kevin Bracey

fbd920777b

Add extra labels for Freescale & STM EMAC drivers

Just checking "does the chip have an EMAC" doesn't work - there are
targets using those chips which do not have an Ethernet connector and
don't provide the necessary surrounding infrastructure (eg DISCO_F429ZI,
not providing the board emac config call, and HEXIWEAR not providing PHY
info).

Make the targets that actually do want EMAC define their own local
Freescale_EMAC and STM_EMAC labels, and move the drivers into
the corresponding TARGET_ directories, removing the #ifdefs.

2018-05-23 12:24:06 +03:00

3 Commits (cb000ceeab036e3da6f16dbd28c473ed2cc0edea)