Date: Wed, 23 Mar 2005 14:17:08 +0100 From: Phil Schulz <ph.schulz@gmx.de> To: lourik@wtec.co.za Cc: freebsd-questions@freebsd.org Subject: Re: Wireless Network NDIS Message-ID: <42416C54.5010303@gmx.de> In-Reply-To: <200503231509.19969.lourik@wtec.co.za> References: <200503231509.19969.lourik@wtec.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/23/05 14:09, Lourik Malan wrote: > HI there > > I get the following when i try an compile the following into the kernel. > > options NDISAPI > device ndis > device wlan > > /usr/src/sys/dev/if_ndis/if_ndis.c:85:30: ndis_driver_data.h: No such file or > directory > /usr/src/sys/dev/if_ndis/if_ndis_pccard.c:66:30: ndis_driver_data.h: No such > file or directory > /usr/src/sys/dev/if_ndis/if_ndis_pci.c:65:30: ndis_driver_data.h: No such file > or directory > mkdep: compile failed > *** Error code 1 > >From ndis(4): "To build a functional driver, the user must have a copy of the driver distribution media for his or her card. From this distribution, the user must extract two files: the .SYS file containing the driver binary code, and its companion .INF file, which contains the definitions for driver-specific registry keys and other installation data such as device identifiers. These two files can be converted into a ndis_driver_data.h file using the ndiscvt(8) utility. This file contains a binary image of the driver plus registry key data. When the ndis driver loads, it will create sysctl(3) nodes for each registry key extracted from the .INF file." So, in short: You'll need to run the supplied Windows driver through ndiscvt(8) before you can build the ndis module. Regards, Phil.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42416C54.5010303>