src-test2/sys/dev/msk, branch release/10.0.0

MFC r257490:

2013-11-05T06:48:12Z

Perform media change after setting IFF_DRV_RUNNING flag. Without it, driver would ignore the first link state update if controller already established a link. Approved by: re (glebius)

- Merge from r249476: Ensure that PCI bus BUS_GET_DMA_TAG() method sees

2013-05-30T12:16:55Z

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 after: 1 week

- Correct mispellings of the word occurrence

2013-04-17T11:40:10Z

Submitted by: Christoph Mallon (via private mail)

RX checksum offloading on old Yukon controllers seem to cause more

2013-02-27T05:03:35Z

problems. Disable RX checksum offloading on controllers that don't use new descriptor format but give chance to enable it with ifconfig(8).

Mechanically substitute flags from historic mbuf allocator with

2012-12-04T09:32:43Z

malloc(9) flags in sys/dev.

For Yukon II controllers that implement optional temperature sensor

2012-04-25T02:46:13Z

and voltage sensor, TWSI is used to get sensor data. msk(4) does not monitor these sensors and interrupt for TWSI completion is disabled by default. However, due to unknown reason, the TWSI completion interrupt fires and it resulted in interrupt storm. To fix it, acknowledges the TWSI completion interrupt if driver see the event. Given that not all Yukon II controllers show the issue it could be a silicon bug which does not honor interrupt masking. Probably the right way to address the issue is disabling automatic TWSI cycle initiation against these sensors. It would be even better to implement reading voltage/temperature from the NIC but it requires access to National LM80 through TWSI and documentation to do that is not available yet(probably will never happen). Reported by: jhb Tested by: jhb MFC after: 2 weeks

ether_ifattach() sets if_mtu to ETHERMTU, don't bother set it again

2012-01-07T09:41:57Z

Reviewed by: yongari

Increase wait time for OP_TCPSTART command processing. It seems

2011-12-19T19:02:36Z

100us is not enough to ensure prefetch unit work.

- There's no need to overwrite the default device method with the default

2011-11-22T21:28:20Z

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.

Enable 64bit DMA addressing support for all msk(4) controllers.

2011-11-16T19:25:26Z

Unnecessarily complex LE format used on Marvell controller was main reason not to enable 64bit DMA addressing in driver. If high 32bit address of DMA address of TX/RX buffer is changed, driver has to generate a new LE. In TX path, driver will keep track of lastly used high 32bit address of DMA address and generate a new LE whenever it sees high address change in the DMA address. In RX path, driver will always use two LEs to specify 64bit DMA address of RX buffer. If the high 32bit address of DMA address of RX buffer is the same as previous DMA address of RX buffer, driver does not have to use two LEs but driver will use two LEs for simplicity in RX ring management. One of draw back for switching to 64bit DMA addressing is that the large amount of LEs are used to specify 64bit DMA address such that number of available LEs for TX/RX buffers are considerably reduced. To mitigate the issue, increase number of available LEs from 256 to 384 for TX and from 256 to 512 for RX. For 32bit architectures, msk(4) does not use 64bit DMA addressing to save resources. Tested by: das