radu
Member level 2
- Joined
- May 30, 2001
- Messages
- 51
- Helped
- 1
- Reputation
- 2
- Reaction score
- 1
- Trophy points
- 1,288
- Location
- Baenre compound, MENZOBERRANZAN
- Activity points
- 398
Hello all,
I'm wondering if any of you have tried to allocate an address range using the NO BACKING STORE option in windows. If so (given that you have to handle the data passing yourself with RtlCopyMemory() ), do you have any suggestions as to what kind of data structure should be used for the buffers?
For example: (this is an example of Bill Mackenzie from wd-3)
.....
case TCODE_WRITE_REQUEST_QUADLET:
{
//copy the quadlet data TO our receive buffer at the offset specified in request packet
RtlCopyMemory
( (PCHAR)pDeviceExtension->pReceiveBuffer + offset, (PCHAR)&pRequestPacket->u3.OHCI_Quadlet_Data,
sizeof(ULONG)
);
It is not clear to me as to what pReceiveBuffer should point to; obviously it should be of type char, but an array/list or what?
I'm a hardware guy, this is my first driver project don't be to hard on me
I'm wondering if any of you have tried to allocate an address range using the NO BACKING STORE option in windows. If so (given that you have to handle the data passing yourself with RtlCopyMemory() ), do you have any suggestions as to what kind of data structure should be used for the buffers?
For example: (this is an example of Bill Mackenzie from wd-3)
.....
case TCODE_WRITE_REQUEST_QUADLET:
{
//copy the quadlet data TO our receive buffer at the offset specified in request packet
RtlCopyMemory
( (PCHAR)pDeviceExtension->pReceiveBuffer + offset, (PCHAR)&pRequestPacket->u3.OHCI_Quadlet_Data,
sizeof(ULONG)
);
It is not clear to me as to what pReceiveBuffer should point to; obviously it should be of type char, but an array/list or what?
I'm a hardware guy, this is my first driver project don't be to hard on me
