summaryrefslogtreecommitdiffstats
path: root/sys/dev/fxp
Commit message (Collapse)AuthorAgeFilesLines
* Correct commentimp2005-06-061-2/+1
|
* Remove some variables the last commit stopped using so the code compiles.brooks2005-06-061-2/+2
|
* The PCI bus code saves/restores these config registers now.imp2005-06-052-20/+0
|
* Be more conservative when enabling extended features. There are fxp(4)mux2005-04-222-3/+7
| | | | | | NICs out there that have an utterly bogus revision ID. Reported by: Denis Shaposhnikov <dsh@vlink.ru>
* Add a microcode to implement receive bundling for 82551 chipsets withmux2005-04-213-20/+152
| | | | | | | a revision ID of 0x0f (D102 E-step). MFC after: 2 weeks Tested by: pav
* Enable extended RFDs and TCBs, and thus checksum offloading, formux2005-04-211-2/+1
| | | | | | | | | | | latest 82550 and 82551 chipsets (revision IDs 0x0e, 0x0f and 0x10). We were only enabling it for revisions 0x0c and 0x0d, now it's enabled for any 8255x NIC with a revision ID bigger than 0x0c. It should be safe, and this is what Intel does in their open source driver. MFC after: 2 weeks Tested by: Pavel Lobach lobach_pavel at mail dot ru
* Unload and destroy the TX DMA maps before destroying the DMA tagmux2005-03-161-4/+3
| | | | | | they're attached to, not after. Spotted by: Coverity via sam
* - Encapsulate the code responsible for initializing a new TX descriptormux2005-03-072-191/+190
| | | | | | | from an mbuf into the fxp_encap() function, as done in other drivers. - Don't waste time calling bus_dmamap_load_mbuf() if we know the mbuf chain is too long to fit in a TX descriptor, call m_defrag() first. - Convert fxp(4) to use bus_dmamap_load_mbuf_sg().
* Cleanup: u_intXX_t -> uintX_t conversion.mux2005-03-063-110/+110
|
* Use BUS_PROBE_DEFAULT for pci probe return valueimp2005-03-051-1/+1
|
* Add support for fxp(4) cards found in Sony FS570 laptops.mux2005-03-051-0/+1
| | | | Submitted by: Gavin Atkinson <gavin.atkinson@ury.york.ac.uk>
* Fix the panic recently reported on -current@ occuring when configuringmux2005-03-031-8/+13
| | | | | | | | | | | | a vlan interface attached to a fxp(4) card when it has not been initialized yet. We now set the links from our internel TX descriptor structure to the TX command blocks at attach time rather than at init time. While I'm here, slightly improve the style in fxp_attach(). PR: kern/78112 Reported by: Gavin Atkinson <gavin.atkinson@ury.york.ac.uk> and others Tested by: flz, Gavin Atkinson <gavin.atkinson@ury.york.ac.uk> MFC after: 1 week
* Fix a stupid bogon from myself, sc->revision wasn't initialized whenmux2005-02-271-10/+10
| | | | | | | | | | | | | testing it to know whether we should enable the 82503 serial mode... Move code to the right location and disallow the use of the 82503 serial mode if the sc->revision field is 0 again. This makes fxp(4) work correctly with ATMEL 350 93C46 cards (3 port 82559 based with a 82555 PHY), as well as with the older ATMEL 220 93C46 (same flavour) and with the even older 10Mbps-only 82557 cards with the 82503 serial interface. Tested by: Andre Albsmeier <andrer@albsmeier.net>, krion MFC after: 2 weeks
* Remove an outdated comment about ifnet not being locked.ru2005-02-151-3/+0
| | | | OK'ed by: njl, rwatson, sam
* Disable ethernet flow control in if_fxp by default, in order to preventrwatson2005-01-291-1/+1
| | | | | | | unexpected surprises when a system panics or is left in the debugger. Requested by: kris MFC after: 3 days
* Start each of the license/copyright comments with /*-, minor shuffle of linesimp2005-01-063-3/+3
|
* Allow fxp(4) cards with a revision id of 0 to use the 82503 serialmux2005-01-041-1/+1
| | | | | | | | | interface as well. This is not an expected revision id per the datasheet, but unfortunately there are such cards out there with a 82557 chipset, and they want to use the 82503. PR: kern/75739 Reported by: Andre Albsmeier <andre.albsmeier@siemens.com>
* Only try to use the 82503 serial interface for the 82557 chipsets. Themux2004-12-201-2/+2
| | | | | | | | | datasheet says it is only valid for such chipsets and shouldn't be used with others. This fixes some 82559 based cards which otherwise only work at 10Mbit. MFC after: 5 days Tested by: krion
* Make interrupt coalescing work on big endian systems.yongari2004-11-171-2/+4
| | | | | | | Also change struct ucode.length to be in number of elements (u_int32_t) to help endian handling. MFC after: 2 weeks
* Add support for the fxp(4) based card in ICH6 (i915) chipsets.mux2004-09-181-0/+1
| | | | | | This is a RELENG_5 candidate. Submitted by: Mike Tancsa <mike@sentex.net>
* Deorbit the fxp tuning hint (hint.fxp.UNIT_NUMBER.ipcbxmit_disable)truckman2004-08-111-26/+4
| | | | | introduced in if_fxp.c revision 1.180. The bug fix committed in revision 1.180 fixed the packet truncation problem.
* Bring in the first chunk of altq driver modifications. This covers themlaier2004-07-021-4/+9
| | | | | | | | | | | following drivers: bfe(4), em(4), fxp(4), lnc(4), tun(4), de(4) rl(4), sis(4) and xl(4) More patches are pending on: http://peoples.freebsd.org/~mlaier/ Please take a look and tell me if "your" driver is missing, so I can fix this. Tested-by: many No-objection: -current, -net
* Remove the setting of the pci config variables on power state changes.imp2004-06-281-37/+2
| | | | The bus does this now.
* Abstract the locking in fxp(4) a bit more by using macros formux2004-06-022-8/+11
| | | | | mtx_assert() and mtx_owned(), as it is done in other places, for instance proc locking.
* Use the device sysctl tree instead of rolling our own. Some of themux2004-06-022-26/+20
| | | | | | | | | | | sysctls were global (hw.fxp_rnr and hw.fxp_noflow), all of them are now per-device. Sample output of "sysctl dev.fxp0" with this patch, with the standard %foo nodes removed : dev.fxp0.int_delay: 1000 dev.fxp0.bundle_max: 6 dev.fxp0.rnr: 0 dev.fxp0.noflow: 0
* Add missing <sys/module.h> includesphk2004-05-301-0/+1
|
* POLA dictates that VLAN_MTU be enabled by default.yar2004-05-271-1/+7
| | | | | | | | In particular, disabling it was likely to break configurations involving ng_vlan(4) since the latter couldn't control the parent's VLAN_MTU in the way vlan(4) did. Pointed out by: ru
* Those sysctls shouldn't be writtable from inside a jail.pjd2004-05-261-2/+2
|
* Teach fxp(4) to control VLAN_MTU in the hardware.yar2004-05-252-8/+17
| | | | | | | | Now reception of extended frames can be toggled through ioctl(SIOCSIFCAP). The card will also receive extended frames when in promiscuous mode.
* Change a if (...) panic() to a KASSERT().mux2004-05-241-2/+2
|
* A handler for ioctl(SIOCSIFCAP) should not alter a bit inyar2004-05-231-1/+2
| | | | | | | if_capenable unless the interface driver is actually able to toggle the respective capability on and off. Reviewed by: ru
* We don't need to initialize if_output, ether_ifattach() does itmux2004-05-231-1/+0
| | | | for us.
* Cosmetic:yar2004-05-211-2/+6
| | | | | Set capability bits in a consistent way. Add a comment on why the VLAN_MTU stuff comes after ether_ifattach().
* The driver fxp(4) has reception of large frames enabled hardcodedly,yar2004-05-211-0/+1
| | | | so let VLAN_MTU be marked in if_capenable from the beginning.
* Implemented per-interface polling(4) control.ru2004-04-111-1/+16
|
* Add new ID for Intel 82562ET (ICH5/ICH5R) Pro/100 VE Ethernet.imp2004-04-071-0/+1
| | | | | Submitted by: Stefan Bethke PR: 61320
* Convert callers to the new bus_alloc_resource_any(9) API.njl2004-03-171-5/+4
| | | | | Submitted by: Mark Santcroos <marks@ripe.net> Reviewed by: imp, dfr, bde
* Adjust $FreeBSD$'s.obrien2004-03-171-3/+0
|
* Announce ethernet MAC addresss in ether_ifattach().mdodd2004-03-141-3/+0
|
* Sometimes cardbus attachments don't attach, so while we track downimp2003-11-281-0/+1
| | | | | | | | this problem put these lines back in. While they should be unnecessary, they appear to be sometimes necessary. Reviewed in concept: dfr Approved by: re (scottl@)
* Remove explicit cardbus attachments from drivers where this is identicaldfr2003-11-031-1/+0
| | | | | | | to the pci attachment. Cardbus is a derived class of pci so all pci drivers are automatically available for matching against cardbus devices. Reviewed by: imp
* Replace the if_name and if_unit members of struct ifnet with new membersbrooks2003-10-311-2/+1
| | | | | | | | | | | | | if_xname, if_dname, and if_dunit. if_xname is the name of the interface and if_dname/unit are the driver name and instance. This change paves the way for interface renaming and enhanced pseudo device creation and configuration symantics. Approved By: re (in principle) Reviewed By: njl, imp Tested On: i386, amd64, sparc64 Obtained From: NetBSD (if_xname)
* Remove unused FXP_UNIT() macro.brooks2003-10-301-2/+0
|
* mark interrupt handlers MPSAFEsam2003-10-291-1/+1
|
* change timeout to be MPSAFEsam2003-09-052-5/+5
| | | | Sponsored by: FreeBSD Foundation
* Use PCIR_BAR(x) instead of PCIR_MAPS.jhb2003-09-021-2/+2
| | | | | Glanced over by: imp, gibbs Tested by: i386 LINT
* Use __FBSDID().obrien2003-08-241-0/+3
| | | | Also some minor style cleanups.
* Prefer new location of pci include files (which have only been in theimp2003-08-221-2/+2
| | | | | tree for two or more years now), except in a few places where there's code to be compatible with older versions of FreeBSD.
* Use the revision ID from PCI configuration space to identify Inteljdp2003-08-041-23/+41
| | | | | | | 8255x chips more precisely. The information was obtained from Intel's Open Source Software Developer Manual for the 8255x. MFC after: 1 day
* Use the BUS_DMA_ZERO flag.mux2003-07-271-4/+2
|
OpenPOWER on IntegriCloud