Generally speaking most users will not need this information -- it is provided only to support individuals targeting "unsupported" operating systems that wish and/or need to write their own drivers.
The ePadInk (IWedge) is designed to not require any vendor-supplied device drivers under MSFT win32 operating systems. It does this by using the existing HID-class protocol.
Options may be read/written to the device using Get/Set Report per the USB and HID class specifications. The data buffer for a FEATURE report must include the report id -- in other words it must be sizeof(reportData) + 1.
When we write a feature, the first byte is set to the report ID etc. and* it is passed to the device both in the setup packet AND as the first byte of data to the device.
When we READ a feature, although we write the 1st byte as the report ID it appears that MSFT returns the DATA starting at byte0.
1.5.4