From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 08:38:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id C039116A4CF; Mon, 26 Jan 2004 08:38:25 -0800 (PST) In-Reply-To: from Danny Braniss at "Jan 26, 2004 10:58:53 am" To: danny@cs.huji.ac.il (Danny Braniss) Date: Mon, 26 Jan 2004 08:38:25 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20040126163825.C039116A4CF@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) cc: freebsd-current@freebsd.org Subject: Re: Project Evil: The Evil Continues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jan 2004 16:38:25 -0000 > i tried with this pci card, but i guess i screwed up somewhere ... > > ndis0: port 0xdcc0-0xdcdf mem > 0xff000000-0xff00ffff,0xff010000-0xff010fff > no match for NdisMDeregisterDevice > no match for NdisMRegisterDevice > no match for NdisCancelTimer > no match for NdisInitializeTimer > ndis0: NDIS API version: 5.1 > NDIS dummy called... No, you didn't screw up: I still need to implement these routines. I didn't realize there was both an NdisInitializeTimer() and NdisMInitializeTimer(). Most miniport drivers use NdisMInitializeTimer(). Anyway, this is exactly the sort of information I was looking for: I'll try to get these functions implemented ASAP. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose =============================================================================