summaryrefslogtreecommitdiffstats
path: root/sys/dev
Commit message (Collapse)AuthorAgeFilesLines
* Fix typo in r223648 which was accidentally committedmarius2011-06-281-1/+1
|
* - In gem_reset_rx() also reset the RX MAC which is necessary in order tomarius2011-06-282-48/+55
| | | | | | | | | | | | | | | | | get it out of a stuck condition that can be caused by GEM_MAC_RX_OVERFLOW. - In gem_reset_rxdma() call gem_setladrf() in order to reprogram the RX filter and restore the previous content of GEM_MAC_RX_CONFIG. While at it consistently use the newly introduced sc_mac_rxcfg throughout the driver instead of reading the its old content. - Increment if_iqdrops instead of if_ierrors in case of RX buffer allocation failure. - According to the GEM datasheet the RX MAC should also be disabled in gem_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. In joint forces with: yongari
* Remove duplicate header includeskevlo2011-06-2813-20/+0
|
* Make sure the extended regdomain word is initialised.adrian2011-06-282-0/+3
| | | | | As with the AR9285, the AR9287 has a default word of 0x1F which means all the various bits in that field are set on by default.
* Enable CPUSaver D102 E-step microcode loading for 82551 revisionyongari2011-06-271-0/+2
| | | | 0x10.
* Disable microcode loading for 82550 and 82550C controllers. Loadingyongari2011-06-271-0/+4
| | | | | | | | | | the microcode caused SCB timeouts. Linux driver does not allow microcode loading for these controllers and jfv also confirmed that there is no need to do and it shouldn't. PR: kern/103332 Additional confirmation from: jfv MFC after: 1 week
* Fix whitespace inconsistencies in the TTY layer and its drivers owned by me.ed2011-06-263-7/+7
|
* Fix beacon transmission after a channel set.adrian2011-06-261-0/+21
| | | | | | | | | | | | | | | | | | | | | The DFS code was tickling the channel set directly whilst going through the state RUN -> CSA -> RUN. This only changed the channel; it didn't go via ath_reset(). However in this driver, a channel change always causes a chip reset, which resets the beacon timer configuration and interrupt setup. This meant that data would go out but as the beacon timers never fired, beacons would never be queued. The confusing part is that sometimes the state transition was RUN -> SCAN -> CAC -> RUN (with CSA being in there sometimes); going via SCAN would clear sc_beacons and thus the transition to RUN would reprogram beacon transmission. In case someone tries debugging why suspending a device currently beaconing (versus just RX'ing beacons which is what occurs in STA mode), add a silly comment which should hopefully land them at this commit message. The call to ath_hal_reset() will be clearing the beacon config and it may not be always reset.
* Add ATH_ENABLE_DFS which enables the DFS flag so the DFS codeadrian2011-06-261-0/+3
| | | | | | | | | can be tested. This doesn't at all actually do radar detection! It's just so developers who wish to test the net80211 DFS code can easily do so. Without this flag, the DFS channels are never marked DFS and thus the DFS stuff doesn't run.
* The SMCWUSBG is a zyd(4) device, not an uath(4) device. Remove from thegavin2011-06-262-1/+1
| | | | | | | | | | | | | | | latter. It appears that the addition to uath(4) came in through PR kern/135009, which had tested another device, the SMCWUSBTG2, successfully with uath(4) and included the SMCWUSBG as it "has the same chipset". I can find no other evidence that these two do actually share the same chipset. Moreover, Linux treats the SMCWUSBG as a zyd(4) device also. This reverts r223537. Discussed with: hselasky, kevlo MFC after: 1 week
* Do not attach to the sound device on G5 Xserves, which is actually annwhitehorn2011-06-261-0/+12
| | | | | | | LED controller used to run the load graph on the server's front panel. Reported by: Paul Mather <paul at gromit dot dlib dot vt dot edu> MFC after: 3 days
* - Export the USB device ID format to userspace tools.hselasky2011-06-252-1/+114
| | | | MFC after: 14 days
* - Remove duplicate USB ID.hselasky2011-06-251-1/+0
| | | | MFC after: 3 days
* Now that ia64 has been switched to the event timers, remove themarcel2011-06-251-4/+0
| | | | conditional compilation work-arounds.
* Commit missing piece from a couple days ago - re-add ath_hal_debug.adrian2011-06-251-2/+8
|
* Small fix to bring the non-debug definitions of HALDEBUG/HALDEBUG_G in lineadrian2011-06-241-2/+2
| | | | with the debug definitions.
* - Export more USB device ID's.hselasky2011-06-243-10/+25
| | | | | | - Update bus_auto.conf accordingly. MFC after: 3 days
* Split out host_pcib_get_busno() from the generic PCI-PCI bridge driver tojhb2011-06-242-92/+130
| | | | | start a new file that will hold utility APIs used by various Host-PCI bridge drivers and drivers that provide PCI domains.
* - Export more USB device ID's.hselasky2011-06-244-49/+49
| | | | MFC after: 3 days
* - Ensure that we get all the required nomatch devd events.hselasky2011-06-241-9/+10
| | | | MFC after: 3 days
* - Move execution of event handlers into the probe and attach function so thathselasky2011-06-242-6/+34
| | | | | | | | | dynamically loaded device drivers get a chance to run their event hooks. - Decouple the USB suspend and resume lock from witness. It produces some false warnings due to reusing the lock name among multiple devices. MFC after: 3 days
* - Export the URIO USB device ID's.hselasky2011-06-241-9/+12
| | | | | | - Add checks for configuration and interface index. MFC after: 3 days
* Typo.jhb2011-06-241-1/+1
|
* - Add additional information to the PnP info of USB HUBs children whichhselasky2011-06-242-8/+5
| | | | | | | | | | is now required by bus_autoconf. - Allow interface class matching even if device class is vendor specific. - Update bus_autoconf tool to not generate system and subsystem match lines for the nomatch event. PR: misc/157903 MFC after: 14 days
* - Move all USB device ID arrays into so-called sections,hselasky2011-06-2439-58/+109
| | | | | | | | | | | | sorted according to the mode which they support: host, device or dual mode - Add generic tool to extract these data: tools/bus_autoconf Discussed with: imp Suggested by: Robert Millan <rmh@debian.org> PR: misc/157903 MFC after: 14 days
* Put back the global for rx processing due to popular demand.jfv2011-06-231-1/+5
|
* add missing #define for the non-debug case.adrian2011-06-231-0/+1
|
* - Add some comments about the origin of some USB descriptors.hselasky2011-06-233-1/+10
| | | | MFC after: 7 days
* - Add more USB templates for various USB device classeshselasky2011-06-2310-11/+1169
| | | | | | | - Add basic template support for USB 3.0 - Export definition of template sysctl numbers through usb_ioctl.h MFC after: 7 days
* Re-introduce a global ath_hal_debug again for now, whilst I figure out whatadrian2011-06-2313-24/+43
| | | | | | | | | | | | to do about the few cases where the HAL state isn't available (regdomain) or isn't yet setup (probe/attach.) The global ath_hal_debug now affects all instances of the HAL. This also restores the ability for probe/attach debugging to work; as the sysctl tree may not be attached at that point. Users can just set the global "hw.ath.hal.debug" to a suitable value to enable probe/attach related debugging.
* Fix indenting issues introduced by the previous commit.adrian2011-06-232-4/+4
|
* Break out most of the HAL related tweaks into a per-HAL instance,adrian2011-06-2315-55/+77
| | | | | | | | | | | | | | | | | rather than global variables. This specifically allows for debugging to be enabled per-NIC, rather than globally. Since the ath driver doesn't know about AH_DEBUG, and to keep the ABI consistent regardless of whether AH_DEBUG is enabled or not, enable the debug parameter always but only conditionally compile in the debug methods if needed. The ALQ support is currently still global pending some brainstorming. Submitted by: ssgriffonuser@gmail.com Reviewed by: adrian, bschmidt
* Fix build on ia64 after r223426.jkim2011-06-221-0/+2
|
* Use USB_VENDOR_OVISLINK define rather than the vendor ID.gavin2011-06-221-1/+1
| | | | | | PR: usb/158142 Submitted by: Robert Millan <rmh debian.org> MFC after: 1 week
* Set negative quality to TSC timecounter when C3 state is enabled for Inteljkim2011-06-221-0/+2
| | | | | | | | | | | | | | | processors unless the invariant TSC bit of CPUID is set. Intel processors may stop incrementing TSC when DPSLP# pin is asserted, according to Intel processor manuals, i. e., TSC timecounter is useless if the processor can enter deep sleep state (C3/C4). This problem was accidentally uncovered by r222869, which increased timecounter quality of P-state invariant TSC, e.g., for Core2 Duo T5870 (Family 6, Model f) and Atom N270 (Family 6, Model 1c). Reported by: Fabian Keil (freebsd-listen at fabiankeil dot de) Ian FREISLICH (ianf at clue dot co dot za) Tested by: Fabian Keil (freebsd-listen at fabiankeil dot de) - Core2 Duo T5870 (C3 state available/enabled) jkim - Xeon X5150 (C3 state unavailable)
* Add a helper routine to conditionally modify the start address of ajhb2011-06-221-22/+4
| | | | | | | | | | | | | | | | resource allocation from an x86 Host-PCI bridge driver so that it can be reused by the ACPI Host-PCI bridge driver (and eventually the MPTable Host-PCI bridge driver) instead of duplicating the same logic. Note that this means that hw.acpi.host_mem_start is now replaced with the hw.pci.host_mem_start tunable that was already used in the non-ACPI case. This also removes hw.acpi.host_mem_start on ia64 where it was not applicable (the implementation was very x86-specific). While here, adjust the logic to apply the new start address on any "wildcard" allocation even if that allocation comes from a subset of the allowable address range. Reviewed by: imp (1)
* Remove link state change callback handler. There is no need toyongari2011-06-222-28/+20
| | | | | | | | | | | | | | register both status change and link state change callbacks. Implement checking valid link in state change callback and poll active link state in vr_tick(). This allows immediate detection of lost link as well as protecting driver from frequent link flips during link renegotiation. taskq implementation was removed because driver now needs to poll link state in vr_tick(). While I'm here do not report current link state if interface is not running. Tested by: n_hibma MFC after: 1 week
* Minor cleanup:imp2011-06-211-5/+16
| | | | | | | | o Consider No CIS a normal event and stop whining about it so much (too many cards are like this, espeically usb/firewire cards). o Add comments to the cis reading code. o Made the read from config space a smidge easier to read and eliminate a loop that can be done mathematically.
* Really spell suppress the right wayimp2011-06-211-1/+1
|
* My broken 'u' key scks!imp2011-06-211-1/+1
|
* Fix build with ACPI_DEBUG defined.jhb2011-06-211-8/+9
| | | | | Submitted by: jkim Pointy hat to: jhb
* Supress command completion failure warning when the card isn'timp2011-06-211-1/+1
| | | | | | present. Only call the bus to check if we actually do timeout so we don't affect the normal case (since this case needn't be optimized and this guards against all races).
* Supress warning that command didn't complete when the parent busimp2011-06-211-2/+2
| | | | thinks the card is gone.
* Minor whitespace and style fixes.jhb2011-06-211-3/+4
|
* Use AcpiWalkResources() to parse the resource list from _CRS rather thanjhb2011-06-212-336/+282
| | | | | | | using a home-rolled loop. While here, add support for 64-bit address range resources. Silence on: acpi@ (older version)
* When we see an interrupt status of 0xffffffff, check to see if theimp2011-06-211-2/+3
| | | | | | child is still present. If not, return 'handled' and don't print anything (this is expected behavior). We expect an interrupt on eject, power-down and/or shutdown.
* Mark the card as bad on shutdown. This means that bus_child_presentimp2011-06-211-0/+6
| | | | | will return false on shutdown and massive spewage from usb disappears for usb cardbus adapters.
* Eliminate some global tuneables in favor of adapter-specific,jfv2011-06-202-63/+125
| | | | | | | | | | | | particular flow control and dma coalesce. Also improve the sysctl operation on those too. Add IPv6 detection in the ioctl code, this was done for ixgbe first, carrying that over. Add resource ability to disable particular adapter. Add HW TSO capability so vlans can make use of TSO
* Correct a typo.delphij2011-06-201-1/+1
| | | | | Submitted by: Fabian Keil <fk fabiankeil de> MFC after: 3 days
* Add new USB ID to UDAV driver.hselasky2011-06-192-0/+2
| | | | | Submitted by: Luiz Gustavo S. Costa <lgcosta@pfsense.org> MFC after: 7 days
OpenPOWER on IntegriCloud