2011/8/27 Michel Dänzer :
>> I observe very strange behavior dependent on value of
>> CONFIG_DRM_RADEON parameter. When it's set to m everything works very
>> good, no problem. When I set it to y I see kernel hang during boot. Or
>> I should better say it "almost hangs" because during last boot att
On Sun, Aug 28, 2011 at 1:36 AM, Borislav Petkov wrote:
>> > With CONFIG_DRM_RADEON=y, the microcode is needed before it can be
>> > loaded from userspace, so it needs to be built into the kernel as well.
>>
>> How should I do that? I've tried to set all "m"s to "y" in .config and
>> still saw thi
Hi,
I observe very strange behavior dependent on value of
CONFIG_DRM_RADEON parameter. When it's set to m everything works very
good, no problem. When I set it to y I see kernel hang during boot. Or
I should better say it "almost hangs" because during last boot attempt
I accidentally waited a litt
2011/8/27 Michel D?nzer :
>> I observe very strange behavior dependent on value of
>> CONFIG_DRM_RADEON parameter. When it's set to m everything works very
>> good, no problem. When I set it to y I see kernel hang during boot. Or
>> I should better say it "almost hangs" because during last boot att
On Sun, Aug 28, 2011 at 1:36 AM, Borislav Petkov wrote:
>> > With CONFIG_DRM_RADEON=y, the microcode is needed before it can be
>> > loaded from userspace, so it needs to be built into the kernel as well.
>>
>> How should I do that? I've tried to set all "m"s to "y" in .config and
>> still saw thi
