Re: Can a touchscreen driver be written as a user mode driver?



Do you have a BSP for this module? If so, it should be no problem building
a new image that contains the kernel mode touch driver. If you don't have a
BSP, then things are much more complicated.

If you are writing a standard touch driver, it will have to run in kernel
mode and be loaded by gwes. But to do that, you'll need to be able to
rebuild the image. You could potentially write a user mode driver that
could access the hardware you need, and then send points back to the
operating system. This wouldn't be a true touch driver though, and probably
would be difficult to implement.

Basically, with the BSP this shouldn't be an issue, life without it will be
difficult.
--
Dean Ramsier - eMVP
BSQUARE Corporation


"Steven Bass" <StevenBass@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E9FE6FF2-B742-479B-8E54-D1F7B8D385F8@xxxxxxxxxxxxxxxx


"Jack" wrote:

well since the touchdriver needs access to the HW you need to run it
in the kernel mode.


I thought drivers in CE6 could access hardware (memory and IO reads). But
I'm still coming up to speed, so maybe I'm wrong.

Since the touchscreen driver lives below the GWES, which is in kernel
space,
I figure that the touchscreen driver will need to be as well. That's what
I'm
trying to verify.

Steve


.