src/sys/dev/tsec, branch release/10.1.0FreeBSD source treehttps://cgit-dev.freebsd.org/src/atom?h=release%2F10.1.02014-05-15T16:11:06ZMFC r2614102014-05-15T16:11:06ZIan Leporeian@FreeBSD.org2014-05-15T16:11:06Zurn:sha1:359c68281f130a91637dbe0f7fe4f9ba4da79e58
Follow r261352 by updating all drivers which are children of simplebus
to check the status property in their probe routines.
MFC r257991, r257992, 257993, 2585042013-12-11T22:36:20ZAndreas Toblerandreast@FreeBSD.org2013-12-11T22:36:20Zurn:sha1:c471eee3e16a6a316f7e1e04701f296bb10e38f5
r257991:
Consolidate Apple firmware hacks and improve them by switching on the
presence of mac-io devices in the tree, which uniquely identifies Apple
hardware.
r257992:
Allow OF_decode_addr() to also be able to map resources on big-endian
devices. To this end, make PCI device detection rely on the device_type
field rather than name, as per the standard.
r257993:
Make tsec work with the device tree present on the RB800. The previous code
assumed that the MDIO bus was a direct child of the Ethernet interface. It
may not be and indeed on many device trees is not. While here, add proper
locking for MII transactions, which may be on a bus shared by several MACs.
r258504:
Save and restore the trap vectors when doing OF calls on pSeries machines.
It turned out that on pSeries machines the call into OF modified the trap
vectors and this made further behaviour unpredictable.
With this commit I'm now able to boot multi user on a network booted
environment on my IntelliStation 285. This is a POWER5+ machine.
Mechanically substitute flags from historic mbuf allocator with2012-12-04T09:32:43ZGleb Smirnoffglebius@FreeBSD.org2012-12-04T09:32:43Zurn:sha1:c6499eccad497913a5025fbde8ae76da70e08043
malloc(9) flags in sys/dev.
Do not reinitialise the interface if it is already running, this prevents the2012-05-09T00:56:11ZAndrew Thompsonthompsa@FreeBSD.org2012-05-09T00:56:11Zurn:sha1:afceeed7033f1a6a5d9b572b61a4c614c7138d73
bootp+nfs code from working as it calls init on each dhcp send and rx fails to
start in time.
The DEVICE_POLLING dereference of sc->tsec_ifp needs to be checked for null2012-05-08T21:09:03ZAndrew Thompsonthompsa@FreeBSD.org2012-05-08T21:09:03Zurn:sha1:335181759e1ca72e0c5103ca8cc2e5ffd6f500eb
first or this will panic. Condense three blocks that check sc->tsec_ifp into
one while I am here.
Respect phy-handle property in Ethernet nodes of the device tree.2012-03-04T19:22:52ZRafal Jaworowskiraj@FreeBSD.org2012-03-04T19:22:52Zurn:sha1:aa15e881bb453670d9155ace6c4b1885b15056e1
This lets specify whereabouts of the parent PHY for a given MAC node
(and get rid of ugly kludges in mge(4) and tsec(4)).
Obtained from: Semihalf
MFC after: 1 week
ether_ifattach() sets if_mtu to ETHERMTU, don't bother set it again2012-01-07T09:41:57ZKevin Lokevlo@FreeBSD.org2012-01-07T09:41:57Zurn:sha1:5bbe0c5357ab1559478babc8c2cf244cff5e98b7
Reviewed by: yongari
- There's no need to overwrite the default device method with the default2011-11-22T21:28:20ZMarius Stroblmarius@FreeBSD.org2011-11-22T21:28:20Zurn:sha1:4b7ec27007570e0ce4fe9dbb447e7afc131b487a
one. Interestingly, these are actually the default for quite some time
(bus_generic_driver_added(9) since r52045 and bus_generic_print_child(9)
since r52045) but even recently added device drivers do this unnecessarily.
Discussed with: jhb, marcel
- While at it, use DEVMETHOD_END.
Discussed with: jhb
- Also while at it, use __FBSDID.
Don't use the MAC address in the device tree if it's all zeroes2011-01-28T23:40:13ZMarcel Moolenaarmarcel@FreeBSD.org2011-01-28T23:40:13Zurn:sha1:df0437ca6f17fad39f2f7f4e1359b0cd45b021ea
(i.e. 00-00-00-00-00-00). Use the currently programmed address
instead.
While here, simplify the function.
Convert the PHY drivers to honor the mii_flags passed down and convert2010-10-15T14:52:11ZMarius Stroblmarius@FreeBSD.org2010-10-15T14:52:11Zurn:sha1:8e5d93dbb40452863b266a378868255bf986af67
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