FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=release%2F9.3.0 2013-03-09T00:39:54Z 2013-03-09T00:39:54Z Marius Strobl marius@FreeBSD.org 2013-03-09T00:39:54Z urn:sha1:03abd02e1efa33cbb430b395dfdf238e8f3a5f60 Mechanically substitute flags from historic mbuf allocator with malloc(9) flags in sys/dev. 2013-03-08T12:44:08Z Marius Strobl marius@FreeBSD.org 2013-03-08T12:44:08Z urn:sha1:5f9b80f2a5aeea8b789d8ff47266b59309aa4822 - Move reporting of failures to disable RX/TX MAC under bootverbose as at least the Saturn chips of 501-6738 cards may fail to do so the first time, which isn't fatal though. Reported by: Paul Keusemann - Explain why we don't enable infinite bursts on sparc64. - Given that these chips support memory write invalidate, make sure that it's enabled in the command register. Also make sure that PERR# and SERR# assertion is enabled. 2013-01-28T00:31:32Z Marius Strobl marius@FreeBSD.org 2013-01-28T00:31:32Z urn:sha1:07b40fe1facf114bb33dbc2454ef16e97369d7de - Check the return value of taskqueue_start_threads(). - At least the Saturn chips of 501-6738 cards need a delay after freezing the external GMII pins before the internal PHY is accessible again. So wait a bit after (un)freezing these. Also don't touch the other bits of that configuration register. [1] - Take advantage of nitems(). Reported and tested by: Paul Keusemann [1] 2012-11-12T07:34:05Z Dimitry Andric dim@FreeBSD.org 2012-11-12T07:34:05Z urn:sha1:7fb0f60ca2d6ed85fa149669427e57e3d2b2c7a9 Remove duplicate const specifiers in many drivers (I hope I got all of them, please let me know if not). Most of these are of the form: static const struct bzzt_type { [...list of members...] } const bzzt_devs[] = { [...list of initializers...] }; The second const is unnecessary, as arrays cannot be modified anyway, and if the elements are const, the whole thing is const automatically (e.g. it is placed in .rodata). I have verified this does not change the binary output of a full kernel build (except for build timestamps embedded in the object files). Reviewed by: yongari, marius 2011-12-31T14:12:12Z Hans Petter Selasky hselasky@FreeBSD.org 2011-12-31T14:12:12Z urn:sha1:0105e7b57ec82d3d157edb9f4322f29f05d54f6e Use DEVMETHOD_END to mark end of device methods. Remove superfluous device methods. Add some missing __FBSBID() macros. 2011-07-13T18:52:11Z Marius Strobl marius@FreeBSD.org 2011-07-13T18:52:11Z urn:sha1:fcdbb666c0604a087a6c2114aab20131b39b6fd1 checking IFF_DRV_RUNNING and simplify the code. This also involves holding the driver lock in the rx_ch callout. - Just use ifp instead of sc->sc_ifp. Submitted by: jhb (mostly) 2011-07-12T13:22:17Z Marius Strobl marius@FreeBSD.org 2011-07-12T13:22:17Z urn:sha1:5f8a9ae4a9cb54686da6aff5c4bba79f9edae591 - Consistently use the newly introduced sc_mac_rxcfg throughout the driver instead of reading the old content of CAS_MAC_RX_CONF. - Increment if_iqdrops instead of if_ierrors in case of RX buffer allocation failure. - According to the Cassini datasheet the RX MAC should also be disabled in cas_setladrf() before changing its configuration. - Add error messages to gem_disable_{r,t}x() and take advantage of these throughout the driver instead of duplicating their functionality all over the place. 2011-04-22T09:44:01Z Marius Strobl marius@FreeBSD.org 2011-04-22T09:44:01Z urn:sha1:a34f0477884dd9e657e623964d1cf3b51ede3bd7 Submitted by: brucec 2010-11-22T22:06:30Z Marius Strobl marius@FreeBSD.org 2010-11-22T22:06:30Z urn:sha1:36334c57d978e290c86d2d9e52332934c1dd0ea4 - Fix compilation with CAS_DEBUG defined. 2010-10-15T14:52:11Z Marius Strobl marius@FreeBSD.org 2010-10-15T14:52:11Z urn: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