mbed-os

Commit Graph

Author	SHA1	Message	Date
jeromecoutant	5612dac3b7	TARGET_STM_EMAC astyle	2018-06-29 17:11:50 +01: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

5612dac3b7

TARGET_STM_EMAC astyle

2018-06-29 17:11:50 +01: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

2 Commits (mbed-os-5.9)