Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

change the description reflecting recent driver modifications.

This commit is contained in:
nisimura 2007-10-19 04:57:48 +00:00
parent 1de52faec2
commit 6c83afd245
1 changed files with 17 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

35
share/man/man4/kse.4
View File

@ -1,4 +1,4 @@
.\" $NetBSD: kse.4,v 1.4 2006/07/06 06:20:52 wiz Exp $ .\" $NetBSD: kse.4,v 1.5 2007/10/19 04:57:48 nisimura Exp $
.\" .\"
.\" Copyright (c) 2006 Tohru Nishimura. .\" Copyright (c) 2006 Tohru Nishimura.
.\" .\"
@ -38,8 +38,16 @@
.Sh DESCRIPTION .Sh DESCRIPTION
The The
.Nm .Nm
driver supports Ethernet interfaces based on the Micrel driver supports Ethernet interfaces based on the Micrel 8842/8841
8842/8841 PCI Ethernet chips. PCI Ethernet chips. The 8842 has 2 Ethernet ports which behave as
a managed switch to bridge each other. It works like a T-shape
connector of Ethernet data flow in which an Ethernet controller
sits at the leg of the T. Frames can flow between the two ports
while traffic destined for the 8842 reaches the EMAC. The 8841 is
a plain 10/100 Ethernet.
The
.Nm
driver distinguishs and handles them according to the HW model.
.Sh SEE ALSO .Sh SEE ALSO
.Xr arp 4 , .Xr arp 4 ,
.Xr ifmedia 4 , .Xr ifmedia 4 ,
@ -52,23 +60,14 @@ The
driver was written by driver was written by
.An Tohru Nishimura . .An Tohru Nishimura .
.Sh BUGS .Sh BUGS
The 8842 has 2 Ethernet ports which behave as a managed switch to
bridge each other.
It works like a T-shape connector of Ethernet data flow in which
the Ethernet controller sits at the leg of the T.
Frames can flow between the two ports while traffic destined
for the 8842 reaches the EMAC.
The The
.Nm .Nm
driver is not aware of the second port's existence and treats the The __STRICT_ALIGNMENT case is not written. 8842 media selection
8842 as if it was a single port 8841. keeps "auto" and indicates "up 100baseTX-FX flow" when either of
The second port PHY is always auto select. two ports is found link-up. There is no functional provision to
The PDF documentation is unclear and inconsistent about whether see and control the media selection of them this moment. Advanced
the Rx DMA alignment restriction is removed or not. features like flow volume bound, VLAN tag insertion/removal, QoS
The __STRICT_ALIGNMENT case is not written. DiffServ are not implemented and remain uncontrollable by the
Advanced features like flow volume bound, VLAN tag insertion/removal,
and detailed MIB counters are not implemented and remain uncontrollable
by the
.Nm .Nm
driver. driver.
UDP4CSUM is not very useful since the HW has an implementation UDP4CSUM is not very useful since the HW has an implementation