Quote:
Originally Posted by knc1
From your description of what "MARKER" does (acts like a token to select which one of the multiple pix processing "jobs" to send the ioctl to)...
Maybe the only change is that before 5.1 there was only one MARKER(token) in use by the Amazon application - the one which you where using in your code.
And that now, starting with 5.1 the Amazon application is using more than that single MARKER(token).
I.E: Maybe 5.1 just marks the point where the Amazon application started to use the multiple pixel processing feature.
Not a actual change in the source code of how the ioctl() is handled, a change in the propriatary Amazon code.
Just some additional thoughts, in case you don't find anything of significance in the 5.1 diff's
|
According to the freescale documentation, the update marker is just a unique arbitrary value that you select when you do an update call that does not have the "wait for completion" bit set. Later when (if) you want to wait for a specific update to complete, you call a "wait for update completion" ioctl call with the unique marker that was used on the update call you want to wait for.
The only exception is marker value zero. According to several different websites, update marker value zero has a special use -- it crashes the driver.
