abarnas
Tue Aug 01 06:10:02 CDT 2006
I don't want to use standard serial driver because I don't want to use this
port to communicate with my own specific hardware in standard way. I need to
do this using few input/output lines which serial port has enough and one
line to signall event (interrupt). If I won't to use one of existing on
mainboard interface I have to buy special input/output card which can be
installed in PCI socket and communicate with world through it. I don't want
to do that because of cost (and in my case it is not necessary - serial port
interface has enough resources and I can adapt it to communicate with my
hardware).
Only standard driver which reserves logical resources is on my way.
â??Gary G. Littleâ?? pisze:
> Why can't you use the standard serial driver? No, you cannot access the
> serial resources as long as the standard driver owns them, but in nearly all
> cases, the assumption that a "special" driver is needed is not true.
>
> --
> The personal opinion of
> Gary G. Little
>
> "abarnas" <abarnas@discussions.microsoft.com> wrote in message
> news:8786C9F6-B39C-440C-9671-9CBB6EBCB4FB@microsoft.com...
> > Hi!
> >
> > I want to write driver for serial port (COM), but I don't want support
> > standard functions. For me that port has 2 outputs, 4 inputs and 1
> > interrupt
> > source. Unfortunatelly I cannot "reserve" I/O ports and interrupt vector
> > (IoReportResourceUsage fails) because standard driver has that resources
> > for
> > its own. When I turn off that serial port in BIOS, IoReportResourceUsage
> > succeed, but writing/reading to/from output/input lines has no effect.
> > Please for help, how to "disconnect" standard driver from one of serial
> > ports
> > (COM1 or COM2 - maybe another if exist) and "connect" to that port with my
> > driver.
> > Of cource my driver cannot figure as serial port on Windows' hardware
> > list.
> >
> > Thanks for any suggestions.
> > Best Regards.
>
>
>