src/sys/dev/bm, branch release/10.1.0FreeBSD source treehttps://cgit-dev.freebsd.org/src/atom?h=release%2F10.1.02012-12-04T09:32:43ZMechanically 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.
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.
- Import the common MII bitbang'ing code from NetBSD and convert drivers to2011-11-01T16:13:59ZMarius Stroblmarius@FreeBSD.org2011-11-01T16:13:59Zurn:sha1:8c1093fc50ab084b2ddd4750290a23d62616e0b6
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.
Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).
Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
Remove some hacks to handle strange behavior of LXT 970 PHYs now better2011-05-12T14:27:28ZNathan Whitehornnwhitehorn@FreeBSD.org2011-05-12T14:27:28Zurn:sha1:6ac75c91b7669497c9e5efc24a4b9256c038db29
handled in miibus after r221812. Thanks to marius@ for piecing this
together!
Do not use Open Firmware to open the device and instead program its start2011-05-06T03:26:24ZNathan Whitehornnwhitehorn@FreeBSD.org2011-05-06T03:26:24Zurn:sha1:cc734417b376e4a745197380a22f3e1e3464aa88
on our own. This prevents hangs at boot when using a bm(4) NIC where the
cable is not plugged in at boot time.
Obtained from: NetBSD
MFC after: 1 week
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
Use if_maddr_rlock()/if_maddr_runlock() rather than IF_ADDR_LOCK()/2009-06-26T11:45:06ZRobert Watsonrwatson@FreeBSD.org2009-06-26T11:45:06Zurn:sha1:eb956cd041f956275522092d6ba66671356ff84f
IF_ADDR_UNLOCK() across network device drivers when accessing the
per-interface multicast address list, if_multiaddrs. This will
allow us to change the locking strategy without affecting our driver
programming interface or binary interface.
For two wireless drivers, remove unnecessary locking, since they
don't actually access the multicast address list.
Approved by: re (kib)
MFC after: 6 weeks
Fix bm_shutdown() KOBJ method to correspond to return int, as it should.2009-02-04T22:16:27ZNathan Whitehornnwhitehorn@FreeBSD.org2009-02-04T22:16:27Zurn:sha1:6b122703cc1fcf73cb1565d2c016c9c094cc290c
Found by: Andriy Gapon
Change the way we enable the BMAC cell in macio. Instead of calling the2008-10-13T17:33:55ZNathan Whitehornnwhitehorn@FreeBSD.org2008-10-13T17:33:55Zurn:sha1:1209e7e53874146070d0a77c862e48f174e4cd5c
macio's enable-enet word, which apparently does nothing on some machines,
open an OF instance of the ethernet controller. This fixes cold booting
from disk on my Blue & White G3.
MFC after: 3 days