From owner-freebsd-current@FreeBSD.ORG Fri Nov 11 05:42:07 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 17ED516A421; Fri, 11 Nov 2005 05:42:07 +0000 (GMT) In-Reply-To: <20051110212148.7a335fd9@vixen42.vulpes> from Vulpes Velox at "Nov 10, 2005 09:21:48 pm" To: v.velox@vvelox.net (Vulpes Velox) Date: Fri, 11 Nov 2005 05:42:07 +0000 (GMT) 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: <20051111054207.17ED516A421@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Cc: freebsd-current@freebsd.org Subject: Re: problems with NDIS driver and convertion for a Marvel Yukon Gigabit chip X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Fri, 11 Nov 2005 05:42:07 -0000 > Ran into a few problems with ndisgen today. > > I have to edit every instance of the following out to get it to > convert. > Magic Packet = "Magic Packet" > Pattern Match = "Pattern Match" > Mag Pack Patt Match = "Magic Packet & Pattern Match" > Link Change = "Link Change" > > > Upon loading the driver I get... > no match for ExUnregisterCallback > no match for ZwPowerInformation > no match for ExRegisterCallback > no match for ExCreateCallback > no match for ZwUnmapViewOfSection > no match for ZwMapViewOfSection > no match for ZwOpenSection > no match for wcslen > > Any chance of getting this working or any suggestions? > Ok, had I read the subject line of your mail fully I'd have known what driver it was. I'm a dolt and I've clearly had too long of a day. Here are the problems: - I don't know exactly what driver image you have. Unless you provide the URL for where you got it to put a copy somewhere, I can't really analyze it. - The .inf parser is not perfect. It's actually much stricter about syntax than Windows is. Stuff that works ok for Windows may be flagged as a syntax error by ndiscvt. If someone wants to help fix this, they're welcome to. (No kernel hacking required.) - I have no earthy idea why Marvell is referencing these functions in their driver. They're totally outside the NDIS spec. I'd be rather surprised that such a driver was able to get WHQL certification. (Assuming it did.) - This is Marvell. Given the rotten treatment I've had from them in the past, I'm not inclined to do them any favors now, so I'm not exactly inclined to fix this anytime soon. -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 =============================================================================