FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=release%2F9.3.0 2014-04-14T04:53:34Z 2014-04-14T04:53:34Z Pyun YongHyeon yongari@FreeBSD.org 2014-04-14T04:53:34Z urn:sha1:281cc1f4cc474b125baa2c1356b9a69a8f3beaae Increase the number of TX DMA segments from 32 to 35. It turned out 32 is not enough to support a full sized TSO packet. While I'm here fix a long standing bug introduced in r169632 in bce(4) where it didn't include L2 header length of TSO packet in the maximum DMA segment size calculation. 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. 2012-10-24T19:04:17Z Gavin Atkinson gavin@FreeBSD.org 2012-10-24T19:04:17Z urn:sha1:5ea65cf54e3d30c510bdff867eee7d219798b08c Align the PCI Express #defines with the style used for the PCI-X #defines. This has the advantage that it makes the names more compact, and also allows us to correct the non-uniform naming of the PCIM_LINK_* defines, making them all consistent amongst themselves. This is a mostly mechanical rename: s/PCIR_EXPRESS_/PCIER_/g s/PCIM_EXP_/PCIEM_/g s/PCIM_LINK_/PCIEM_LINK_/g In this MFC, #defines have been added for the old names to assist out-of-tree drivers. 2012-06-11T01:38:34Z Kevin Lo kevlo@FreeBSD.org 2012-06-11T01:38:34Z urn:sha1:c72ac85d6d183d2ea76bb68e2038defe3219b25d Fix a logic error when use PCIY_PMG capability Reviewed by: yongari 2011-05-03T19:51:29Z Marius Strobl marius@FreeBSD.org 2011-05-03T19:51:29Z urn:sha1:3fcb7a5365f9de7824a2b5f8e8ab159c8d3d79a0 (reporting IFM_LOOP based on BMCR_LOOP is left in place though as it might provide useful for debugging). For most mii(4) drivers it was unclear whether the PHYs driven by them actually support loopback or not. Moreover, typically loopback mode also needs to be activated on the MAC, which none of the Ethernet drivers using mii(4) implements. Given that loopback media has no real use (and obviously hardly had a chance to actually work) besides for driver development (which just loopback mode should be sufficient for though, i.e one doesn't necessary need support for loopback media) support for it is just dropped as both NetBSD and OpenBSD already did quite some time ago. - Let mii_phy_add_media() also announce the support of IFM_NONE. - Restructure the PHY entry points to use a structure of entry points instead of discrete function pointers, and extend this to include a "reset" entry point. Make sure any PHY-specific reset routine is always used, and provide one for lxtphy(4) which disables MII interrupts (as is done for a few other PHYs we have drivers for). This includes changing NIC drivers which previously just called the generic mii_phy_reset() to now actually call the PHY-specific reset routine, which might be crucial in some cases. While at it, the redundant checks in these NIC drivers for mii->mii_instance not being zero before calling the reset routines were removed because as soon as one PHY driver attaches mii->mii_instance is incremented and we hardly can end up in their media change callbacks etc if no PHY driver has attached as mii_attach() would have failed in that case and not attach a miibus(4) instance. Consequently, NIC drivers now no longer should call mii_phy_reset() directly, so it was removed from EXPORT_SYMS. - Add a mii_phy_dev_attach() as a companion helper to mii_phy_dev_probe(). The purpose of that function is to perform the common steps to attach a PHY driver instance and to hook it up to the miibus(4) instance and to optionally also handle the probing, addition and initialization of the supported media. So all a PHY driver without any special requirements has to do in its bus attach method is to call mii_phy_dev_attach() along with PHY-specific MIIF_* flags, a pointer to its PHY functions and the add_media set to one. All PHY drivers were updated to take advantage of mii_phy_dev_attach() as appropriate. Along with these changes the capability mask was added to the mii_softc structure so PHY drivers taking advantage of mii_phy_dev_attach() but still handling media on their own do not need to fiddle with the MII attach arguments anyway. - Keep track of the PHY offset in the mii_softc structure. This is done for compatibility with NetBSD/OpenBSD. - Keep track of the PHY's OUI, model and revision in the mii_softc structure. Several PHY drivers require this information also after attaching and previously had to wrap their own softc around mii_softc. NetBSD/OpenBSD also keep track of the model and revision on their mii_softc structure. All PHY drivers were updated to take advantage as appropriate. - Convert the mebers of the MII data structure to unsigned where appropriate. This is partly inspired by NetBSD/OpenBSD. - According to IEEE 802.3-2002 the bits actually have to be reversed when mapping an OUI to the MII ID registers. All PHY drivers and miidevs where changed as necessary. Actually this now again allows to largely share miidevs with NetBSD, which fixed this problem already 9 years ago. Consequently miidevs was synced as far as possible. - Add MIIF_NOMANPAUSE and mii_phy_flowstatus() calls to drivers that weren't explicitly converted to support flow control before. It's unclear whether flow control actually works with these but typically it should and their net behavior should be more correct with these changes in place than without if the MAC driver sets MIIF_DOPAUSE. Obtained from: NetBSD (partially) Reviewed by: yongari (earlier version), silence on arch@ and net@ 2011-03-23T13:10:15Z John Baldwin jhb@FreeBSD.org 2011-03-23T13:10:15Z urn:sha1:3b0a4aef967e33d85308e74b00c472820e173c7a pci_find_cap() instead. 2011-01-13T14:42:43Z John Baldwin jhb@FreeBSD.org 2011-01-13T14:42:43Z urn:sha1:932b56d24263f40b8992848c828f8594af41c1ec the lock instead of queueing it to a task. - Do not invoke jme_rxintr() to reclaim any unprocessed but received packets when shutting down the interface. Instead, just drop these packets to match the behavior of other drivers. - Hold the driver lock in the interrupt handler to avoid races with ioctl requests to down the interface. Reviewed by: yongari 2010-12-18T23:52:50Z Pyun YongHyeon yongari@FreeBSD.org 2010-12-18T23:52:50Z urn:sha1:4f1ff93a3b88264cd1b715368e1b2ef483ba7418 controller with Card Read Host Controller. These controllers are multi-function devices and have the same ethernet core of JMC250/JMC260. Starting from REVFM 5(chip full mask revision) controllers have the following features. o eFuse support o PCD(Packet Completion Deferring) o More advanced PHY power saving Because these controllers started to use eFuse, station address modified by driver is permanent as if it was written to EEPROM. If you have to change station address please save your controller default address to safe place before reprogramming it. There is no way to restore factory default station address. Many thanks to JMicron for continuing to support FreeBSD. HW donated by: JMicron 2010-12-18T23:26:38Z Pyun YongHyeon yongari@FreeBSD.org 2010-12-18T23:26:38Z urn:sha1:4d9ab34335e6398af78883ed3f78cec39388a406 number. 2010-12-18T23:24:59Z Pyun YongHyeon yongari@FreeBSD.org 2010-12-18T23:24:59Z urn:sha1:cd33cef72395bde1a42953b48e073ae53e0dcb07