Re: KSPROPERTY_TYPE_SET cannot return data??



Tom,

I've never done set-modify-return on the user mode side, which is what you
are trying to do. However it is something that obviously works and ksxbar.ax
uses that all the time.
Can you post how you define your property item in question (should be
similar to 'can route' item from xbar set), your 'set' handler from that
item and your user mode code.

If I don't see anything obviously wrong I can still ask around. The chances
are high that we can figure things out for you if you can wait a few days.

-- Max.




"Tom Udale" <-> wrote in message
news:ivudncFBu98L1yPZnZ2dnUVZ_oqdnZ2d@xxxxxxxxxxxxxx
Dear Max,

Yes, in my experience M must be = N.
Don't remember why.

Just design your data structure accordingly.

Well, I am not sure whether to be happy or sad but it did not seem to
work.

I went all the way down the Microsoft style road, passing the same
structure
for input and output and copying the input to the output in KM before
setting my output information. Still, in UM, my output structure is
completely untouched. I also adjusted the MinProperty/MinData parameters
in
the KSPROPERTY_ITEM as appropriate and that did not seem to make any
difference either.

Is there some flag I am missing on my UM call (this part I do not have
with
respect to the atixbar example, so I cannot see how they call from UM).
Maybe do I have to OR SRB_GET_DEVICE_PROPERTY and SRB_SET_DEVICE_PROPERTY
together or some such thing (I am indeed grasping at straws here). Or
perhaps some flag on the property set in general?

The very mad thing is that my SRB_GET_DEVICE_PROPERTY code is exactly the
same as my original SRB_SET_DEVICE_PROPERTY, with the M!=N sized input and
output parameters, and it works fine. Furthermore, I find it very odd
that
not only does KsProperty() succeed, but it reports that is wrote the
correct
amount of data in the BytesReturned parameter. Where exactly does it
think
it wrote it??



Best regards,

Tom




.



Relevant Pages

  • Re: PSL_RF inclusion in PSL_USERCHANGE for i386
    ... PSL_RF (Flag to ensure single-step only happens once per instruction.). ... but popfl doesn't set it for me now and user mode cannot execute iret. ... CPU that sets PSL_RF for faults (for all faults or only for debug ...
    (freebsd-arch)
  • Re: PSL_RF inclusion in PSL_USERCHANGE for i386
    ... that with a mask of allowed flags to be changed. ... PSL_RF (Flag to ensure single-step only happens once per instruction.). ... but popfl doesn't set it for me now and user mode cannot execute iret. ...
    (freebsd-arch)
  • RE: Interrupt Handling
    ... but then somehow it would notify user mode code. ... it can only queue a dpc routine. ... You can do all of this, and of course you can turn interrupts off on ...
    (microsoft.public.development.device.drivers)
  • Re: MmMapIoSpace for applications in CE 6.0?
    ... No one ever said there was no way for user mode code to access physical memory. ... The important distinction here is that the user mode code cannot create mappings of arbitrary physical addresses into user mode space. ... DDRAW is part of GWES and thus part of the kernel, so it CAN create mappings to a given process on behalf of the user mode code that it's working with. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: how to get data from mirror driver
    ... I know that how to send/receive data from user mode to kernel ... but is there any data structure that is available for mirror ... driver that returns me screen data(how can i get this screen data?) ...
    (microsoft.public.development.device.drivers)