From owner-freebsd-mobile Sat Jan 25 15: 0: 7 2003 Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A27EE37B401 for ; Sat, 25 Jan 2003 15:00:05 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58C4043ED8 for ; Sat, 25 Jan 2003 15:00:04 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id AAA24192; Sun, 26 Jan 2003 00:00:02 +0100 (CET) Received: from uriah.heep.sax.de (localhost.heep.sax.de [127.0.0.1]) by uriah.heep.sax.de (8.12.6/8.12.6) with ESMTP id h0PMtLRL097998; Sat, 25 Jan 2003 23:55:21 +0100 (MET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.12.6/8.12.6/Submit) id h0PMtK7Q097997; Sat, 25 Jan 2003 23:55:20 +0100 (MET) Date: Sat, 25 Jan 2003 23:55:20 +0100 From: Joerg Wunsch To: "M. Warner Losh" Cc: mobile@freebsd.org Subject: Re: How to make an Intel EtherExpress known to xe(4)? Message-ID: <20030125235520.A97813@uriah.heep.sax.de> Reply-To: Joerg Wunsch References: <20030125225051.B95899@uriah.heep.sax.de> <20030125.151358.95772758.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20030125.151358.95772758.imp@bsdimp.com>; from imp@bsdimp.com on Sat, Jan 25, 2003 at 03:13:58PM -0700 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org 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: 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