| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
Originally submitted by: Wayne Self <wself@cdrom.com>
Allow a ppp startup option in rc.conf.
Adjust sysinstall so that it appends to the end of ppp.conf
and uses the generated profile to start ppp in auto mode on
boot.
Submitted by: Josef L. Karthauser <joe@uk.FreeBSD.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ethernet controllers based on the AIC-6915 "Starfire" controller chip.
There are single port, dual port and quad port cards, plus one 100baseFX
card. All are 64-bit PCI devices, except one single port model.
The Starfire would be a very nice chip were it not for the fact that
receive buffers have to be longword aligned. This requires buffer
copying in order to achieve proper payload alignment on the alpha.
Payload alignment is enforced on both the alpha and x86 platforms.
The Starfire has several different DMA descriptor formats and transfer
mechanisms. This driver uses frame descriptors for transmission which
can address up to 14 packet fragments, and a single fragment descriptor
for receive. It also uses the producer/consumer model and completion
queues for both transmit and receive. The transmit ring has 128
descriptors and the receive ring has 256.
This driver supports both FreeBSD/i386 and FreeBSD/alpha, and uses newbus
so that it can be compiled as a loadable kernel module. Support for BPF
and hardware multicast filtering is included.
|
|
|
|
| |
Submitted by: "Sean O'Connell" <sean@stat.Duke.EDU>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
track.
The $Id$ line is normally at the bottom of the main comment block in the
man page, separated from the rest of the manpage by an empty comment,
like so;
.\" $Id$
.\"
If the immediately preceding comment is a @(#) format ID marker than the
the $Id$ will line up underneath it with no intervening blank lines.
Otherwise, an additional blank line is inserted.
Approved by: bde
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
track.
The $Id$ line is normally at the bottom of the main comment block in the
man page, separated from the rest of the manpage by an empty comment,
like so;
.\" $Id$
.\"
If the immediately preceding comment is a @(#) format ID marker than the
the $Id$ will line up underneath it with no intervening blank lines.
Otherwise, an additional blank line is inserted.
Approved by: bde
|
| |
|
| |
|
|
|
|
|
|
| |
- Don't discourage people from using "make readmes"
- Document WRKDIRPREFIX.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gigabit ethernet adapters. This includes two single port cards
(single mode and multimode fiber) and two dual port cards (also single
mode and multimode fiber). SysKonnect is currently the only
vendor with a dual port gigabit ethernet NIC.
The ports on dual port adapters are treated as separate network
interfaces. Thus, if you have an SK-9844 dual port SX card, you
should have both sk0 and sk1 interfaces attached. Dual port cards
are implemented using two XMAC II chips connected to a single
SysKonnect GEnesis controller. Hence, dual port cards are really
one PCI device, as opposed to two separate PCI devices connected
through a PCI to PCI bridge. Note that SysKonnect's drivers use
the two ports for failover purposes rather that as two separate
interfaces, plus they don't support jumbo frames. This applies to
their Linux driver too. :)
Support is provided for hardware multicast filtering, BPF and
jumbo frames. The SysKonnect cards support TCP checksum offload
however this feature is not currently enabled (hopefully it will
be once we get checksum offload support).
There are still a few things that need to be implemeted, like
the ability to communicate with the on-board LM80 voltage/temperature
monitor, but I wanted to get the driver under CVS control and into
-current so people could bang on it.
A big thanks for SysKonnect for making all their programming info
for these cards (and for their FDDI and token ring cards) available
without NDA (see www.syskonnect.com).
|
|
|
|
| |
Submitted by: Sheldon Hearn <sheldonh@uunet.co.za>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
PR: docs/12302
Submitted by: Don Croyle <croyle@gelemna.ft-wayne.in.us>
Reviewed by: nik
|
| |
|
|
|
|
|
|
| |
Sync vnode.9 with the definitions in <sys/vnode.h>
Reviewed by: Doug Rabson
|
| |
|
|
|
|
| |
Approved by: dg
|
|
|
|
| |
fix wording in man page, through != to
|
|
|
|
| |
for section 9 man pages.
|
|
|
|
|
|
| |
section. Update some descriptions of the various sections to
reflect that they are valid for section 9 man pages. Add a table
of section numbers and what they are used for.
|
| |
|
| |
|
|
|
|
| |
Submitted/Reviewed by: Joe Touch <touch@ISI.EDU>
|
|
|
|
|
|
| |
DEVICE_PROBE can return priorities.
Reviewed by: Doug Rabson <dfr@nlsystems.com>
|
|
|
|
|
|
| |
man pages that use it.
PR: 10659
|
|
|
|
|
|
|
|
|
| |
Don't document non-bugs in the BUGS section, or anywhere else. It
is not a bug to drop data when overloaded. The compile-time tuning
options turned out to be not very useful, and aren't supported
offically.
Documented the not so new option CY_PCI_FASTINTR.
|
| |
|
|
|
|
|
| |
PR: docs/12068
Submitted by: Steve Coltrin <spcoltri@io.com>
|
|
|
|
|
|
|
|
| |
(QIC) written under 2.X may not be easily read under the current
driver without explicitly setting to variable mode or to the blocksize
these tapes were written under 2.X with.
PR: 6681
|
| |
|
|
|
|
|
| |
PR: docs/10474
Submitted by: Yoshiteru Kageyama <yt-kage@cb3.so-net.ne.jp>
|
|
|
|
|
| |
PR: docs/10624
Submitted by: Joe Abley <jabley@buddha.clear.net.nz>
|
|
|
|
|
| |
PR: docs/11596
Submitted by: Robert Watson <robert@fledge.watson.org>
|
|
|
|
|
|
|
| |
fail on some filesystems.
PR: docs/11645
Submitted by: Harold Gutch <logix@foobar.franken.de>
|
|
|
|
|
|
|
| |
directories).
PR: docs/11695
Submitted by: Chris Costello <chris@calldei.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
similar to the PNIC I (supported by the pn driver). In fact, it's really
a Macronix 98715A with wake on LAN support added. According to LinkSys,
the PNIC II was jointly developed by Lite-On and Macronis. I get the
feeling Macronix did most of the work. (The datasheet has the Macronix
logo on it, and is in fact nearly identical to the 98715 datasheet, except
for the extra wake on LAN registers.) In any case, the PNIC II works just
fine with the Macronix driver.
The changes are:
- Move PCI ID for the PNIC II from the pn driver to the mx driver.
- Mention PNIC II support in mx.4.
- Mention PNIC II support in RELNOTES.TXT and HARDWARE.TXT.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
to the '-o' flag in the mount(8) and filesystem specific
mount pages where information can be obtained about the available
options.
PR: docs/10108
|
|
|
|
| |
PR: i386/10328
|
|
|
|
| |
PR: docs/10500 (Masaru Tsunoda [3]masaru@pokemon.to)
|
|
|
|
|
|
|
| |
- Mention that the 6Mbps turbo adapters are supported in HARDWARE.TXT
and RELNOTES.TXT and the wi.4 man page
- Mention turbo adapters in the wicontrol.8 man page and provide a
complete table of available transmit speed settings
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ADMtek AL981 "Comet" chipset. The AL981 is yet another DEC tulip clone,
except with simpler receive filter options. The AL981 has a built-in
transceiver, power management support, wake on LAN and flow control.
This chip performs extremely well; it's on par with the ASIX chipset
in terms of speed, which is pretty good (it can do 11.5MB/sec with TCP
easily).
I would have committed this driver sooner, except I ran into one problem
with the AL981 that required a workaround. When the chip is transmitting
at full speed, it will sometimes wedge if you queue a series of packets
that wrap from the end of the transmit descriptor list back to the
beginning. I can't explain why this happens, and none of the other tulip
clones behave this way. The workaround this is to just watch for the end
of the transmit ring and make sure that al_start() breaks out of its
packet queuing loop and waiting until the current batch of transmissions
completes before wrapping back to the start of the ring. Fortunately, this
does not significantly impact transmit performance.
This is one of those things that takes weeks of analysis just to come
up with two or three lines of code changes.
|
|
|
|
| |
OKed by: peter
|
|
|
|
|
|
| |
* Optional bits now shown as such.
Submitted by: Philippe Charnier & bde
|