| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
some confusion when reading the manual page.
PR: 117798
Discussed with: keramida, brueffer
Recommended by: phk
|
|
|
|
|
|
| |
PR: 130324
Submitted by: Jaakko Heinonen <jh@saunalahti.fi>
MFC after: 3 days
|
|
|
|
|
|
|
| |
security.7 manpage a while ago.
MFC after: 1 week
Noticed by: simon
|
| |
|
|
|
|
| |
kern.cam.cd.%d.minimum_cmd_size to new SYSCTL VARIABLES section.
|
| |
|
|
|
|
| |
Add one more proposition to check correct PCM audio device usage.
|
| |
|
|
|
|
|
| |
Some hardware require different drivers depending on implementation,
that may confuse users.
|
|
|
|
| |
Discussed with: stas
|
|
|
|
|
|
| |
Noticed by: simon
Reviewed by: imp
MFC after: 1 week
|
|
|
|
|
|
|
| |
struct protosw.
Submitted by: bz
MFC after: 3 weeks
|
|
|
|
|
| |
Approved by: kib (mentor)
MFC after: 1 week
|
|
|
|
|
|
|
| |
- ae(4) first appeared in 7.1. Reflect this.
Approved by: kib (mentor)
MFC after: 1 week
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now the NDISulator supports NDIS USB drivers that it've tested with
devices as follows:
- Anygate XM-142 (Conexant)
- Netgear WG111v2 (Realtek)
- U-Khan UW-2054u (Marvell)
- Shuttle XPC Accessory PN20 (Realtek)
- ipTIME G054U2 (Ralink)
- UNiCORN WL-54G (ZyDAS)
- ZyXEL G-200v2 (ZyDAS)
All of them succeeded to attach and worked though there are still some
problems that it's expected to be solved.
To use NDIS USB support, you should rebuild and install ndiscvt(8) and
if you encounter a problem to attach please set `hw.ndisusb.halt' to
0 then retry.
I expect no changes of the NDIS code for PCI, PCMCIA devices.
Obtained from: //depot/projects/ndisusb/...
|
| |
|
| |
|
|
|
|
| |
MFC after: 1 month
|
|
|
|
|
|
|
|
|
| |
Silence mdoc(7) warnings;
Xref correct manual pages;
Point user to the ddb.8 manual page.
PR: 129398
Submitted by: gavin
|
|
|
|
|
|
|
| |
Add a missing comma and bump doc date.
PR: 127602
Submitted by: Dmitry Sivachenko <mitya@yandex-team.ru>
|
|
|
|
| |
MFC after: 4 weeks
|
|
|
|
|
|
|
|
|
|
| |
Note that there is no working backend (or at least
that is mentioned in the PR ticket) but the device
is now supported on our end.
PR: 117205
Submitted by: Artem Naluzhnyy <tut at nhamon dot com dot ua>
MFC after: 1 week
|
| |
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
anything other than 0. Make it so. This fixes
"panic: VOP_STRATEGY failed bp=0xc320dd90 vp=0xc3b9f648",
encountered when writing to an orphaned filesystem. Reason
for the panic was the following assert:
KASSERT(i == 0, ("VOP_STRATEGY failed bp=%p vp=%p", bp, bp->b_vp));
at vfs_bio:bufstrategy().
Reviewed by: scottl, phk
Approved by: rwatson (mentor)
Sponsored by: FreeBSD Foundation
|
|
|
|
|
| |
Submitted by: yongari
MFC after: 1 week
|
|
|
|
|
| |
Reviewed by: brueffer
MFC after: 4 weeks
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. separating L2 tables (ARP, NDP) from the L3 routing tables
2. removing as much locking dependencies among these layers as
possible to allow for some parallelism in the search operations
3. simplify the logic in the routing code,
The most notable end result is the obsolescent of the route
cloning (RTF_CLONING) concept, which translated into code reduction
in both IPv4 ARP and IPv6 NDP related modules, and size reduction in
struct rtentry{}. The change in design obsoletes the semantics of
RTF_CLONING, RTF_WASCLONE and RTF_LLINFO routing flags. The userland
applications such as "arp" and "ndp" have been modified to reflect
those changes. The output from "netstat -r" shows only the routing
entries.
Quite a few developers have contributed to this project in the
past: Glebius Smirnoff, Luigi Rizzo, Alessandro Cerri, and
Andre Oppermann. And most recently:
- Kip Macy revised the locking code completely, thus completing
the last piece of the puzzle, Kip has also been conducting
active functional testing
- Sam Leffler has helped me improving/refactoring the code, and
provided valuable reviews
- Julian Elischer setup the perforce tree for me and has helped
me maintaining that branch before the svn conversion
|
| |
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
| |
- Tweak a word choice.
- Drop a reference to Alpha.
|
|
|
|
|
| |
Reviewed by: arch
Approved by: kib
|
| |
|
|
|
|
|
|
| |
laptops. This includes battery presence detection, charging status, current
and voltage readouts, and charge level indication. The sysctl interface
is somewhat ACPI-like.
|
| |
|
| |
|
| |
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
Submitted by: Ben Kaduk
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
module; the ath module now brings in the hal support. Kernel
config files are almost backwards compatible; supplying
device ath_hal
gives you the same chip support that the binary hal did but you
must also include
options AH_SUPPORT_AR5416
to enable the extended format descriptors used by 11n parts.
It is now possible to control the chip support included in a
build by specifying exactly which chips are to be supported
in the config file; consult ath_hal(4) for information.
|
| |
|
|
|
|
|
|
|
| |
macros. Note the logging of file and line.
Reviewed by: dchagin
MFC after: 3 days
|
| |
|
| |
|
| |
|
| |
|