summaryrefslogtreecommitdiffstats
path: root/sys/dev
Commit message (Collapse)AuthorAgeFilesLines
* Fix compilation when compiled w/out WITNESS.adrian2009-06-071-0/+1
| | | | Submitted by: Edwin Shao <poleris@gmail.com>
* Initial version of the sec(4) driver for the integrated security engine foundraj2009-06-062-0/+2301
| | | | | | | | | | | in Freescale system-on-chip devices. The following algorithms and schemes are currently supported: - 3DES, AES, DES - MD5, SHA1, SHA256, SHA384, SHA512 Reviewed by: philip Obtained from: Freescale, Semihalf
* Import ACPICA 20090521.jkim2009-06-0546-168/+148
|
* Move buffer management into kbd and kbdmux drivers.ed2009-06-052-45/+93
| | | | | | | | These two drivers seem to be the last consumers of clists. clists are quite overengineered for simple circular buffers, so I'm adding similar buffer management routines to the kbd and kbdmux drivers. The input buffer is now part of the softc structures, instead of having dynamically allocated cblocks.
* Remove duplicate variable setting.thompsa2009-06-041-1/+0
| | | | Spotted by: Sylvestre Gallon
* revert r162516. We only support 1 or 2 channels per streamthompsa2009-06-041-1/+3
| | | | | | which reflects mono and stereo. Submitted by: Hans Petter Selasky
* reimplements RF logic for GCT chipset (as known as UW2453) to supportweongyo2009-06-042-155/+187
| | | | | | | | | | ICIDU NI-707503 which is donated by Nick Hibma (great thanks!). Though it has a MAXIM RF (0x8) there's some success reports with using GCT RF (0x9) codes and it worked well for ICIDU NI-707503 too. So codes for MAXIM and GCT RFs are integrated. Before this commit, if I rememeber correctly, MAXIM RF is never tested that it seems it's a first report working with FreeBSD.
* cleanups the device match list.weongyo2009-06-041-48/+52
|
* Remove unused VM includes.jhb2009-06-032-7/+0
|
* treat IEEE80211_S_CSA as a "running state"; this fixessam2009-06-031-4/+4
| | | | ap mode 11h channel switch announcements
* improve raw xmit failure handlingsam2009-06-021-17/+21
|
* count frag tx failures as an ifnet errorsam2009-06-021-0/+1
|
* fix commentsam2009-06-021-1/+1
|
* restart tdma beacons after vap destroysam2009-06-021-4/+10
|
* fix setting of ni_txratesam2009-06-021-25/+1
| | | | Submitted by: "Paul B. Mahol" <onemda@gmail.com>
* Place the fifo and ref counting variables on the stack to prevent races.thompsa2009-06-022-101/+98
| | | | Submitted by: Hans Petter Selasky
* Reorgansise the logic for tranversing the pipe list.thompsa2009-06-021-9/+9
| | | | Submitted by: Hans Petter Selasky
* Fix compile after the removal of bsd_udev.thompsa2009-06-021-1/+1
| | | | Submitted by: Hans Petter Selasky
* Fix multithread issue where the is_uref variable was not set and clearedthompsa2009-06-021-8/+23
| | | | | | properly in the CDEV private data. Submitted by: Hans Petter Selasky
* Staticize ukbd_detach and fix indentation.thompsa2009-06-021-2/+2
| | | | Submitted by: Sylvestre Gallon
* Re-enable WARNS=6 after my universe test.delphij2009-06-021-0/+1
|
* Buf-ring fixes for mxgegallatin2009-06-022-27/+8
| | | | | | | | | | - always maintain byte/mcast/drop stats via drbr - move #define of IFNET_BUF_RING so that its picked up by all files in the driver - conditionalize IFNET_BUF_RING on the FreeBSD_version bump just after it appeared in the tree. Sponsored by: Myricom Inc.
* In bwi_newstate, only zero the bssid when we stop a STA. And onlyimp2009-06-021-6/+20
| | | | | | | when we've not stopped the card. It hangs the system when we touch the CSR after bwistop. This fixes the hanging on kldunload.
* Include <machine/stdarg.h> for va_*(). I'm not sure how this compiledjhb2009-06-021-0/+1
| | | | on amd64 without this.
* Add support for the four PUC serial interfaces found on IBM SurePOS 300rwatson2009-06-021-0/+11
| | | | | | | series POS terminals. MFC after: 3 days Submitted by: Marc Balmer <marc at msys.ch>
* Add Yukon Extreme device ids, 88E8071 and 88E8072.yongari2009-06-022-3/+9
| | | | | While I'm here correct description of 88E8070. 88E8070 is Yukon Extreme and have gigabit PHY.
* Add Rx checksum offloading support for Yukon FE+ and Yukon Extreme.yongari2009-06-022-8/+67
| | | | | | | | | | | These controllers use newer descriptor format and the new descriptor format uses status LE to indicate the status of checksum. Rx checksummed value used in previous controllers were very cryptic and I failed to understand how to use them. In addition most controllers in previous generations had Rx checksum offloading bug. While I'm here introduce a MSK_FLAG_NORX_CSUM flag to bypass checking Rx checksum offloading as Yukon FE+ A0 has status LE bug.
* Add frame parser capability of Yukon FE+ and Yukon Extreme. Withyongari2009-06-022-13/+47
| | | | | | | | | | | | | | | | | | | this feature hardware automatically computes TCP/UDP payload offset. Introduce MSK_FLAG_AUTOTX_CSUM to mark the capability. Yukon Extreme B0 revision is known to have a silicon for the feature so disable it. Yukon Extreme B0 still can do Tx checksum offloading but CPU have to compute TCP/UDP payload offset. To enable traditional checksum offloading, disable automatic Tx checksum calculation capability. Yukon Extreme A0 revision could not use store-and-forward mode for jumbo frames(silicon bug) so disable Tx checksum offloading for jumbo frames. I believe controllers that have MSK_FLAG_AUTOTX_CSUM capability or new descriptor format do not have Tx checksum offload bug so disable checksum offloading workaround for for short frames. Tested by: jhb, Warren Block ( wblock <> wonkity dot com )
* Add preliminary Yukon Extreme support and register definitions.yongari2009-06-022-34/+198
| | | | | | | | | | | | | | | | | | | | | Yukon Extreme uses new descriptor format for TSO and has Tx frame parser which greatly reduces CPU cycles spent in computing TCP/UDP payload offset calculation in Tx checksum offloading path. The new descriptor format also removed TCP/UDP payload computation for TSO which in turn results in better TSO performance. It seems Yukon Extreme has a lot of new (unknown) features but only basic offloading is supported at this time. So far there are two known issues. o Sometimes Rx overrun errors happen when pulling data over gigabit link. Running over 100Mbps seem to ok. o Ethernet hardware address shows all-zeroed value on 88E8070. Assigning ethernet address with ifconfig is necessary to make it work. Support for Yukon Extreme is not perfect but it would be better than having a non-working device. Special thanks to jbh who fixed several bugs of initial patch. Tested by: jhb, Warren Block ( wblock <> wonkity dot com )
* Program LED registers for 88E1116/88E1149 PHYs. These PHYs areyongari2009-06-022-3/+47
| | | | | | | found on Marvell Yukon Ultra, Marvell Yukon Extreme controllers. While I'm here explicitly issue 'powerup' command for 88E1149 PHY. Tested by: jhb, Warren Block ( wblock <> wonkity dot com )
* Don't assume page register value is 0 and restore previous pageyongari2009-06-021-1/+3
| | | | register after issuing 'powerup'.
* Remove another d_thread_t use that crept in.jhb2009-06-011-1/+1
|
* MFp4.mav2009-06-012-14/+58
| | | | Log supported AHCI controller capabilities.
* Rework socket upcalls to close some races with setup/teardown of upcalls.jhb2009-06-011-13/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Each socket upcall is now invoked with the appropriate socket buffer locked. It is not permissible to call soisconnected() with this lock held; however, so socket upcalls now return an integer value. The two possible values are SU_OK and SU_ISCONNECTED. If an upcall returns SU_ISCONNECTED, then the soisconnected() will be invoked on the socket after the socket buffer lock is dropped. - A new API is provided for setting and clearing socket upcalls. The API consists of soupcall_set() and soupcall_clear(). - To simplify locking, each socket buffer now has a separate upcall. - When a socket upcall returns SU_ISCONNECTED, the upcall is cleared from the receive socket buffer automatically. Note that a SO_SND upcall should never return SU_ISCONNECTED. - All this means that accept filters should now return SU_ISCONNECTED instead of calling soisconnected() directly. They also no longer need to explicitly clear the upcall on the new socket. - The HTTP accept filter still uses soupcall_set() to manage its internal state machine, but other accept filters no longer have any explicit knowlege of socket upcall internals aside from their return value. - The various RPC client upcalls currently drop the socket buffer lock while invoking soreceive() as a temporary band-aid. The plan for the future is to add a new flag to allow soreceive() to be called with the socket buffer locked. - The AIO callback for socket I/O is now also invoked with the socket buffer locked. Previously sowakeup() would drop the socket buffer lock only to call aio_swake() which immediately re-acquired the socket buffer lock for the duration of the function call. Discussed with: rwatson, rmacklem
* Update VNET base pointer setting macro to use a correct source ofzec2009-06-011-1/+1
| | | | | | vnet context. Approved by: julian (mentor)
* Initialize the match structure. This is unnecessary but gcc insists todelphij2009-06-011-2/+1
| | | | complain about it when we raise the WARNS level.
* Add an internal pci_printf() routine similar to device_printf() exceptjhb2009-06-011-7/+18
| | | | that it prefixes the output with 'pci<domain>:<bus>:<device>:<function>: '.
* Adjust some comments.jhb2009-06-011-4/+4
|
* Set an rx jumbo cluster to the correct size beforegallatin2009-06-012-1/+4
| | | | | | | | using bus_dmamap_load_mbuf_sg() on it. This prevents data corruption when the mxge MTU is between 4076 and 8172 on machines with 4KB pages and MXGE_VIRT_JUMBOS is in use (which it isn't, in -current or -stable)
* Revert the WARNS change for now, need some time to fix the real problem.delphij2009-06-011-1/+0
|
* Mark as WARNS=6.delphij2009-06-011-0/+1
|
* Code cleanups to make this WARNS=6 clean.delphij2009-06-017-45/+56
| | | | PR: bin/96128
* driver for Marvell 88W8363 Wireless LAN controllersam2009-06-018-0/+10625
|
* Move the unlock to after the ifdef (maybe the right fix is to removeimp2009-06-011-1/+1
| | | | | the ifdef) since it calls bwi_start_locked, which expects to the lock to be held...
* Make sure that we drain the LED blinking callout on detach.imp2009-06-011-0/+1
| | | | Submitted by: Paul B. Mahol
* Add a comment about what may be happening when we get certainimp2009-06-011-0/+17
| | | | messages. No change to actual code.
* Comment out old Realtek ALC883 quirk, that was disabling phantop power onmav2009-06-011-1/+3
| | | | | | | mic inputs. I have no idea what for it was made that time, but now I have several reports that it should be removed to make microphones work. If this quirk is still required for some systems then they should be identified and specified explicitly.
* According to Intel documentation (307013), 3Gbps mode is supported ondelphij2009-06-011-3/+3
| | | | | Desktop chipsets only for ICH7 series, so mark all ICH7M as ATA_SA150 instead of ATA_SA300.
* ZyXEL G-202 has zd1211b chipset, not zd1211.weongyo2009-06-011-1/+1
| | | | Tested by: Samuel Boivie <samuel at boivie.org>
* Restore support for bell pitch/duration.ed2009-05-315-3/+20
| | | | | | | | Because we only support a single argument to tf_param, use 16 bits for the pitch and 16 bits for the duration. While there, make the argument unsigned. There isn't a single param call that needs a signed integer. Submitted by: danfe (modified)
OpenPOWER on IntegriCloud