Re: modifying ethernet driver - advice needed

From: Geronimo W. Christ Esq (thegreatsuprendo_at_hotmail.com)
Date: 09/18/05

  • Next message: john.maximus_at_gmail.com: "Re: modifying ethernet driver - advice needed" 
    Date: Sun, 18 Sep 2005 18:32:10 +0100

    john.maximus@gmail.com wrote:

    > Actually, the driver is not a character driver in the true sense.
    >
    > It actually sends and recieves network packets (Only Ethernet Packets)
    > No TCP/IP.

    So it's an ethernet driver.

    > But I think the ethernet driver is closely coupled with the networking
    > code of linux.

    It does not have to be. There are routines that make it a lot easier to
    couple to Linux's IP stack, but you don't have to call them.

    > I dont have any ethernet driver running on my system.

    An ethernet driver is a bit of code which sends and receives ethernet
    packets. Since this is what your code does, therefore it is an ethernet
    driver.

    What is it you are trying to do ? You're sending and receiving the
    packets. Where are you getting the packet data to send, and what do you
    want to do with the packet data you receive ?

    > I tried modifying the enet code. but i dont know what the upper layer
    > passes to each of the driver functions.

    What "upper layer" ?

    > It passes some device and net_device structures and i dont know what
    > values these contain when it passes to the lower driver layer and what
    > modifications the upper layer do to these data structures.

    Linux Device Drivers (http://www.xml.com/ldd/chapter/book/) explains
    this quite well.

    > I need your advice in this regard. how can i solve and resolve my
    > problem and how do i go about it.

    We don't know much about what your problem actually is. You seem to be
    trying to modify an ethernet driver, but other than saying that you
    don't want to use TCP/IP you haven't given much info.

    > The reason why i want to do it is time.

    The reason why you want to do .. what exactly ?

    > sending/recieving the packets
    > must be very fast (very high performance sensitive).

    Why ? What is the use case ?

  • Next message: john.maximus_at_gmail.com: "Re: modifying ethernet driver - advice needed"

    Relevant Pages

    • Re: How to convert linux ethernet driver to wince driver
      ... WinCE Ethernet driver are NDIS driver, which is not the case of Linux ones, ... >> I have source code of this driver. ...
      (microsoft.public.windowsce.platbuilder)
    • Re: ethercons: ethernet console driver for 5-current
      ... >paper this summer on a Linux ethernet console driver, ... >implementing ethernet console support for FreeBSD. ... inserted into transmitted packets. ...
      (freebsd-current)
    • 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: There is no such thing as a "normal filter NDIS IM driver".
      ... Is it possible to filter modem packets through net stack? ... Or can I use USB/COM-port stack to capture modem packets? ... IM driver knows explicitly how to deal with those miniports. ...
      (microsoft.public.development.device.drivers)