summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* Add better error handling for RTAS calls. These can potentially causenwhitehorn2011-06-261-1/+18
| | | | | | | machine checks (e.g. invalid PCI configuration cycles), but these can be caught and recovered from. This change also the RTAS PCI driver to work without modification as a replacement for the Grackle driver on Grackle-based Powermacs.
* Revert r223479. It is unnecessary and served only to slightly amelioratenwhitehorn2011-06-262-4/+0
| | | | some manifestations of the bug actually fixed in r223485.
* .. this wasn't supposed to be committed! sorry.adrian2011-06-261-2/+0
|
* 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-262-1/+5
| | | | | | | | | 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-263-3/+3
| | | | | | | | | | | | | | | 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
* I think 23dBm is the correct value to use here. CRDA uses 20dBm + 3dB max ↵adrian2011-06-261-9/+9
| | | | | | | antenna gain; I believe net80211 doesn't take antenna gain into account and leaves it up to the driver to enforce. (ath_hal(4) certainly tries to do this.)
* Add a couple more frequency ranges to the FCC3 (FCC + DFS) regulatory domain.adrian2011-06-262-0/+62
| | | | | | | | | | | | | The frequency range 5490MHz -> 5710MHz was opened up sometime in 2009, but regdomain.xml wasn't updated. FCC reference: (Section 15.407): http://louise.hallikainen.org/FCC/FccRules/2009/15/407/ The hole between 5600-5650MHz is due to a request from Airports using a weather radar system which also utilises this range. The GIT commit explaining this hole in more detail can be found here: http://git.kernel.org/?p=linux/kernel/git/linville/wireless-regdb.git;a=commit;h=fcbf9225d56e82d9a4e506187d42285e76d81523
* Remove duplicate header includeskevlo2011-06-2616-47/+17
|
* Replace tab with 8 spaces, bringing it in line with the rest of the file.adrian2011-06-261-3/+3
|
* cam/scsi/scsi_cd.c:gibbs2011-06-261-7/+4
| | | | | | In cdregister(), hold the periph lock semaphore during changer probe/configuration. This removes a window where an open of the cd device may succeed before probe processing has completed.
* cam/cam_xpt.c:gibbs2011-06-261-2/+2
| | | | | | | | In camisr_runqueue(), we need to run the sims queue regardless of whether or not the current peripheral has more work to do. This reverts a change mistakenly made in revision 223081. Reported by: ache
* Turn the minimum PWM fan speed down to 30 from 40. It turns out the burningnwhitehorn2011-06-261-1/+1
| | | | | | | smell that caused me to turn this up was due to a failed fan burning, not a CPU (plus a healthy dose of paranoia). Submitted by: Paul Mather <paul at gromit dot dlib dot vt dot edu>
* 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
* sh: Test that '!' is literal if quoted and first char of bracket expressionjilles2011-06-251-0/+16
| | | | This also works on stable/8.
* More accurate birthplace.joel2011-06-251-1/+1
|
* Oops. The sec field of struct bintime is *not* a 32-bit type.marcel2011-06-251-1/+1
| | | | It's time_t, which is 64 bits on ia64.
* - Move bus_auto.conf back into /etc/devd/hselasky2011-06-253-2/+2
| | | | | | | - Rename bus_auto.conf into usb.conf Requested by: imp @ MFC after: 14 days
* Define the minimum fractional period in terms of hz. We know hz ismarcel2011-06-251-2/+2
| | | | | | | | | a magnitude smaller than itc_freq. A minimum period of 10*hz is sufficient precision. As a side-effect, the number of clocks per second, when the machine is idle, dropped by more than 50%. Be anal and define the maximum period to be at least 4G seconds. With a 64-bit counter and an ITC frequency that's expected to be always less than 4Ghz, it takes longer than that to wrap around.
* If there is a read error reading Y/N confirmation from the keyboard,kientzle2011-06-252-1/+12
| | | | | | | | | exit immediately with an error. If there is an error opening or reading a file to put into the archive, set the return value for a deferred error exit. PR: bin/154407
* The kerberos5 tools are only used as build tools but not otherwise andmarius2011-06-251-1/+1
| | | | | | didn't get installed either. MFC after: 1 week
* As with EFI, OFW and U-Boot etc only compile FDT support on thosemarius2011-06-253-4/+8
| | | | architectures that actually use it.
* - 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
* - Move auto-load devd config file into etc/defaults folder.hselasky2011-06-252-116/+2010
| | | | | | | - Regenerate file after bugfix in the generator. Suggested by: Jeremy Messenger MFC after: 14 days
* - Need to respect the module name and the USB mode when accumulating device ↵hselasky2011-06-253-10/+24
| | | | | | | | | ID's. - Be more verbose on file seek failures. Allow a file size of zero. - Improve the wrapper shell. MFC after: 14 days
* - Improve bus_autoconf tool.hselasky2011-06-2511-416/+1005
| | | | | | | | | | - Implement simple and generic language which can be used to describe any kind of device ID structures. - Fix endian issues. - Add an example format file. Suggested by: imp @ MFC after: 14 days
* Remove redundant Capsicum sysctl.jonathan2011-06-251-7/+0
| | | | | | Since we're now declaring FEATURE(security_capabilities), there's no need for an explicit SYSCTL_NODE. Approved by: rwatson
* Add missing libkvm and libutil dependencies.pluknet2011-06-251-0/+2
| | | | | | | Now libprocstat takes care of its own dependencies and does not require applications to specify them. Reviewed by: stas, jilles
* unconditionally stop other cpus when entering kdb in smp systemavg2011-06-251-21/+2
| | | | | | | | | | | ... and thus retire debug.kdb.stop_cpus tunable/sysctl. The knob was to work around CPU stopping issues, which since have been either fixed or greatly reduced. kdb should really operate in a special environment with scheduler stopped and interrupts disabled to provide deterministic debugging. Discussed with: attilio, rwatson X-MFC after: 2 months or never
* generic_stop_cpus: pull timeout logic from under DIAGNOSTICavg2011-06-251-3/+1
| | | | | | | | | | | | | | | ... and also increase the timeout. It's better to try to proceed somehow despite stuck CPUs than to hang indefinitely. Especially so during shutdown and when entering kdb or panic. Timeout value is still an aribitrary value. Timeout diagnostic is just a printf; the work on something more debuggable is planned by attilio. Need to be careful here as stop_cpus_hard is called very early while enetering kdb and soon(-ish) it may become called very early when entering panic. Reviewed by: attilio MFC after: 2 months
* Replace the original copyright notice with my own. Everything inmarcel2011-06-251-30/+22
| | | | | this file is written by me and has no bearing on the initial or original version.
* Update copyright.marcel2011-06-251-1/+1
|
* Now that ia64 has been switched to the event timers, remove themarcel2011-06-251-4/+0
| | | | conditional compilation work-arounds.
* Switch to the event timers infrastructure. This includes:marcel2011-06-258-106/+137
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | o Setting td_intr_frame to the XIVs trap frame because it's referenced by the ET event handler. o Signal EOI to the CPU before calling the registered XIV handlers. This prevents lost ITC interrupts, which cause starvation in one-shot mode. o Adding support for IPI_HARDCLOCK with corresponding per-CPU counters. o Have the APs call cpu_initclocks() so as to limited the scattering of clock related initialization. cpu_initclocks() calls the <self>_bsp() or <self>_ap() version accordingly. o Uncomment the ET clock handling in cpu_idle(). o Update the DDB 'show pcpu' output for the new MD fields. o Entirely rewritten ia64_ih_clock(). Note that we don't create as many clock XIVs as we have CPUs, as is done on PowerPC. It doesn't scale. We can only have 240 XIVs and we can have more CPUs than that. There's a single intrcnt index for the cumulative clock ticks and we keep per CPU counts in the PCPU stats structure. o Register the ITC by hooking SI_SUB_CONFIGURE (2nd order). Open issues: o Clock interrupts can still be lost. Some tweaking is still necessary. Thanks to: mav@ for his support, feedback and explanations. ET stats while committing: eris% sysctl machdep.cpu | grep nclks machdep.cpu.0.nclks: 24007 machdep.cpu.1.nclks: 22895 machdep.cpu.2.nclks: 13523 machdep.cpu.3.nclks: 9342 machdep.cpu.4.nclks: 9103 machdep.cpu.5.nclks: 9298 machdep.cpu.6.nclks: 10039 machdep.cpu.7.nclks: 9479 eris% vmstat -i | grep clock clock 108599 50
* 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.
* Comment out AH_DEBUG, to get this kernel to compile, until AH_DEBUG is fixed.cognet2011-06-241-1/+1
|
* sh(1): Improve documentation of shell patterns:jilles2011-06-241-5/+10
| | | | | | | | | | | * Shell patterns are also for ${var#pat} and the like. * An '!' by itself will not trigger pathname generation so do not call it a meta-character, even though it has a special meaning directly after an '['. * Character ranges are locale-dependent. * A '^' will complement a character class like '!' but is non-standard. MFC after: 1 week
* - Export more USB device ID's.hselasky2011-06-244-11/+60
| | | | | | - Update bus_auto.conf accordingly. MFC after: 3 days
* Split out host_pcib_get_busno() from the generic PCI-PCI bridge driver tojhb2011-06-243-92/+131
| | | | | start a new file that will hold utility APIs used by various Host-PCI bridge drivers and drivers that provide PCI domains.
* - Add auto-load devd config file for USB kernel modules.hselasky2011-06-241-0/+2347
| | | | MFC after: 14 days
* - We need to sort all USB device ID's together. Else the matching order willhselasky2011-06-243-54/+163
| | | | | | be wrong. This is required because devd only executes one entry. MFC after: 14 days
* sh(1): Document the case command better.jilles2011-06-241-2/+13
| | | | | Suggested by: netchild Reviewed by: gjb
* - 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
* Don't die if either of INET or INET6 aren't in the running kernel.jhb2011-06-241-5/+25
| | | | | | | | Instead, report "protocol not supported" errors at runtime if a user attempts to use a protocol that the kernel doesn't support. Reviewed by: bz MFC after: 1 week
* Add support for string values with white spaces for ifconfig(8)pluknet2011-06-241-1/+1
| | | | | | | | | | | | parameters accepting them (such as description, group). Changes discussed on freebsd-rc. PR: conf/156675 Reported by: "Alexander V. Chernikov" <melifaro att ipfw ru> Suggested by: hrs Analyzed with: Alexander V. Chernikov via IRC MFC after: 2 weeks
OpenPOWER on IntegriCloud