os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Remove outdated note about ndis not supporting USB, add list of card

Browse source 
types supported to previous paragraph.

Edit redundant language.

Clarify explanation of 32-bit versus 64-bit drivers.
This commit is contained in:
Warren Block 2012-04-18 03:33:14 +00:00
parent 705ca6c684
commit 83ffb4ec19
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=38690
1 changed files with 15 additions and 22 deletions

37
en_US.ISO8859-1/books/handbook/config/chapter.sgml
View file

@ -905,17 +905,12 @@ linuxemu/chapter.sgml -->
&os; NDISulator (otherwise known as Project Evil) takes a
&windows; driver binary and basically tricks it into
thinking it is running on &windows;. Because the
&man.ndis.4; driver is using a &windows; binary, it is only
usable on &i386; and amd64 systems.</para>
&man.ndis.4; driver is using a &windows; binary, it only
runs on &i386; and amd64 systems. PCI, CardBus, PCMCIA
(PC-Card), and USB devices are supported.</para>
<note>
<para>The &man.ndis.4; driver is designed to support mainly
PCI, CardBus and PCMCIA devices, USB devices are not yet
supported.</para>
</note>
<para>In order to use the NDISulator, you need three
things:</para>
<para>To use the NDISulator, three
things are needed:</para>
<orderedlist>
<listitem>
@ -932,27 +927,25 @@ linuxemu/chapter.sgml -->
</orderedlist>
<para>Locate the files for your specific card. Generally,
they can be found on the included CDs or at the vendors'
websites. In the following examples, we will use
they can be found on the included CDs or at the vendor's
website. In the following examples, we will use
<filename>W32DRIVER.SYS</filename> and
<filename>W32DRIVER.INF</filename>.</para>
<note>
<para>You can not use a &windows;/i386 driver with
&os;/amd64, you must get a &windows;/amd64 driver to make it
work properly.</para>
</note>
<para>The driver bit width must match the version of &os;.
For &os;/i386, use a &windows; 32-bit driver. For
&os;/amd64, a &windows; 64-bit driver is needed.</para>
<para>The next step is to compile the driver binary into a
loadable kernel module. To accomplish this, as
loadable kernel module. As
<username>root</username>, use &man.ndisgen.8;:</para>
<screen>&prompt.root; <userinput>ndisgen <replaceable>/path/to/W32DRIVER.INF</replaceable> <replaceable>/path/to/W32DRIVER.SYS</replaceable></userinput></screen>
<para>The &man.ndisgen.8; utility is interactive and will
prompt for any extra information it requires; it will
produce a kernel module in the current directory which can
be loaded as follows:</para>
<para>&man.ndisgen.8; is interactive and
prompts for any extra information it requires.
A new kernel module is written in the current directory.
Use &man.kldload.8; to load the new module:</para>
<screen>&prompt.root; <userinput>kldload <replaceable>./W32DRIVER_SYS.ko</replaceable></userinput></screen>