| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Submitted by: avg@
|
|
|
|
|
|
|
| |
disabled for BCM5719 A0 revision due to known hardware errata.
Many thanks to Broadcom for continuing support of FreeBSD.
Submitted by: Geans Pin at Broadcom
|
|
|
|
|
|
|
|
|
|
|
| |
AR8132 FastEthernet controller. The PHY has no ability to
establish a gigabit link. Previously only link parters which
support down-shifting was able to establish link.
This change should fix a long standing link establishment issue of
AR8132.
PR: kern/156935
MFC after: 1 week
|
| |
|
|
|
|
|
|
| |
systems. In principle, FreeBSD should run on at least some of these
already, and support for the remainder will hopefully show up eventually,
so add this while I'm thinking about it.
|
|
|
|
|
| |
handled in miibus after r221812. Thanks to marius@ for piecing this
together!
|
|
|
|
|
|
|
| |
after rest, in which case we may need to deisolate it.
Tested by: nwhitehorn
MFC after 1 week
|
|
|
|
| |
been enumerated (merlin and later), flick this on.
|
|
|
|
|
|
|
|
|
| |
Casting a pointer to a wide integer is probably not that bad, but I am
still guilty of not testing this.
Pointyhat to: avg
MFC after: 1 week
X-MFC with: r221803
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
file and processes information retrieval from the running kernel via sysctl
in the form of new library, libprocstat. The library also supports KVM backend
for analyzing memory crash dumps. Both procstat(1) and fstat(1) utilities have
been modified to take advantage of the library (as the bonus point the fstat(1)
utility no longer need superuser privileges to operate), and the procstat(1)
utility is now able to display information from memory dumps as well.
The newly introduced fuser(1) utility also uses this library and able to operate
via sysctl and kvm backends.
The library is by no means complete (e.g. KVM backend is missing vnode name
resolution routines, and there're no manpages for the library itself) so I
plan to improve it further. I'm commiting it so it will get wider exposure
and review.
We won't be able to MFC this work as it relies on changes in HEAD, which
was introduced some time ago, that break kernel ABI. OTOH we may be able
to merge the library with KVM backend if we really need it there.
Discussed with: rwatson
|
|
|
|
|
|
|
| |
them in a new header file, ar9002/ar9285_an.h.
Shuffle the AR9280 analog registers in ar5416/ar541phy.h into a contiguous
spot.
|
|
|
|
|
|
|
|
|
|
| |
This brings our implementation in line with OSS specification for
systems that support mmap. The change should also improve compatibility
with OSS software not specifically written for FreeBSD, e.g. PulseAudio
OSS plugin.
Reviewed by: kib, jhb
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
(beta?) AR9280 chips.
Note: This doesn't "fix" half/quarter rate support for these
chips; it merely fixes an oversight.
Obtained from: Atheros
|
|
|
|
|
| |
* If AR9130, give the chip extra time to reset
* If AR5416, don't shutdown the chip during reset
|
| |
|
|
|
|
|
| |
MFC after: 1 month
Obtained from: OpenBSD
|
|
|
|
| |
Reviewed by: julian
|
|
|
|
| |
to Seth Heasley for preparing the changes.
|
|
|
|
|
|
|
|
| |
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.
|