Memory mapped IO to PCI driver
- From: paulgc3@xxxxxxxxx
- Date: 28 Jun 2006 10:14:55 -0700
Hello,
I like .NET CF 2.0. I love speed. I need both.
Situation: PCI device on CE 5.0. Memory mapped IO connectivity to
device.
Desires:
o I want to have my driver init routine return an address pointing to
the user mode address of the memory mapped region in the hardware.
o I want to PInvoke into this code to grab that pointer and load it
into an unsafe block in c#.
o I want to manipulate things in the hardware via .NET by using this
unsafe block to change values in the memory region I got from the prior
step.
I think this all works, but I am not peaked on the performance issues.
I belive that I can avoid all the pinvoke business this way (except for
the first one that sets things up) and do fast .NET access to the
hardware.
Can anybody comment on my peculiar approach? I am willing to take the
risks, but I am looking for people who understand the thing I am doing
at a CE internals level who may know reasons this is bad bad bad.
Thanks,
Paul
.
- Follow-Ups:
- Re: Memory mapped IO to PCI driver
- From: <ctacke/>
- Re: Memory mapped IO to PCI driver
- From: paulgc3
- Re: Memory mapped IO to PCI driver
- Prev by Date: Re: WMP wrapper in C# CF 2.0
- Next by Date: Re: Memory mapped IO to PCI driver
- Previous by thread: Re: Problem with socket communication for client (On handheld) / server (on PC) application
- Next by thread: Re: Memory mapped IO to PCI driver
- Index(es):
Relevant Pages
|