summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Define and exclude DRAM regions used by hardware/bootloder on XLPjchandra2012-08-201-65/+73
| | | | | Fix xlp_mem_init() - remove the ad-hoc code for excluding memory regions and use an array of regions.
* Flesh out some initial EDMA TX FIFO fill, complete and refill routines.adrian2012-08-201-6/+195
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Note: This is totally sub-optimal and a work in progress. * Support filling an empty FIFO TXQ with frames from the ath_buf queue in the ath_txq list. However, since there's (currently) no clean, easy way to separate the frames that are in the FIFO versus just waiting, the code waits for the FIFO to be totally empty before it attempts to queue more. This is highly sub-optimal but is enough to get the ball rolling. * A _lot_ of the code assumes that the TX status is filled out in the struct ath_buf bf_status field. So for now, memcpy() the completion over. * None of the TX drain / reset routines will attempt to complete completed frames before draining, so it can't be used for 802.11n TX aggregation. (This won't work anyway, as the aggregation TX descriptor API hasn't yet been converted; and that'll happen in some future commits.) * Fix an issue where the FIFO counter wasn't being incremented, leading to the queue logic just plain not working. * HAL_EIO means "descriptor wasn't valid", versus "not finished, don't continue." So don't stop processing descriptors when HAL_EIO is hit. * Don't service frame completion from the beacon queue. It isn't currently fully setup like a real queue and the first attempt at accessing the queue lock will panic the kernel. Tested: * AR9380, STA mode This commit is brought to you by said AR9380 in STA mode.
* Advance the descriptor pointer by sc->sc_tx_desclen bytes, rather thanadrian2012-08-201-12/+11
| | | | | | | | | | | | | | sizeof(struct ath_desc). This isn't correct for EDMA TX descriptors. This popped up during iperf tests. Ping tests never created frames that had enough segments to overflow into a second descriptor. However, an iperf TCP test would do that after a few seconds; the second descriptor would almost always certainly have garbage. Tested: * AR9380, STA mode * AR9280, STA mode (802.11n TX, legacy TX)
* Make sure all of the buffers are printed, rather than (n-1).adrian2012-08-201-4/+2
|
* Add the ds1631 temperature driver.andreast2012-08-193-0/+3
|
* Add a new sound driver for PowerMacs, found here on my Quad G5.andreast2012-08-192-0/+316
| | | | | It allows simple playback and volume control like the other Mac drivers, not more.
* Add a new temperature driver for certain PowerMacs. Found here on my Quad G5.andreast2012-08-192-0/+414
|
* Unify the sysctl description with the other PowerMac temperature drivers.andreast2012-08-191-7/+9
|
* Avoid using the degree symbol. Looks ugly on the console.andreast2012-08-191-3/+4
|
* Do the ADC init only at startup and not during every sensor read call.andreast2012-08-191-5/+12
| | | | This reduces the number of interrupts.
* Fix typo. Not a win in terms of functionality but in terms of completeness.andreast2012-08-191-1/+1
|
* Though I disagree, I conceed to jhb & Rui. Noterrs2012-08-191-1/+1
| | | | | | | | that we still have a problem with this whole structure of locks and in_input.c [it does not lock which it should not, but this *can* lead to crashes]. (I have seen it in our SQA testbed.. besides the one with a refcnt issue that I will have SQA work on next week ;-)
* Update zfs(8) manpage with illumos version of "zfs diff"mm2012-08-191-26/+44
| | | | | | | | | | | | Illumos issue: 2399 zfs manual page does not document use of "zfs diff" References: https://www.illumos.org/issues/2399 PR: docs/170764 Obtained from: ssh://anonhg@hg.illumos.org/illumos-gate MFC after: 1 week
* Backport fix for vendor issue #3085mm2012-08-191-4/+5
| | | | | | | | | | | 3085 zfs diff panics, then panics in a loop on booting References: https://www.illumos.org/issues/3085 PR: kern/170763 Obtained from: ssh://anonhg@hg.illumos.org/illumos-gate (r13772) MFC after: 1 week
* In ip6_ctloutput() guard inp_flags modifications with INP_WLOCK.trociny2012-08-191-0/+6
| | | | MFC after: 2 weeks
* - Allow to pass extra parameters for each jails.kuriyama2012-08-192-5/+20
| | | | | | | - To achieve above, convert jail(8) invocation to use new style command line "-c" flag. Reviewed at: freebsd-jail@
* Extend the TX descriptor debug printing to be properly aware ofadrian2012-08-192-4/+83
| | | | | | | | | | | | | | | | | EDMA code. * create a new TX EDMA descriptor struct to represent TX EDMA descriptors when doing debugging; * implement an EDMA printing function which: + hardcodes the TX map size to 4 for now; + correctly prints out the number of segments - there's one descriptor for up to 4 buffers (segments), not one for each segment; + print out 4 DS buffer and len pointers; + print out the correct number of DWORDs in the TX descriptor. TODO: * Remove all of the hard-coded stuff. Ew.
* When assembling the descriptor list, make sure that the "first" descriptoradrian2012-08-191-1/+3
| | | | | | | | | | | | | | | | | | | | | | is marked correctly. The existing logic assumed that the first descriptor is i == 0, which doesn't hold for EDMA TX. In this instance, the first time filltxdesc() is called can be up to i == 3. So for a two-buffer descriptor: * firstSeg is set to 0; * lastSeg is set to 1; * the ath_hal_filltxdesc() code will treat it as the last segment in a descriptor chain and blank some of the descriptor fields, causing the TX to stop. When firstSeg is set to 1 (regardless of lastSeg), it overrides the lastSeg setting. Thus, ath_hal_filltxdesc() won't blank out these fields. Tested: AR9380, STA mode. With this, association is successful.
* Use pmap_kextract(x) rather than pmap_extract(kernel_pmap, x). Themarcel2012-08-181-1/+1
| | | | | former knows about all the special mappings, like PBVM. The kernel text and data are in the PBVM.
* Build zfs on ia64 as well. We don't build a loader with zfs supportmarcel2012-08-181-0/+1
| | | | just yet, but building it makes sure we catch (build) regressions.
* Don't build the ski loader anymore. The code is not deleted just yet,marcel2012-08-181-1/+6
| | | | | as it explains the distinction between the common and the platform- specific code.
* Remove support for SKI: HP's Itanium simulator. It's pretty much notmarcel2012-08-186-467/+0
| | | | | | | | | used, serves very little value given that FreeBSD runs on real H/W for a long time. Note that SKI is open-source (see http://ski.sourceforge.net), so if there's interest and value again, then this code can be revived. Discussed with: jhb
* Add drm and i915 ioctl translations for 32 bit process on 64 bit host.kib2012-08-188-8/+988
| | | | | Submitted by: meowthink@gmail.com MFC after: 2 weeks
* Deliver SIGSYS to the guilty thread, not to the process.kib2012-08-181-1/+1
| | | | MFC after: 1 week
* Cleanup use of 'host' when running 'rpcinfo -p'.kevlo2012-08-181-5/+11
| | | | Obtained from: NetBSD
* Fix typokevlo2012-08-181-1/+1
|
* Add mvts(4) driver for internal thermal sensor found on 88F6282 and 88F6283.hrs2012-08-182-0/+179
| | | | | | The temperature value will be exported via sysctl like this: dev.mvts.0.temperature: 52.1C
* Sort IDs.hrs2012-08-181-1/+1
|
* Fix build when DEBUG is defined.hrs2012-08-181-2/+5
|
* - MV_DEV_88F6282 has 256KB 4-way L2 cache.hrs2012-08-181-6/+14
| | | | | | - Sort IDs in win_cpu_can_remap() and remove MV_DEV_MV78100 because it is included in MV_DEV_DISCOVERY. - Add MV_DEV_MV78XXX to xor_max_eng().
* Fix a bug that could fail to initialize GPIO pins specified in "gpios" becausehrs2012-08-181-1/+1
| | | | "gpio-controller" property at the controller node was always ignored.
* - Add OF_hasprop() and ofw_bus_has_prop(). These can be used to checkhrs2012-08-184-2/+29
| | | | | | | | | existence of the property. - Fix ofw_bus_is_compatible{,_strict}() to prevent substring match in the compatible string. Reviewed by: raj
* Fix two instances of the file names generated by revnetgroup(8).zeising2012-08-181-2/+2
| | | | Approved by: joel (mentor)
* Remove machine from the LN2410SBC config, it is set by std.s3c2410andrew2012-08-181-1/+0
|
* Set machine correctly on ARM. This allows universe to use the correct worldandrew2012-08-1820-13/+22
| | | | | | when building each kernel. Reviewed by: imp
* Eliminate another vestige of page coloring.alc2012-08-171-2/+1
|
* Catch up with the subversion conversion and apply these build-time patches.obrien2012-08-175-94/+13
|
* Remove unused member of struct indir (in_exists) from UFS and EXT2 code.mjg2012-08-176-11/+0
| | | | | | Reviewed by: mckusick Approved by: trasz (mentor) MFC after: 1 week
* Add new USB device ID.hselasky2012-08-172-0/+2
| | | | | PR: usb/170688 MFC after: 1 week
* Unexpand a couple of TAILQ_FOREACH()s.jhb2012-08-172-6/+2
|
* Fix dhclient to properly exit and teardown the configured lease whenjhb2012-08-171-0/+7
| | | | | | | | | | link is lost. devd will start a new dhclient instance when link is restored. PR: bin/166656 Submitted by: Peter Jeremy (mostly) Reviewed by: brooks (earlier version from Peter) MFC after: 1 month
* Allow static DMA allocations that allow for enough segments to do page-sizedjhb2012-08-171-6/+7
| | | | | | | | | segments for the entire allocation to use kmem_alloc_attr() to allocate KVM rather than using kmem_alloc_contig(). This avoids requiring a single physically contiguous chunk in this case. Submitted by: Peter Jeremy (original version) MFC after: 1 month
* Ok jhb, lets move the ifa_free() down to the bottom torrs2012-08-171-1/+1
| | | | | | | | assure that *all* tables and such are removed before we start to free. This won't protect the Hash in ip_input.c but in theory should protect any other uses that *do* use locks. MFC after: 1 week (or more)
* Fix two problems with pmap_clear_modify().alc2012-08-171-51/+13
| | | | | | | | | | | | | | | | | First, pmap_clear_modify() is write protecting all mappings to the specified page, not just clearing the modified bit. Specifically, it sets PTE_RO on the PTE, which is wrong. Moreover, it is calling vm_page_dirty(), which is not the expected behavior for pmap_clear_modify(). Generally speaking, the machine-independent VM layer masks these mistakes. For example, setting PTE_RO will result in additional soft faults, but not a catastrophe. Second, pmap_clear_modify() may not clear the modified bits because it only iterates over the PV list when the page has the PV_TABLE_MOD flag set and elsewhere the pmap clears the PV_TABLE_MOD flag anytime a modified mapping is write protected or destroyed. However, the page may still have other mappings with the modified bit set. Eliminate a stale comment.
* The GPIO drivers were initialising their mutexes with type ofrpaulo2012-08-174-8/+4
| | | | | MTX_NETWORK_LOCK. This is wrong since these mutexes have nothing to do with networking.
* regen.davidxu2012-08-179-9/+9
|
* Correct a regression introduced during the import of file(1) 5.11.mckay2012-08-172-3/+1
| | | | | | | | | | | Magic tests containing "search" or "regex" directives were incorrectly compiled by "mkmagic" and were effectively ignored. This caused troff files (for example) to be detected as simply "ASCII text" instead of as "troff or preprocessor input, ASCII text". PR: bin/170415 Approved by: consensus on developers@ MFC after: 3 days
* Implement syscall clock_getcpuclockid2, so we can get a clock iddavidxu2012-08-1721-23/+272
| | | | | | | | for process, thread or others we want to support. Use the syscall to implement POSIX API clock_getcpuclock and pthread_getcpuclockid. PR: 168417
* The TCP PAWS fix for kernels with fast tick rates (r231767) changed the TCPlstewart2012-08-171-4/+6
| | | | | | | | | | | | | | | | | | | timestamp related stack variables to reference ms directly instead of ticks. The h_ertt(4) Khelp module relies on TCP timestamp information in order to calculate its enhanced RTT estimates, but was not updated as part of r231767. Consequently, h_ertt has not been calculating correct RTT estimates since r231767 was comitted, which in turn broke all delay-based congestion control algorithms because they rely on the h_ertt RTT estimates. Fix the breakage by switching h_ertt to use tcp_ts_getticks() in place of all previous uses of the ticks variable. This ensures all timestamp related variables in h_ertt use the same units as the TCP stack and therefore results in meaningful comparisons and RTT estimate calculations. Reported & tested by: Naeem Khademi (naeemk at ifi uio no) Discussed with: bz MFC after: 3 days
* Make 'junk' volatile so that compilers won't be tempted to optimizekevlo2012-08-171-1/+1
| | | | | Reviewed by: ache MFC after: 3 days
OpenPOWER on IntegriCloud