Communication with PCIe device; reading/writing hw registers
- From: ta <ta@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 28 Jan 2009 05:12:01 -0800
Hi there,
I'm fairly new to driver development, but I am supposed to write a driver
for a device under windows, which does already have a driver for Linux.
In Linux it is done in such a way that all the device's registers are mapped
to a virtual filesystem, which can be accessed in user address space. This
allows to modify the registers quite simply.
As far as I know, IOCTLs are the preferred way to communicate between user
and kernel space. As far as I can foresee, the driver needs to run in KMDF.
But is there another way, possibly a more elegant way, to communicate between
user space and kernel space? In order to be able to communicate with hardware
device, I would assume to use quite a lot IOCTLs, which as I personally would
think, makes things quiet confusing and hard to keep track of. Therefore, my
question: is there another way to handle the device, for example to map a
handle from kernel space to user space, which will allow me to work with the
hardware device or something similar, what ever you can think of?
.
- Follow-Ups:
- Re: Communication with PCIe device; reading/writing hw registers
- From: Pavel A.
- Re: Communication with PCIe device; reading/writing hw registers
- From: Maxim S. Shatskih
- Re: Communication with PCIe device; reading/writing hw registers
- From: Don Burn
- Re: Communication with PCIe device; reading/writing hw registers
- Prev by Date: Re: pnputil vs. device manager
- Next by Date: Re: Communication with PCIe device; reading/writing hw registers
- Previous by thread: mount manager drive letter
- Next by thread: Re: Communication with PCIe device; reading/writing hw registers
- Index(es):
Relevant Pages
|
