src-test2/sys/dev/sk, branch release/9.2.0

MFC: r251133

2013-06-09T12:51:42Z

- Merge from r249476: Ensure that PCI bus BUS_GET_DMA_TAG() method sees the actual PCI device which makes the request for DMA tag, instead of some descendant of the PCI device, by creating a pass-through trampoline. - Sprinkle const on tables. - Use NULL instead of 0 for pointers. - Take advantage of nitems().

MFC: r243857 (partial)

2013-03-09T00:39:54Z

Mechanically substitute flags from historic mbuf allocator with malloc(9) flags in sys/dev.

MFC r226173, r227843, r227848 and r227908:

2011-12-31T14:12:12Z

Use DEVMETHOD_END to mark end of device methods. Remove superfluous device methods. Add some missing __FBSBID() macros.

Allocate the DMA memory shared between the host and the controller as

2011-03-11T22:21:12Z

coherent. MFC after: 2 weeks

Fix a long standing bug in programming station address for Yukon

2010-11-06T22:07:22Z

controllers. sk(4) never reprogrammed station address for Yukon controllers so overriding station address with ifconfig(8) was not possible. Fix the bug by reprogramming all registers that control station address, flow-control and virtual station address. Virtual station address has no use at this moment since driver does not make use of fail over feature. Tested by: "Mikhail T." aldan.algebra.com> MFC after: 1 week

If we got an invalid station address, generate random address. This

2010-11-06T21:54:32Z

might be caused by broken BIOS. Reported by: "Mikhail T." aldan.algebra.com> MFC after: 1 week

Convert the PHY drivers to honor the mii_flags passed down and convert

2010-10-15T14:52:11Z

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

Some revision of Yukon controller generates corrupted frame when TX

2010-07-09T21:21:08Z

checksum offloading is enabled. The frame has a valid checksum value so payload might be modified during TX checksum calculation. Disable TX checksum offloading but give users chance to enable it when they know their controller works without problems with TX checksum offloading. Reported by: Andrzej Tobola iem dot pw dot edu dot pl>

Take a step towards removing if_watchdog/if_timer. Don't explicitly set

2009-11-06T14:55:01Z

if_watchdog/if_timer to NULL/0 when initializing an ifnet. if_alloc() sets those members to NULL/0 already.

Use if_maddr_rlock()/if_maddr_runlock() rather than IF_ADDR_LOCK()/

2009-06-26T11:45:06Z

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