X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding; q=dns; s=
	default; b=tQVszxlsrzUCI4EXc0RW6cuu7pWP/xIErSYugGelSk2+oxPWK52Uo
	GsmbOHdnfBTTr9I2hza2UIBkwmCMwPn1RCiDYgqyOFN1SiKVuYOdLnYgZx0cuDsn
	DWB5zXgD/0jmZMC7NoqBl5TYr1+arKwPRRzDQrmQlnn6Uzl01PjZvI=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding; s=default;
	 bh=P4F52OtAmKqE+UllDl9DyE61RUc=; b=HFegZ1yO10xahDWcYiB+vNkUHyvB
	DBvc1ptyBSR7Ik2hFH0emWr8TUsTY9AhymCG+MW+QdeMBL7PUkLwT64M5zTacITl
	xg3cEVCvw10HsCCvBdROgK2qEwBj91gDu3Gf/9zn7Zd7VZwtzmMKrynDbFCeP74A
	wM1pU/O7WGfGViw=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2
X-HELO: plane.gmane.org
To: cygwin AT cygwin DOT com
From: Mark Geisert <mark AT maxrnd DOT com>
Subject: Re: File operations on a Windows Driver (character device)
Date: Wed, 20 May 2015 01:19:27 +0000 (UTC)
Lines: 36
Message-ID: <loom.20150520T030416-888@post.gmane.org>
References: <CACs=mWDRGh9KZBT45=8yy4J6h62v0RNYxczV91qRhhb8LcfY4Q AT mail DOT gmail DOT com>	<5559FB9E DOT 3040200 AT cygwin DOT com>	<CACs=mWCO8ejvsufP3C_HFAiKDrcsanGZ+J_EuQQGOm+u30T_zg AT mail DOT gmail DOT com>	<loom DOT 20150519T094146-560 AT post DOT gmane DOT org> <CACs=mWBEe2CqkN=tizTMcCXLxvbkwNat8Uch_CTPSaDgFCUmYQ AT mail DOT gmail DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes

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
> >
http://stackoverflow.com/questions/29938573/accessing-kernel-memory-from-user-mode-windows
> > 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.

..mark


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple