Freescale fec phy driver

[ ] fec fethernet eth0: Freescale FEC PHY driver [SMSC LAN/LAN] Note that the SMSC PHY driver is picked up here, and that specific driver implements a different phy_read_status() callback due to how the PHY operates. The PHY driver also overrides the config_init() callback to perform some PHY-specific initialization.  · The boot process block at the information “eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=, irq=-1) Sending DHCP requests.” for a long time. The information displays on the console means what? Now I can not make sure if there is something wrong with the software or the hardware or both.  · On Tue, at +, Andrew Lunn wrote: On Thu, at PM +, Matthias Schiffer wrote: On some SoCs like www.doorway.ru6UL it is common to use the same MDIO bus for PHYs.

Tell FEC it's ready, interrupt when done, * it's the last BD of the frame, and to put the CRC on the end. */. status |= (BD_ENET_TX_READY | BD_ENET_TX_TC); bdp- cbd_sc = cpu_to_fec16 (status); /* If this was the last BD in the ring, start at the beginning again. */. bdp = fec_enet_get_nextdesc (last_bdp, txq- bd);. Check our new training course. and Creative Commons CC-BY-SA. lecture and lab materials. [ ] fec fethernet eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=fetherne, irq=-1) Here, the Generic PHY driver has been selected, which will use the MII_BMSR register contents to determine the Link status and parameters. You might want to make sure that your board selects the.

Nov we observe on a few devices the ethernet "swinging" > or toggling: > [ ] fec fethernet eth0: Freescale FEC PHY driver. Nov 4 drivers/net/ethernet/freescale/fec_main.c | 24 2 include/linux/mlx5/driver.h | 20 include/linux/phy.h | 4 kernel/bpf/arraymap.c. Dec eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=, irq=-1) Sending DHCP.