This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: File operations on a Windows Driver (character device)

Alessio Faina writes:
> Well.....I wrote and answered myself the question you pointed out that
> is residing on stackoverflow....

Oh, small world :)

> It was my first option I thought of to pass the pointer to the virtual
> address to the userland application but
> I've been asked to mantain the architecture using open(), ioctl(),
> mmap() etc.... so I don't know, it's a kind of
> jolly to be played in case I won't be able to use the posix
> architecture....but reading on forums/mailing lists...
> I think I will be forced to use the kind of implementation I've
> described in the SO question.
> It seems that no-one ever have got the need to do something like I'm
> trying to do.
> 2015-05-19 9:52 GMT+02:00 Mark Geisert <XXXX <at> XXXXXX.XXX>:
> > Does
> >
> > help to answer your question?  If it does, you'll still have to decide
> > whether to translate the Windows calls there into Cygwin calls or instead
> > just localize the Windows calls in one user-level module and leave
> > everything else to Cygwin.

Cygwin is entirely and intentionally in user space.  Most of its users don't
even need programming access to Windows user space, let alone kernel space.
 So yes, you're likely to be forging a new path.

If you get it working with toy Windows test programs, we *might* be able to
tell you how to convert it to Cygwin, if it's possible.  But the actual
figuring it out for Windows is outside the scope of what Cygwin is intended
to provide.


Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]