linux-kernel - Re: Kernel almost hangs when CONFIG_DRM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAG1a4rv8YirPpyYP735Zn3gpp-kcvvECd=-haZ-qx90_99x8aQ@mail.gmail.com>
Date:	Sun, 28 Aug 2011 17:47:59 -0400
From:	Pavel Ivanov <paivanof@...il.com>
To:	Borislav Petkov <bp@...en8.de>, Pavel Ivanov <paivanof@...il.com>,
	Michel Dänzer <michel@...nzer.net>,
	dri-devel@...ts.freedesktop.org,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Kernel almost hangs when CONFIG_DRM_RADEON=y

On Sun, Aug 28, 2011 at 1:36 AM, Borislav Petkov <bp@...en8.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?


Pavel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/