To use DriverWizard:
****************************************************************************************
| NOTE | |
| When selecting the virtual PCI device option, the DriverWizard allows you to define the device's resources. By specifying the IO/Memory ranges, you may further define run-time registers (the offsets are relative to BARs). In addition, the IRQ must be specified if you want to generate code that acknowledges interrupts via run-time registers. Note, that the IRQ number and the size of the IO/Memory ranges are irrelevant, since these will be automatically detected by DriverWizard when you install a physical device. |
For non-Plug and Play cards, select ISA. To generate code for a PCI device that is not currently attached to the computer, select PCI: PCI Virtual Device.
If you do not need to generate an INF file, skip this step and proceed to the next one.
To generate the INF file with the DriverWizard, follow the steps below:
On Windows 2000/XP/Server 2003/Vista you can choose to automatically
install the INF file from the DriverWizard by checking the
Automatically Install the INF file option in the
DriverWizard's INF generation dialogue.
On Windows 98/Me you must install the INF file manually,
using Windows Add New Hardware Wizard or
Upgrade Device Driver Wizard, as explained in
section 15.1.
If the automatic INF file installation on Windows 2000/XP/Server 2003/Vista fails,
DriverWizard will notify you and provide manual installation
instructions for this OS as well.
****************************************************************************************
| NOTE | |
| To use Message-Signaled Interrups (MSI) or Extended Message-Signaled Interrups (MSI-X) on Windows Vista (for PCI cards that support MSI/MSI-X) you will need to modify or replace the generated DriverWizard INF file to include specific MSI information, otherwise WinDriver will attempt to use legacy level sensitive interrupt handling for your card, as explained in section 9.2.6.1 of the manual. |
If you do not need to uninstall an INF file, skip this step and proceed to the next one.
For non-Plug-and-Play hardware, define your hardware's resources manually.
You can define the registers manually.
****************************************************************************************
| NOTE | |
| You have the option to check the Auto Read box in the Register Information window. The registers that are marked with the Auto Read option will automatically be read with any register read/write operation performed from the Wizard (the read results will be displayed in the wizard's Log window). |
****************************************************************************************
| NOTE | |
| When accessing memory mapped ranges, be aware that Linux PowerPC uses big-endian for handling memory storage, as opposed to the PCI bus that uses little-endian. For more information regarding little/big-endian issues, refer to section 9.3. |
****************************************************************************************
| NOTES | |
|
****************************************************************************************
| NOTE | |
| Before generating Kernel PlugIn code you must install Microsoft's Driver Development Kit (DDK) for your target OS(s). |