Are they aware the same issue appears to be happening with the Broxton firmware as well? Should that be tracked under a separate issue?
Are they aware the same issue appears to be happening with the Broxton firmware as well? Should that be tracked under a separate issue?