driver design question

From: Derek Pitcher (derekpitcher_at_yahoo.com)
Date: 07/28/04 

Date: 27 Jul 2004 19:35:36 -0700

I need to implement a simple driver for interfacing with another
device over PCI. I am envisioning a packet-based design whereby the
cpu will write a packet into a memory block, and notify the receipient
when done. The receive direction works similarly, the device will dump
data into memory, and interrupt when complete.
In looking through docs, it seems that the best paradigm with this
design is to use a network device driver, since the device asks to
transfer packets into the kernel.
If this is the case, then I don't need all of the overhead associated
with an ethernet driver, since this is a simple proprietary protocol.

All that I'm envisioning is that the driver simply needs to transfer
packets from the device -> kernel -> receiving user.

Is there some minimal network driver which doesn't require the
overhead of ehternet/ip etc (essentially a raw driver), or is there a
better driver
design paradigm to use.

TIA,
Derek

Relevant Pages

  • Re: Filter Hook
    ... the callback routine is been invoked at DISPATCH_LEVEL. ... If you really have to keep such a queue for the packets, then the IP filter driver is not suitable for your needs since you have to process all the packets in the callback routine without any wait actionand return it to the tcpip driver immediately when the callback routine returns. ... What IRQL are you running at when you crash, ...
    (microsoft.public.development.device.drivers)
  • Re: MAC bridging and sniffing packets with specific Ethertype
    ... That is, the Ethernet adapters are bound to the Mbridge driver (which, since ... Mbridge handles the bridging of packets between the adapters. ...
    (microsoft.public.windowsce.embedded)
  • Re: Test on 10GBE Intel based network card
    ... Who ya gonna call, why me of course, its my driver:) ... ix0: ... Driver dropped packets = 0 ... ix1: ...
    (freebsd-performance)
  • Re: Degradation of TCP connection
    ... and running ifconfigon the target does indeed show ... the huge number of dropped Rx packets, ... RX stall (possibly due to mishandled RX overrun in the driver) ... RX interrupts have stopped firing ...
    (comp.os.vxworks)
  • Re: Degradation of TCP connection
    ... "Each of our boards will have an ethernet driver specific ... once you get a target into a failed state, ... when the VxWorks box stops ACKing packets sent from the Windows box. ...
    (comp.os.vxworks)