| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
bcm4306 cards are ambiguous. BCM4306 rev 2 requires bwi. BCM4306 rev
3 will work with either. Since we can't easily determine which is
which, just remove them.
|
|
|
|
|
|
| |
Fix a typo.
Submitted by: pluknet at gmail dot com
|
|
|
|
| |
Suggested by: joel
|
|
|
|
| |
functionality and configuration options.
|
| |
|
|
|
|
|
|
| |
date.
Pointed by: imp, Ruslan Mahmatkhanov <cvs-src at yandex dot ru>
|
|
|
|
|
|
|
| |
Add a man page for the mps(4) driver, and reference it in the
mpt(4) driver man page.
Sponsored by: Spectra Logic Corporation
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The $ip6addrctl_policy is a variable to choose a pre-defined address
selection policy set by ip6addrctl(8).
The keyword "ipv4_prefer" sets IPv4-preferred one described in Section 10.3,
the keyword "ipv6_prefer" sets IPv6-preferred one in Section 2.1 in RFC 3484,
respectively. When "AUTO" is specified, it attempts to read
/etc/ip6addrctl.conf first. If it is found, it reads and installs it as
a policy table. If not, either of the two pre-defined policy tables is
chosen automatically according to $ipv6_activate_all_interfaces.
When $ipv6_activate_all_interfaces=NO, interfaces which have no corresponding
$ifconfig_IF_ipv6 is marked as IFDISABLED for security reason.
The default values are ip6addrctl_policy=AUTO and
ipv6_activate_all_interfaces=NO.
Discussed with: ume and bz
|
|
|
|
|
|
| |
will be replaced with a per-IF version later.
Based on: changes in r206408 by dougb
|
|
|
|
| |
Discussed with: dougb, core.5, and core.6
|
| |
|
|
|
|
|
|
|
|
| |
year is 2010, not 2005.
Approved by: keramida (mentor)
Pointy hat to: gjb
MFC after: 1 week
|
|
|
|
|
| |
Approved by: keramida (mentor)
MFC after: 1 week
|
|
|
|
|
|
|
| |
about chipset type instead of card names because it's not easy to sort
names what cards use these chipsets.
Pointed by: imp
|
|
|
|
| |
Approved by: rrs (mentor)
|
|
|
|
| |
Sponsored by: The FreeBSD Foundation
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
PR: 149979
Submitted by: gcooper
Patch by: gcooper
Approved by: keramida (mentor)
MFC after: 1 week
|
|
|
|
|
|
|
| |
* add a phatom target for the DTRACEOBJS
* when invoking DTrace, don't add DTRACEOBJS to the command line.
Sponsored by: The FreeBSD Foundation
|
| |
|
|
|
|
|
|
| |
code associated with overflow or with the drain function. While this
function is not expected to be used often, it produces more information
in the form of an errno that sbuf_overflowed() did.
|
|
|
|
|
|
|
|
|
| |
define USDT probes on a provider.d file and then use this new make
infrastructure to build the corresponding header file and object file.
This will only take effect when the user defines WITH_DTRACE when building.
Sponsored by: The FreeBSD Foundation
|
|
|
|
|
|
|
| |
program or library depend on that before doing the final linking. This
will be needed by DTrace.
Sponsored by: The FreeBSD Foundation
|
|
|
|
| |
Sponsored by: The FreeBSD Foundation
|
|
|
|
|
|
|
| |
(http://lists.freebsd.org/pipermail/freebsd-current/2008-December/001756.html)
Submitted by: nork
MFC after: 3 days
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
called when the sbuf internal buffer is filled. For kernel sbufs with a
drain, the internal buffer will never be expanded. For userland sbufs
with a drain, the internal buffer may still be expanded by
sbuf_[v]printf(3).
Sbufs now have three basic uses:
1) static string manipulation. Overflow is marked.
2) dynamic string manipulation. Overflow triggers string growth.
3) drained string manipulation. Overflow triggers draining.
In all cases the manipulation is 'safe' in that overflow is detected and
managed.
Reviewed by: phk (the previous version)
|
| |
|
|
|
|
|
| |
Submitted by: nork at FreeBSD.org
MFC after: 3 days
|
|
|
|
| |
by loader(8) interface.
|
|
|
|
|
|
|
|
| |
a solution is using PIO mode. As fas as I know all open source based
broadcom drivers for specially LP PHY has this issue because it's
a reverse engineered driver from wl(4).
Pointed by: Warren Block <wblock at wonkity.com>
|
|
|
|
|
| |
supported by the bwn(4) firmware that as fas as I know the vendor
dropped its support. Bumps date also.
|
|
|
|
| |
Submitted by: Ben Kaduk <minimarmot gmail com>, Valentin Nechaev
|
| |
|
|
|
|
| |
Approved by: nwhitehorn (mentor)
|
|
|
|
| |
Approved by: nwhitehorn (mentor)
|
|
|
|
|
|
|
|
|
| |
characters.
PR: 150098
Submitted by: cc (cpt_complain at yahoo dot com)
Approved by: keramida (mentor)
MFC after: 1 week
|
|
|
|
|
|
| |
Tested on PowerMac G4 AGP.
Reviewed by: nwhitehorn
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
Approved By: pgollucci (co-mentor)
|
|
|
|
| |
Submitted by: jkim
|
|
|
|
|
| |
While I'm here Xref vlan(4) as sis(4) supports VLAN oversized
frames.
|
|
|
|
|
|
| |
PR: conf/150214
Submitted by: Li
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
| |
- add rm_try_rlock().
- add RM_SLEEPABLE to use sx(9) as the back-end lock in order to sleep while
holding the write lock.
- change rm_noreadtoken to a cpu bitmask to indicate which CPUs need to go
through the lock/unlock in order to synchronize. As a side effect, this
also avoids IPI to CPUs without any readers during rm_wlock.
Discussed with: ups@, rwatson@ on arch@
Sponsored by: Isilon Systems, Inc.
|
|
|
|
|
|
|
|
| |
are under include/ and include/fs/.
PR: docs/139153
Submitted by: gjb
MFC after: 1 week
|
|
|
|
|
|
|
| |
The number returned by stat(2) is generated automatically, so it is not
possible to deduce whether the device is blocking or not.
MFC after: 1 week
|