| Age | Commit message (Collapse) | Author |
|---|
|
ok miod@
|
|
|
|
watchdogd(4), so there's no point in supporting old, unused,
non-generic interfaces.
Tested by < jg , rilk - com>.
The sensors available on the WDT501 model will be supported later using
the sensors framework.
ok mickey markus
|
|
to be mapped in stge_start().
|
|
stopen(). This change was misplaced in the st roto-tilling at c2k6.
Noticed by deraadt@.
|
|
of B1 to account for the differences with the revision defines used in
OpenBSD's if_bgereg.h vs FreeBSD's.
|
|
information can be passed.
|
|
|
|
- move default MAC/BBP/RF settings from rt2661.c to rt2661reg.h
|
|
- encrypt mgmt frames when they need to (shared authmode)
- move default MAC/BBP/RF settings from rt2560.c to rt2560reg.h
|
|
- move default MAC/BBP/RF settings from if_ral.c to if_ralreg.h
|
|
|
|
ok toby@, "absolutely" deraadt@
|
|
This was causing the "empty portfacts" issue since the IOC wasn't complete
yet with the request however since the id would match the requested id the
timeout was a terminal condition.
|
|
ok toby@, deraadt@
|
|
for any value that is not an increase in size when we are under mbuf pressure,
rather than only succeeding when setting the value to the 4k minimum.
ok markus@, henning@
|
|
me pointed out by marco.
|
|
ok dlg
|
|
|
|
|
|
|
|
|
|
wants. Note that redboot still wants to have a virtual load address
between 0 and ramsize, so loading an unmodified kernel still doesn't work.
|
|
|
|
|
|
|
|
in mem_access_fault4m.
|
|
|
|
# bioctl -h ami0
Volume Status Size Device
ami0 0 Rebuild 1000M sd1 RAID5 8% done
|
|
|
|
functional change.
|
|
|
|
|
|
prodded by uwe@
|
|
|
|
Use it to dynamically tune radio receive sensitivity.
The idea is simple:
- increase sensitivity when the RSSI is bad to optimize throughput on
long distance to the AP, and
- decrease sensitivity when the RSSI is good to reduce noise level and
optimize throughput on short distance to the AP
The EMA allows to smooth RSSI variations so we don't end up changing the
sensitivity too frequently. We check if it would be worth updating the
sensitivity every one second.
RSSI thresholds were taken from the Ralink Tech. Linux driver.
Also, clean a few things while I'm here:
- account for FCS when determining if RTS protection must be used
- fix check for whether WEP encryption is needed or not
- encrypt mgmt frames if we need to (shared authmode)
- cosmetic tweaks
|
|
retry the init sequence if this happens.
|
|
cardbus_conf_read/cardbus_conf_write. This makes fxp* at cardbus?
work (again?) on macppc. tested by various users.
|
|
Thanks for krw@ for testing isa floppies. brad@ ok,
jason@ ok.
|
|
ok krw@
|
|
function as this is already done in the MII tick handler just before calling
the autonegotiation function.
ok krw@
|
|
- when checking for the parity error itself:
+ use pmap_kenter_pa() and pmap_kremove() for the temporary mapping.
+ reenable external cache before invoking pmap_kremove() [which can cause
a cache flush on some models].
|
|
this is better than panic'ing due to low memory condition.
|
|
|
|
|
|
|
|
|
|
|
|
This means that for now a config file can build us3 kernels
ok jason
|
|
After a rmdir()ed directory has been truncated, force an update of
the directory's inode after queuing the dirrem that will decrement
the parent directory's link count. This will force the update of
the parent directory's actual link to actually be scheduled. Without
this change the parent directory's actual link count would not be
updated until ufs_inactive() cleared the inode of the newly removed
directory, which might be deferred indefinitely. ufs_inactive()
will not be called as long as any process holds a reference to the
removed directory, and ufs_inactive() will not clear the inode if
the link count is non-zero, which could be the result of an earlier
system crash.
If a background fsck is run before the update of the parent directory's
actual link count has been performed, or at least scheduled by
putting the dirrem on the leaf directory's inodedep id_bufwait list,
fsck will corrupt the file system by decrementing the parent
directory's effective link count, which was previously correct
because it already took the removal of the leaf directory into
account, and setting the actual link count to the same value as the
effective link count after the dangling, removed, leaf directory
has been removed. This happens because fsck acts based on the
actual link count, which will be too high when fsck creates the
file system snapshot that it references.
This change has the fortunate side effect of more quickly cleaning
up the large number dirrem structures that linger for an extended
time after the removal of a large directory tree. It also fixes a
potential problem with the shutdown of the syncer thread timing out
if the system is rebooted immediately after removing a large directory
tree.
|
