385153aa98
the NIC drivers as well as the PHY drivers to take advantage of the mii_attach() introduced in r213878 to get rid of certain hacks. For the most part these were: - Artificially limiting miibus_{read,write}reg methods to certain PHY addresses; we now let mii_attach() only probe the PHY at the desired address(es) instead. - PHY drivers setting MIIF_* flags based on the NIC driver they hang off from, partly even based on grabbing and using the softc of the parent; we now pass these flags down from the NIC to the PHY drivers via mii_attach(). This got us rid of all such hacks except those of brgphy() in combination with bce(4) and bge(4), which is way beyond what can be expressed with simple flags. While at it, I took the opportunity to change the NIC drivers to pass up the error returned by mii_attach() (previously by mii_phy_probe()) and unify the error message used in this case where and as appropriate as mii_attach() actually can fail for a number of reasons, not just because of no PHY(s) being present at the expected address(es). Reviewed by: jhb, yongari |
||
---|---|---|
.. | ||
cryptocteon | ||
octe | ||
usb | ||
asm_octeon.S | ||
ciu.c | ||
cvmx_config.h | ||
files.octeon1 | ||
obio.c | ||
obiovar.h | ||
octeon_ds1337.c | ||
octeon_ebt3000_cf.c | ||
octeon_machdep.c | ||
octeon_mp.c | ||
octeon_pcmap_regs.h | ||
octeon_rnd.c | ||
octeon_rtc.c | ||
octopci_bus_space.c | ||
octopci.c | ||
octopcireg.h | ||
octopcivar.h | ||
std.octeon1 | ||
uart_bus_octeonusart.c | ||
uart_cpu_octeonusart.c | ||
uart_dev_oct16550.c |