Kernel almost hangs when CONFIG_DRM_RADEON=y
bp at alien8.de
Sun Aug 28 22:49:26 PDT 2011
On Sun, Aug 28, 2011 at 05:47:59PM -0400, Pavel Ivanov wrote:
> On Sun, Aug 28, 2011 at 1:36 AM, Borislav Petkov <bp at alien8.de> 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 this issue. Should I set some special parameter?
> > You need to add "radeon/CEDAR_pfp.bin" to CONFIG_EXTRA_FIRMWARE when you
> > configure your kernel and enable CONFIG_FIRMWARE_IN_KERNEL.
> > The radeon/CEDAR_pfp.bin file (+ leading directory, mind you) should
> > most probably be located in /lib/firmware or to whatever you have set
> > CONFIG_EXTRA_FIRMWARE_DIR so that Kbuild can find it (if not, you'll get
> > a warning at the end of the kernel build). This way, it works for both
> > radeon being =m and =y.
> Everything else in /lib/firmware/radeon is needed after user space
> become available?
You mean the other *.bin files? If so, not for your case, AFAICT - your
driver is requesting CEDAR_pfp.bin only, correct? But I mean, it won't
hurt if you leave them all there, they're under 1M.
You should recheck and add any other .bin files to the
CONFIG_EXTRA_FIRMWARE string so that radeon.ko is satisfied :).
More information about the dri-devel