summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Add basic metadata integrity check. In case when partition table wasae2011-05-111-1/+48
| | | | | | | | probed and read successfull, but it contains invalid values (e.g. overlapped partitions, offset or size is out of bounds), then table will be rejected. MFC after: 1 month
* Remove wrong comment.dchagin2011-05-111-3/+0
| | | | MFC after: 1 week.
* + DTrace as a bootstrap tool is only needed on certain older systems.obrien2011-05-111-4/+10
| | | | | | | + Be more consistent between BMAKE and TMAKE. + Add NO_CTF to crosstools as is done for bootstrap and build tools. Reviewed by: marcel
* Fix up the net80211 alq logging - this commit makes it usable.adrian2011-05-111-3/+5
| | | | | | | | * revert a local path change that shouldn't have made it to the commit * fix some indenting/wrapping * Fix the ale data copy - i should be copying into the ale data pointer, not over the ale entry itself.
* net80211 alq bugfixes:adrian2011-05-111-3/+12
| | | | | | * Track number of logged operations * call alq_post() so things are logged * network order things
* Make freebsd-update(8) smarter in how it handles $FreeBSD$ tags incperciva2011-05-111-3/+33
| | | | | | | | | | | | | | | | | | | configuration files. If the current file differs from the canonical version from the old release only due to differences in the $FreeBSD$ tag (which can happen if the system was installed from source code, depending on how the src tree was checked out) then freebsd-update will treat the file as "unmodified" and silently update it to the "clean" version in the new release. If the only change being made to a configuration file is in the $FreeBSD$ tag (e.g., for any configuration files which have been modified locally, now that we're using SVN and the $FreeBSD$ tag changes when a branch is created), freebsd-update will no longer print the diff and prompt "Does this look reasonable (y/n)?". Nagged by: pgollucci MFC after: 1 month
* Make the NF calibration logic (hopefully!) more resistive to noisyadrian2011-05-111-12/+28
| | | | | | | | | | | | | | | | environments. In setups where NF calibration can take a while, don't load the CCA and kick off a new NF calibration if the previous one hasn't yet completed. This shouldn't happen unless the environment is noisy but those exist (hi phk!). Here, if the previous NF hasn't completed when ar5416LoadNf() is run (which reads the NF), it skips updating the history buffer, loading the NF CCA array and kicking off the next NF cal. It's hoped it'll occur in the next long calibration interval. Obtained from: Atheros, ath9k, my local HAL
* Always log if the NF CCA load fails; so users with debugging enabledadrian2011-05-111-2/+2
| | | | can see they're likely in a very noisy environment.
* Make sure the chip is awake before writing to it to finally detachadrian2011-05-111-0/+6
| | | | | | it. Obtained from: Atheros
* Add a new flag - HAL_DEBUG_UNMASKABLE - which always logs a debug messageadrian2011-05-112-1/+3
| | | | (when debug is enabled) no matter what.
* Remove unused variableadrian2011-05-111-1/+0
|
* Remove the initial NF completion check.adrian2011-05-111-22/+4
| | | | | | | | | | | | This is taking quite a while for some people in some situations (eg AR5418 in phk's Abusive Radio Environment). Instead, the rest of the calibration related code should ensure that a NF calibration has occured before reading NF values and kicking off another NF calibration. The channel should also likely be marked as "noisy" (CWINT) if the NF calibration takes too long.
* Remove a now unneeded comment..adrian2011-05-111-1/+0
|
* Restore the RSSI threshold after writing the board values.adrian2011-05-111-3/+3
| | | | This would be overwritten by the board initvals written in ah->writeIni().
* Use new option names for NFS client and NFS servergonzo2011-05-1116-28/+28
| | | | See UPDATING entry for 20110427
* Add an ATOMIC_CLEAR_LONG.marius2011-05-101-0/+11
|
* Fix whitespace.marius2011-05-101-1/+1
|
* Fix a bug in r221407; this driver doesn't add the media itself.marius2011-05-101-1/+1
| | | | PR: 156893
* Add SC_PIXEL_MODE to GENERIC for amd64 and i386.jkim2011-05-102-0/+2
| | | | Requested by: many
* bitcount32: replace lengthy comment with a reference to SWARavg2011-05-101-38/+2
| | | | MFC after: 5 days
* dtrace: remove unused codeavg2011-05-102-42/+2
| | | | | | Which is also useless, IMO. MFC after: 5 days
* Only try to set up IPIs at boot on systems that actually have more than onenwhitehorn2011-05-101-12/+16
| | | | | | | CPU. This fixes a panic observed on Heathrow-based systems without SMP-capable PICs when the kernel had both options SMP and INVARIANTS. MFC after: 5 days
* Regen.ru2011-05-101-36/+75
|
* Reassurance for impatient.ru2011-05-101-0/+10
|
* Style.ru2011-05-101-10/+10
|
* Add an entry for the SIIG Quartet Serial 850 which uses an Oxfordjhb2011-05-101-0/+6
| | | | | | | chip with a non-default clock. PR: kern/147583 MFC after: 1 week
* - There now exist options that have different defaults depending onru2011-05-103-49/+139
| | | | | | | | | | | | | | the architecture, reflect this in documentation. For such options, both WITH_FOO and WITHOUT_FOO description files should be provided. Prodded by: des - Setting a build option may enforce other build options, try harder to detect this case. - Setting a build option may change other option's default value, try harder to detect this case.
* The Objective C support was removed in r220755.ru2011-05-101-2/+0
| | | | Submitted by: des
* Removed unsupported options MK_BINUTILS and MK_GCC that wereru2011-05-101-2/+0
| | | | silently added in r218936.
* Flush the scriptfile whenever we see a non-graphical character to getphk2011-05-101-5/+11
| | | | | more real-time logging, without forcing a write(2) on every single character.
* Another fallout from r220359: MK_GNU_CPIO was mistakenly re-addedru2011-05-101-2/+1
| | | | after being removed in r205702. Remove it again.
* AR9285 (Kite) fixes.adrian2011-05-102-10/+38
| | | | | | | | | | | | | | | | | | * Correct some of the silicon revision checks to match what the Atheros HAL does. (See [1] below.) * Move the PA cal and init cal method assignment to -after- the mac version/revision IDs are stored. The AR9285 init cal was never being called. * Enable ANI. Note Kite 1.0 and 1.1 were prototypes that shouldn't be seen in the wild. Linux ath9k simply removed the prototype code from their codebase. I'm going to leave it in there for now but make it conditionally compilable in the future. Obtained from: Atheros
* Add VID for Simtec Electronics.bms2011-05-101-0/+4
| | | | Add PID for Simtec Electronics EntropyKey, a hardware random number generator.
* Typo. For USB devices, 'serial' should be 'sernum'.bms2011-05-101-1/+1
| | | | See sys/dev/usb/usb_device.c for what devctl_notify() gets.
* Regenerated with latest configure script.delphij2011-05-101-0/+6
| | | | MFC after: 1 month
* MFV: Update to less v443.delphij2011-05-0966-4983/+2848
| | | | MFC after: 1 month
* Another long standing vm bug found at Isilon:mlaier2011-05-091-0/+18
| | | | | | | Fix a race between vm_object_collapse and vm_fault. Reviewed by: alc@ MFC after: 3 days
* Recognize BCM5719C PHY.yongari2011-05-092-0/+2
| | | | Submitted by: Geans Pin at Broadcom
* Since r117657, bge(4) does not enable buffer manager for BCM5705 oryongari2011-05-091-34/+47
| | | | | | | | | | | | | | | newer controllers. However, all data sheet I have access has no indication that buffer manager should not be touched on these controllers. It seems the buffer manager always runs on BCM5705 or newer controllers. Some controller(e.g. BCM5719) needs other buffer manager configuration so driver should enable buffer manager for all controllers. Both Linux and OpenBSD/NetBSD use the same approach. This change polls enable bit of block to know whether specified block was really stopped as well as enabling buffer manager for all controllers in driver initialization. Obtained from: NetBSD
* - Simplify multicast address programming.davidch2011-05-092-66/+65
| | | | | | | | - Fix an incorrect "uint32_t *" cast in bxe_set_rx_mode(). Submitted by: yongari@ Approved by: davidch@ MFC after: Two weeks
* Move VT switching hack for suspend/resume from bus drivers to syscons.cjkim2011-05-094-198/+82
| | | | | | using event handlers. A different version was Submitted by: Taku YAMAMOTO (taku at tackymt dot homeip dot net)
* Implement boot-time TSC synchronization test for SMP. This test is executedjkim2011-05-094-13/+75
| | | | | | | when the user has indicated that the system has synchronized TSCs or it has P-state invariant TSCs. For the former case, we may clear the tunable if it fails the test to prevent accidental foot-shooting. For the latter case, we may set it if it passes the test to notify the user that it may be usable.
* Disable diversity combining support until I can get a firm answeradrian2011-05-092-7/+13
| | | | | | | | | from Atheros as to what/when this is supposed to be enabled. Using the default RX fast diversity settings seems to help quite a bit. Whilst I'm here, change the prototype to return HAL_BOOL rather than int.
* Fix a regression I introduced - only swap analog chains if the RX chainmaskadrian2011-05-091-1/+2
| | | | is 0x5.
* Disable TX STBC - it isn't used for now, but it isn't supported on Kite.adrian2011-05-091-1/+2
|
* Add proper build infrastructure for teken.ed2011-05-0910-28/+305
| | | | | | | | | | | I'm not sure whether we should install teken as a library on any stock FreeBSD installation, but I can imagine people want to tinker around with it now and then. Create a /sys/teken/libteken, which holds a Makefile to install a shared library version of the terminal emulator, complete with a manpage. Also add Makefiles for the demo/stress applications, to build it against the shared library.
* Workaround for broken no-name USB audio devices sold by dealextremehselasky2011-05-091-1/+48
| | | | | | called "3D sound" and the alike. MFC after: 14 days
* Import some initial Kite fixed diversity code from Atheros.adrian2011-05-094-44/+148
| | | | | | | | | | | | | | | | | | | | | | | | | | For now, the diversity settings are controlled by 'txantenna', -not- rxantenna. This is because the earlier chipsets had controllable TX diversity; the RX antenna setting twiddles the default antenna register. I'll try sort that stuff out at some point. Call the antenna switch function from the board setup function so scans, channel changes, mode changes, etc don't set the diversity back to a default state too far from what's intended. Things to todo: * Squirrel away the last antenna diversity/combining parameters and restore them during board setup if HAL_ANT_VARIABLE is defined. That way scans, etc don't reset the diversity settings. * Add some more public facing statistics, rather than what's simply logged under HAL_DEBUG_DIVERSITY. For now, the fixed antenna settings behave better than variable settings for me. I have some further fiddling to do.. Obtained from: Atheros
* Remove an un-needed PA cal call here.adrian2011-05-091-2/+0
|
* Release SP's refcount in key_get_spdbyid().vanhu2011-05-091-0/+1
| | | | | | PR: 156676 Submitted by: Tobias Brunner (tobias@strongswan.org) MFC after: 1 week
OpenPOWER on IntegriCloud