1.\" $NetBSD: kse.4,v 1.6 2007/10/19 05:11:07 nisimura Exp $ 2.\" 3.\" Copyright (c) 2006 Tohru Nishimura. 4.\" 5.\" Redistribution and use in source and binary forms, with or without 6.\" modification, are permitted provided that the following conditions 7.\" are met: 8.\" 1. Redistributions of source code must retain the above copyright 9.\" notice, this list of conditions and the following disclaimer. 10.\" 2. Redistributions in binary form must reproduce the above copyright 11.\" notice, this list of conditions and the following disclaimer in the 12.\" documentation and/or other materials provided with the distribution. 13.\" 3. All advertising materials mentioning features or use of this software 14.\" must display the following acknowledgement: 15.\" This product includes software developed by Tohru Nishimura. 16.\" 4. The name of the author may not be used to endorse or promote products 17.\" derived from this software without specific prior written permission. 18.\" 19.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR 20.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES 21.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. 22.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, 23.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 24.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 25.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 26.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 27.\" INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF 28.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 29.\" 30.Dd July 6, 2006 31.Dt KSE 4 32.Os 33.Sh NAME 34.Nm kse 35.Nd Micrel 8842/8841 PCI Ethernet controller driver 36.Sh SYNOPSIS 37.Cd "kse* at pci? dev ? function ?" 38.Sh DESCRIPTION 39The 40.Nm 41driver supports Ethernet interfaces based on the Micrel 8842/8841 42PCI Ethernet chips. The 8842 has 2 Ethernet ports which behave as 43a managed switch to bridge each other. It works like a T-shape 44connector of Ethernet data flow in which an Ethernet controller 45sits at the leg of the T. Frames can flow between the two ports 46while traffic destined for the 8842 reaches the EMAC. The 8841 is 47a plain 10/100 Ethernet. 48The 49.Nm 50driver distinguishs and handles them according to the HW model. 51.Sh SEE ALSO 52.Xr arp 4 , 53.Xr ifmedia 4 , 54.Xr netintro 4 , 55.Xr pci 4 , 56.Xr ifconfig 8 57.Sh AUTHORS 58The 59.Nm 60driver was written by 61.An Tohru Nishimura . 62.Sh BUGS 63__STRICT_ALIGNMENT case is not written. 8842 media selection 64keeps "auto" and indicates "up 100baseTX-FX flow" when either of 65two ports is found link-up. There is no functional provision to 66see and control the media selection of them this moment. Advanced 67features like flow volume bound, VLAN tag insertion/removal, QoS 68DiffServ are not implemented and remain uncontrollable by the 69.Nm 70driver. 71UDP4CSUM is not very useful since the HW has an implementation 72error for the case when a large UDP datagram is fragmented into 73MTU sized frames. 74