none
Regarding Serial port Driver RRS feed

  • Question

  • Hi all

    i am new to driver development, and i am currently referring to Walter Oney's WDM Second Edition.

    in that there is a sample driver for PCI Chip s5933, as i don't have this chip set, I decided to use the serial port (RS232) for reading and writing data and also handling the interrupt.

    But to modify the PCI code to support the serial port hardware, where do i get the following information, what is the equivalent for Serial Port RS232 hardware.

    // This is for PCI hardware

    #define MWAR  0x24  // write address register
    #define MWTC  0x28  // write transfer count register
    #define MRAR  0x2C  // read address register
    #define MRTC  0x30  // read transfer count register
    #define MBEF  0x34  // mailbox empty/full status
    #define INTCSR  0x38  // interrupt control/status register
    #define MCSR  0x3C  // bus master control/status register

    any ideas or suggestion is appreciated

     

    regards
    REkha

    Friday, November 30, 2012 9:48 AM

Answers

  • You need to understand that there is a DriverEntry routine and that is about it between a simple WDM and KMDF driver.    Yes in the future you may want a Kernel Service API that was part of WDM, but the challenge to learn in WDM is the plug and play state machine, power management, and request cancelation and all of these are addressed by KMDF.   Today the recommended approach is to learn KMDF then branch into WDM since WDM is a lot harder.


    Don Burn Windows Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr

    Sunday, December 2, 2012 6:14 PM

All replies

  • First if you are new to driver development WDM is the wrong model to use.  Get "developing Drivers for the Windows Driver Foundation" and start looking at KMDF.  Take a look at the samples in the WDK, there are several that work with common boards, or you can get some simple hardware from OSR https://www.osronline.com/custom.cfm?name=index_fullframeset.cfm&pageURL=https://www.osronline.com/store/index.cfm


    Don Burn Windows Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr

    Friday, November 30, 2012 12:19 PM
  • First of all thanks for replying.

    Donald D.Burn: "First if you are new to driver development WDM is the wrong model to use. "

    Rekha: You mean to say, without understanding DriverEntry Routines, AddDevice and other Kernel APIs, i can start with KMDF.

    my intention was to move to KMDF ASAP, but i thought i will try at least one full Function Driver in WDM (example the PCI or Serial Port) and then move on to KMDF.

    please tell me what you think ?

    regards

    Rekha

    Sunday, December 2, 2012 3:04 PM
  • You need to understand that there is a DriverEntry routine and that is about it between a simple WDM and KMDF driver.    Yes in the future you may want a Kernel Service API that was part of WDM, but the challenge to learn in WDM is the plug and play state machine, power management, and request cancelation and all of these are addressed by KMDF.   Today the recommended approach is to learn KMDF then branch into WDM since WDM is a lot harder.


    Don Burn Windows Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr

    Sunday, December 2, 2012 6:14 PM