53 Commits

Author SHA1 Message Date
marius
544830c8f1 Add a man page for cas(4) and reference it as appropriate.
Approved by:	re (kib)
MFC after:	2 weeks
2009-06-15 18:24:04 +00:00
yongari
b801626916 Add alc(4) man page and hook up ale(4) to the build.
Also add Xr to appropriate man pages.
2009-06-10 02:19:54 +00:00
antoine
e0ce7397e7 vlan(4) no longer depends on miibus(4).
Reviewed by:	jhb@
MFC after:	1 month
2009-04-20 15:01:45 +00:00
yongari
c7acada69c Correct .Dd
Pointed out by:	maxim
2008-11-12 10:31:06 +00:00
yongari
1ce66caae7 Add ale(4) man page and hook up ale(4) to the build.
Also add Xr to appropriate man pages.
2008-11-12 10:20:29 +00:00
stas
be8a06226f - Add ae(4) to the list of devices support full hardware VLAN
tags processing.

Approved by:	kib (mentor)
MFC after:	1 week
2008-10-04 15:44:22 +00:00
yongari
f00bca6334 Add jme(4) to the list of devices supporting full VLAN processing
in hardware.
2008-05-27 02:01:42 +00:00
yongari
fcbd489a4d Add age(4) to the list of devices supporting full VLAN processing
in hardware.
2008-05-19 02:03:52 +00:00
yongari
2102b743cf sf(4) gained VLAN_MTU support.
Touch Dd.
2008-01-21 06:47:20 +00:00
yar
987f730185 tl(4) appears to support long frames.
Tested by:	Peter Jeremy <peterjeremy at optushome dot com dot au>
2007-05-09 09:02:11 +00:00
yar
edde22f288 Tell that nve(4) has got support for VLAN_MTU.
Touch Dd.
2007-05-07 09:52:39 +00:00
yar
c48f91f092 Update info on VLAN support in hardware:
- bce(4) and cxgb(4) can do hardware acceleration;
- fwe(4) and nfe(4) can handle long frames.
2007-05-02 10:51:48 +00:00
yar
d36c1f8546 Having finished with vlan(4) for today, touch .Dd. 2007-04-24 11:48:49 +00:00
yar
36d1315ab8 We shouldn't say that most Ethernet drivers don't support long frames,
as it's no longer true.
2007-04-24 11:40:52 +00:00
yar
3a3608ddab "Long frame" is the well-known term found in h/w documentation
from several vendors, so prefer it over other synonyms.
2007-04-24 11:35:47 +00:00
yar
f64dce605e Now that we list hardware that supports vlan(4) natively,
we don't need to repeat that for each device listed.
2007-04-24 11:22:27 +00:00
yar
1edfd06b2c xl(4) can support long frames on all chip revisions now. 2007-04-24 11:06:35 +00:00
yar
e9be8ccaeb de(4) ceased to support the BIG_PACKET hack. 2007-04-24 11:03:53 +00:00
yar
67b5103f29 tl(4) in fact has no signs of long frame support. 2007-04-24 10:51:48 +00:00
yar
d20c01926b vr(4) gained VLAN_MTU support. 2007-04-24 10:49:56 +00:00
yongari
af6ffc8ef3 Add msk(4) to the list of devices supporting full VLAN processing
in the hardware.
2006-12-13 02:42:01 +00:00
yar
e65c3fa75d Fix incorrect .Xr syntax I introduced in the previous commit.
Noticed by:	ru
X-MFC with:	rev. 1.31
2006-08-12 17:11:43 +00:00
yar
fb2ee09397 Optionally pad outgoing frames to the minimum of 60 bytes (excl. FCS)
before tagging them.  This can help to work around brain-damage in some
switches that fail to pad a frame after untagging it if its length drops
below the minimum.  This option is blessed by IEEE Std 802.1Q (2003 Ed.),
paragraph C.4.4.3.b.  It's controlled by sysctl net.link.vlan.soft_pad.

Idea by:	az
MFC after:	1 week
2006-08-11 17:09:27 +00:00
yongari
f5c019cc67 Add stge(4) to the list of devices supporting full VLAN processing
in the hardware.
2006-07-25 00:56:47 +00:00
marius
d3ad463bb9 Add le(4) to the list of devices supporting VLAN-sized frames natively. 2006-01-31 22:41:59 +00:00
yar
d258e90d41 Record sk(4) as having native support for extended VLAN frames.
PR:		kern/79998
MFC after:	1 month
2005-10-11 22:59:01 +00:00
trhodes
b7d0ff1b4b Work around an apparent mdoc(7) bug.
Spotted by:	marius
Discussed with:	ru
2005-10-07 02:32:16 +00:00
marius
ca3e74c977 Add gem(4) to the list of devices supporting VLAN-sized frames natively
(since sys/dev/gem/if_gem.c rev. 1.34).

MFC after:	1 week
2005-08-28 15:08:57 +00:00
trhodes
a87b82ead9 Break long lines and kill a few instances of EOL whitespace.
Noticed by:	ru
2005-07-21 05:02:39 +00:00
trhodes
17d84e4e12 Add a "Load module on start up" comment, similar to mac_*.4 pages[1].
Quote .Cd and .Nd text.
Bump doc date.

Requested by:	some user through ru
Supported by:	ru, dwmalone, brueffer
2005-07-19 00:26:30 +00:00
yar
3c06de23de Bump the document date since its content has changed. 2005-01-30 12:13:13 +00:00
yar
fa9897222f Revise the part on VLAN support in physical interfaces.
MFC after:	1 week
2005-01-30 12:06:02 +00:00
yar
8eed1be1fd Update the list of VLAN-aware interface types.
MFC after:	3 days
2005-01-30 10:59:50 +00:00
brueffer
392ec03981 (fast) ethernet -> (Fast) Ethernet
MFC after:	3 days
2004-12-21 01:09:34 +00:00
yar
ec2edfc1ae BUGS should stay below SEE ALSO.
Pointed out by:	ru (wearing the mdoc(7) police hat on his head)
2004-11-15 16:38:37 +00:00
yar
acd420a745 Mention in the BUGS section that EVFILT_NETDEV events
on vlan(4) will be noticed only if the parent uses miibus(4).

Pointed out by:	John-Mark Gurney <gurney_j -at- resnet.uoregon.edu>
2004-11-15 14:33:17 +00:00
brueffer
99d84e82f3 gx(4) is gone, remove any references 2004-11-08 20:06:40 +00:00
yar
de292e5162 Bump the date.
Reminded by:	ru
2004-10-04 15:54:56 +00:00
yar
cd602b46fa Document that vlan(4) requires miibus(4) now. 2004-10-04 13:57:44 +00:00
yar
618c3ddad0 Touch .Dd because the content of the manpage has been updated.
Pointed out by:	ru
2004-05-27 11:12:07 +00:00
yar
ff1f6d8a76 Update the status of VLAN support in interface drivers. 2004-05-26 11:34:51 +00:00
joerg
66ff2a693e Mention that hme(4) natively supports oversized frames. 2004-05-06 13:38:53 +00:00
sam
25af12f3d1 document auto-recognition of device capabilities 2002-11-15 00:25:33 +00:00
yar
c81f62abfe Language style and grammar fixes.
tx(4) has gained native support for vlan(4).

MFC after:	3 days
2002-08-27 14:26:05 +00:00
yar
7e25ea6e98 Update the section on NIC driver support status.
MFC after:	3 days
2002-08-27 14:01:14 +00:00
brooks
b129ffd210 Document the fact that these devices are allocated at runtime using
cloning and point to two common methods of doing so.
2002-05-29 06:55:06 +00:00
ambrisko
81dbce8cc9 Add VLAN for the dc(4) driver (ie long frame). The patch is 2 parts.
One to notify the system that the MTU for VLAN can be 1500 so the vlan
will automatically be configured with a 1500 MTU the other is to ignore
the error case if the received frame is to long.

The frame size notification came from code in the SIS driver, and
the support for long frames derived from the NetBSD Tulip driver.

Tested on:	4 port D-Link adapter DFE-570TX 4 Intel 21143
		Netgear card with 82c169 PNIC 10/100BaseTX

Reviewed by:	ru (manpage), wpaul (not objected to), archie
Approved by:	imp
Obtained from:	NetBSD
2002-01-16 16:33:58 +00:00
jhay
13ccdfc032 Note sis(4) VLAN support.
MFC after:	7 days
2001-12-05 09:34:49 +00:00
yar
bbb41c11df Update the status of VLAN support in the ethernet drivers. 2001-10-05 06:30:42 +00:00
brooks
7da2447808 Make vlan(4) loadable, unloadable, and clonable. As a side effect,
interfaces must now always enable VLAN support.

Reviewed by:	jlemon
MFC after:	3 weeks
2001-09-05 21:10:28 +00:00