Date: Fri, 11 Nov 2005 19:09:32 -0600 From: Vulpes Velox <v.velox@vvelox.net> To: wpaul@FreeBSD.ORG (Bill Paul) Cc: freebsd-current@freebsd.org Subject: Re: problems with NDIS driver and convertion for a Marvel Yukon Gigabit chip Message-ID: <20051111190932.25ad86af@vixen42.vulpes> In-Reply-To: <20051111054207.17ED516A421@hub.freebsd.org> References: <20051110212148.7a335fd9@vixen42.vulpes> <20051111054207.17ED516A421@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 11 Nov 2005 05:42:07 +0000 (GMT) wpaul@FreeBSD.ORG (Bill Paul) wrote: > > 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. http://marvell.com/drivers/driverDisplay.do?dId=118&pId=6 IIRC the installer dumps it Program Files/Marvell It is where I grabbed the .sys and . > - 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.) Cool, any suggested reads? > - 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. Fun, what happened, if I may ask?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051111190932.25ad86af>