On Tue, Aug 28, 2012 at 07:09:14PM -0000, Joseph Salisbury wrote:
> As a work-around, you may be able to blacklist the cirrus kernel module.
Given that KVM is the dominant use case for the cirrus driver, can I suggest
that this be done in the kernel package itself by not building the broken
driver until this is resolved?
On Tue, Aug 28, 2012 at 07:09:14PM -0000, Joseph Salisbury wrote:
> As a work-around, you may be able to blacklist the cirrus kernel module.
Given that KVM is the dominant use case for the cirrus driver, can I suggest
that this be done in the kernel package itself by not building the broken
driver until this is resolved?