| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
MFC after: 1 week.
|
|
|
|
|
|
|
| |
+ Be more consistent between BMAKE and TMAKE.
+ Add NO_CTF to crosstools as is done for bootstrap and build tools.
Reviewed by: marcel
|
|
|
|
|
|
|
|
| |
* 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.
|
|
|
|
|
|
| |
* Track number of logged operations
* call alq_post() so things are logged
* network order things
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
can see they're likely in a very noisy environment.
|
|
|
|
|
|
| |
it.
Obtained from: Atheros
|
|
|
|
| |
(when debug is enabled) no matter what.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
This would be overwritten by the board initvals written in ah->writeIni().
|
|
|
|
| |
See UPDATING entry for 20110427
|
| |
|
| |
|
|
|
|
| |
PR: 156893
|
|
|
|
| |
Requested by: many
|
|
|
|
| |
MFC after: 5 days
|
|
|
|
|
|
| |
Which is also useless, IMO.
MFC after: 5 days
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
chip with a non-default clock.
PR: kern/147583
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Submitted by: des
|
|
|
|
| |
silently added in r218936.
|
|
|
|
|
| |
more real-time logging, without forcing a write(2) on every single
character.
|
|
|
|
| |
after being removed in r205702. Remove it again.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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 PID for Simtec Electronics EntropyKey, a hardware random number generator.
|
|
|
|
| |
See sys/dev/usb/usb_device.c for what devctl_notify() gets.
|
|
|
|
| |
MFC after: 1 month
|
|
|
|
| |
MFC after: 1 month
|
|
|
|
|
|
|
| |
Fix a race between vm_object_collapse and vm_fault.
Reviewed by: alc@
MFC after: 3 days
|
|
|
|
| |
Submitted by: Geans Pin at Broadcom
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
- Fix an incorrect "uint32_t *" cast in bxe_set_rx_mode().
Submitted by: yongari@
Approved by: davidch@
MFC after: Two weeks
|
|
|
|
|
|
| |
using event handlers. A different version was
Submitted by: Taku YAMAMOTO (taku at tackymt dot homeip dot net)
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
is 0x5.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
called "3D sound" and the alike.
MFC after: 14 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
| |
PR: 156676
Submitted by: Tobias Brunner (tobias@strongswan.org)
MFC after: 1 week
|