summaryrefslogtreecommitdiffstats
path: root/sys/dev
Commit message (Collapse)AuthorAgeFilesLines
* Add device ID for the Davicom 56PDV PCI Modem.jhb2011-07-081-0/+1
| | | | | | PR: kern/75132 Submitted by: Mike Tancsa @ Sentex (older patch against puc(4)) MFC after: 1 week
* Add new USB 3G driver.hselasky2011-07-083-0/+1844
| | | | | Submitted by: PseudoCylon <moonlightakkiy@yahoo.ca> MFC after: 14 days
* A fix to make the LINT-NOINET build happy, if thisjfv2011-07-071-3/+3
| | | | works out the ixgbe driver should be changed as well.
* With retirement of cpumask_t and usage of cpuset_t for representing aattilio2011-07-041-4/+5
| | | | | | | | | | | | | | | mask of CPUs, pc_other_cpus and pc_cpumask become highly inefficient. Remove them and replace their usage with custom pc_cpuid magic (as, atm, pc_cpumask can be easilly represented by (1 << pc_cpuid) and pc_other_cpus by (all_cpus & ~(1 << pc_cpuid))). This change is not targeted for MFC because of struct pcpu members removal and dependency by cpumask_t retirement. MD review by: marcel, marius, alc Tested by: pluknet MD testing by: marcel, marius, gonzo, andreast
* Make the USB keyboard driver more HID compliant.hselasky2011-07-043-151/+475
| | | | | | Try to auto-detect keyboards which should use the BOOT protocol. MFC after: 2 weeks
* Tag mbufs of all incoming frames or packets with the interface's FIBbz2011-07-034-0/+7
| | | | | | | | | setting (either default or if supported as set by SIOCSIFFIB, e.g. from ifconfig). Submitted by: Alexander V. Chernikov (melifaro ipfw.ru) Reviewed by: julian MFC after: 2 weeks
* Introduce a quirk for broken USB MIDI hardware instead of limiting performancehselasky2011-07-034-11/+18
| | | | | | in general. MFC after: 1 week
* Fix for "nomatch" event for ums and ukbd drivers when uhid is loaded.hselasky2011-07-021-0/+12
| | | | MFC after: 3 days
* Fix problem about USB MIDI TX data format, that some devices only accepthselasky2011-07-021-23/+30
| | | | | | | a maximum of 4 bytes (one command) per short terminated USB transfer. Optimise the TX case by sending multiple USB frames. MFC after: 1 week
* Add ID for Marvell 88SE9125 SATA controller.mav2011-06-301-0/+1
| | | | | PR: kern/157843 MFC after: 1 week
* Add detection for the Marvel 88E1149R and treat it just like theimp2011-06-302-1/+6
| | | | 88E1149.
* - Add read-only sysctls for all of the tunables supported by the igb andjhb2011-06-293-5/+53
| | | | | | | | | | | em drivers. - Make the per-instance 'enable_aim' sysctl truly per-instance by having it change a per-instance variable (which is used to control AIM) rather than having all of the per-instance sysctls operate on a single global variable. Reviewed by: jfv (earlier version) MFC after: 1 week
* Add support for a MosChip PCI express serial port adapter.hselasky2011-06-291-0/+2
| | | | MFC after: 1 week
* Fix a corner case in STA beacon processing when a CSA is received butadrian2011-06-291-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | the AP doesn't transmit beacons. If the AP requests a CSA (ie, a channel switch) and then enters CAC (channel availability check) for 60 seconds, it doesn't send beacons and it just listens for radar events (and other things which we don't do yet.) Now, ath_newstate() was not resetting the beacon timer config on a transition to the RUN state when in STA mode - it was setting sc_syncbeacon, which simply updates the beacon config from the contents of the next received beacon. This means the STA never generates beacon miss events. If the AP goes into CAC for 60 seconds and recovers, the STA will happily receive the first beacon and reconfigure timers. But if it gets a radar event after that, it'll change channel again, not notify the station that it's changed channel.. and since the station is happily waiting for the first beacon to configure the beacon timer details from, it won't ever generate a beacon miss interrupt and it'll sit there forever (or until the AP appears on that channel once again.) This change forces the last known beacon timer config to be written to hardware on a transition from CSA->RUN in STA mode. This forces bmiss events to occur and the STA will eventually (after a handful of beacon miss events) begin scanning for another access point.
* 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)
OpenPOWER on IntegriCloud