This file confirms that we are indeed defining all the required keys (including kIOMaximumSegmentByteCount) before calling UserReportHBAConstraints, and it also demonstrates the SetProperties workaround we implemented to bypass the issue. Ahh, I see what’s going on. I believe UserReportHBAConstraints actually sets those values at the controller level (not the peripheral), and your ioreg snippet didn’t include the controller. Can you upload a full IORegistryExplorer snapshot just so I can confirm everything is correct? Aside from that, having read through the bug again, I think setting kIOMaximumByteCountRead/WriteKey on the peripheral is probably your best option. I want to double-check that with the engineering lead (he’s out sick today) just in case I’ve missed something, but I don’t think that will change anything. __ Kevin Elliott DTS Engineer, CoreOS/Hardware
Topic:
App & System Services
SubTopic:
Drivers
Tags: