Originally posted by deanjo
View Post
but still... is it a case of a control 'bit' being set/unset on or off wrongly, or a 'real hardware errata' that they know about and have not fixed, did anyone bother to report this known error on [email protected] for instance ?
Comment