Date: Sat, 25 Jan 2003 23:55:20 +0100 From: Joerg Wunsch <j@uriah.heep.sax.de> To: "M. Warner Losh" <imp@bsdimp.com> Cc: mobile@freebsd.org Subject: Re: How to make an Intel EtherExpress known to xe(4)? Message-ID: <20030125235520.A97813@uriah.heep.sax.de> In-Reply-To: <20030125.151358.95772758.imp@bsdimp.com>; from imp@bsdimp.com on Sat, Jan 25, 2003 at 03:13:58PM -0700 References: <20030125225051.B95899@uriah.heep.sax.de> <20030125.151358.95772758.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
As M. Warner Losh wrote: > : In addition to make it known to the files in /sys/dev/xe/, > : what else needs to be done to handle this card? > > Index: if_xe_pccard.c ... > Should be all that's needed, unless it has a modem built-in. Yep, thanks, it is all to make it known: xe0: <Intel EtherExpress PRO/100> at port 0x100-0x10f irq 11 function 0 config 1 on pccard0 xe0: Intel CE3, bonding version 0x45, 100Mbps capable xe0: DingoID = 0x444b, RevisionID = 0x1, VendorID = 0 xe0: Ethernet address 00:a0:c9:bc:b5:ef However, when trying to use it i get: xe0: discard oversize frame (ether type 800 flags 3 len 1518 > max 1514) This didn't happen with that card under 4.x. I might look into the differences... The connection is not usable that way, it seems all packets are thrown away as being oversized. Maybe as a workaround just assume it's a full-sized packet, and only discard the `oversized' bytes? If this was in error, the higher protocol layers will throw the packet away anyway. I'll eventually tcpdump both ends. It's not a show-stopper right now, i've also got a 3C589xxx i can use. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030125235520.A97813>