Quote:
Originally Posted by BMT
If it's an OS issue, rather than a kext issue, how is it that older versions of the DisplayLink software (2.1 for example) did not have this issue? - That suggests that it's the result of a change made by DisplayLink not the OS.
|
In 2.2 we started using a new API for an important part of the driver. The previous API has been deprecated and its reliability was rapidly decaying with every new OS version.
The new API has benefits but has some issues as well, one of which is the log spamming in some situations. We have raised all issues with Apple.
I cannot share any more information on this I'm sorry
Cheers
Carlo