Ethernet drivers normally fit into a standard architecture. For VxWorks, this would be VxWorks specific, but it resembles other Unix network driver models. Apart from interfacing with the network stack (which you would need to implement yourself), the driver needs to “talk” to the NIC hardware. You can use DriverBuilder’s generic hardware access routines to access the NIC hardware. The main advantage in this case would be that you can reuse the hardware handling code on Linux, Windows or any other OS that WinDriver supports.