From 6c83afd24538cbc5361489518280a107e5a59267 Mon Sep 17 00:00:00 2001 From: nisimura Date: Fri, 19 Oct 2007 04:57:48 +0000 Subject: [PATCH] change the description reflecting recent driver modifications. --- share/man/man4/kse.4 | 35 +++++++++++++++++------------------ 1 file changed, 17 insertions(+), 18 deletions(-) diff --git a/share/man/man4/kse.4 b/share/man/man4/kse.4 index 542227df7a05..d8db23f61fdc 100644 --- a/share/man/man4/kse.4 +++ b/share/man/man4/kse.4 @@ -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. .\" @@ -38,8 +38,16 @@ .Sh DESCRIPTION The .Nm -driver supports Ethernet interfaces based on the Micrel -8842/8841 PCI Ethernet chips. +driver supports Ethernet interfaces based on the Micrel 8842/8841 +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 .Xr arp 4 , .Xr ifmedia 4 , @@ -52,23 +60,14 @@ The driver was written by .An Tohru Nishimura . .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 .Nm -driver is not aware of the second port's existence and treats the -8842 as if it was a single port 8841. -The second port PHY is always auto select. -The PDF documentation is unclear and inconsistent about whether -the Rx DMA alignment restriction is removed or not. -The __STRICT_ALIGNMENT case is not written. -Advanced features like flow volume bound, VLAN tag insertion/removal, -and detailed MIB counters are not implemented and remain uncontrollable -by the +The __STRICT_ALIGNMENT case is not written. 8842 media selection +keeps "auto" and indicates "up 100baseTX-FX flow" when either of +two ports is found link-up. There is no functional provision to +see and control the media selection of them this moment. Advanced +features like flow volume bound, VLAN tag insertion/removal, QoS +DiffServ are not implemented and remain uncontrollable by the .Nm driver. UDP4CSUM is not very useful since the HW has an implementation