Quote:
Originally Posted by knc1
Your correct.
The ioctl() commands, once released, are supposed to be engraved in stone.
The addition of a new (or changed) one is supposed to overlap the continued existance of the one being replaced.
So the maintainer of the e-ink driver screwed the pooch on letting that change(s) in.
|
Yes, that pooch is getting a sore behind from the 5.1.0 update -- that is for sure!
They inserted new fields into the middle of a critical structure used by the eink udpate ioctl, moving other critical fields, and they did not even bother to rename this new stucture layout to maintain compatibility between 5.1.x and 5.0.x firmware. That means you need different program versions that use different structure layouts to do eink updates, depending on whether you booted from the main or from the diags partitions, after you install the 5.1.0 firmware update.
I tried copying the old field values from their new location into the new fields in their old location, and of course that breaks eink updates on the new firmware. The iotcl codes are modified by the structure length, so those different structures cause different codes to be used. Grr... 
That pooch won't be sitting down for quite awhile.
