Hi Daniel,
Userspace can write a 24-bit value (encoded as a 6 character hex string)
to the 'object' sysfs entry to modify a single byte of the object table.
The hex string encodes a 3 bytes, in the following format:
TTFFVV
Where:
TT = object type
FF = object offset
VV = byte value
The object table is modified in device ram, which means the change is
volatile, and will be overwritten on the next device reset. To make
changes permanent, the new settings should be persisted in the device's
Non-Voltatile Memory using the updatenv sysfs entry.
Also, since the device driver initializes itself by reading some values
from the object table, the entire driver may need to be unloaded and
reloaded after writing the values for the driver to stay in sync. Whether
this is required depends on exactly which values were updated.
Signed-off-by: Daniel Kurtz <redacted>
---
Perhaps you could give an example of why this is needed?
Thanks,
Henrik