From owner-freebsd-mobile Tue Jan 28 14:30:12 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 2520337B401; Tue, 28 Jan 2003 14:30:11 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E36C43E4A; Tue, 28 Jan 2003 14:30:09 -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 XAA21682; Tue, 28 Jan 2003 23:30:03 +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 h0SMLkRL088962; Tue, 28 Jan 2003 23:21:46 +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 h0SMLjkr088961; Tue, 28 Jan 2003 23:21:45 +0100 (MET) Date: Tue, 28 Jan 2003 23:21:45 +0100 From: Joerg Wunsch To: Scott Mitchell Cc: "Greg 'groggy' Lehey" , mobile@FreeBSD.ORG, Kevin Oberman Subject: Re: How to make an Intel EtherExpress known to xe(4)? Message-ID: <20030128232145.J85085@uriah.heep.sax.de> Reply-To: Joerg Wunsch References: <20030125235520.A97813@uriah.heep.sax.de> <20030125230756.BC4195D06@ptavv.es.net> <20030127000131.B27981@uriah.heep.sax.de> <20030128015118.GQ56320@wantadilla.lemis.com> <20030128150749.GA29247@fishballoon.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20030128150749.GA29247@fishballoon.dyndns.org>; from scott@uk.freebsd.org on Tue, Jan 28, 2003 at 03:07:49PM +0000 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 Scott Mitchell wrote: > That comment about not knowing what most of the config bits do was > obviously written before I got hold of the programming manual :-) > I'll have a look tonight and see what the 'CRC' bit actually does. Ah, didn't know you've got the docs now. It seems they are only available under NDA, unfortunately. According to Werner Koch, the XIRCREG40_RMASK0 is not the register to fiddle, it only contains an interrupt bit mask. There's another bit that makes the chip not /sending/ a CRC, but he didn't find anything quickly that would it make not delivering the CRC with the received frame. -- 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