From: Gregory Shearman <zekeyg@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Can't build firmware into kernel
Date: Fri, 9 Dec 2011 16:50:51 +1100 [thread overview]
Message-ID: <20111209055050.GA8274@pacific.net.au> (raw)
In-Reply-To: <i5Zaa-3PK-5@gated-at.bofh.it>
In linux.gentoo.user, Lavender wrote:
> Thanks a lot ! But I used lspci -v | less, it printed vebose
> information, then I looked up carefully for my video card, but I did
> not find anything about R600,R700 or other like, I'm still not clear
> about R*** things , is it chipset name?
>>Hmm, I re-installed radeon-ucode package and I'm sure that I have
>>R600_rlc.bin cause I canlocate it in /lib/firmware/ and
>>/usr/src/linux/somewhere. But when I use make , the error message
>>like:make[1]: *** No rule to make target
>>`firmware/radeon/R600_rlc.bin', needed by
>>`firmware/radeon/R600_rlc.bin.gen.o'. Stop.make: *** [firmware] Error
>>2
> It's weird, because I think I have done all the Prerequisite
> correctly, so how could I fix it out ?
I think you need:
CONFIG_PREVENT_FIRMWARE_BUILD=y
Configured into your kernel.
Have a look at your dmesg output. It should have your Radeon card
version listed. Mine is a Radeon REDWOOD chip.
Here's my kernel config relating to building firmware into the kernel:
(ignore the fact that I wastefully build in all the chip versions other
than the REDWOOD)
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE="radeon/REDWOOD_pfp.bin radeon/REDWOOD_rlc.bin \
radeon/REDWOOD_me.bin radeon/CEDAR_pfp.bin radeon/CEDAR_rlc.bin \
radeon/CEDAR_me.bin radeon/CYPRESS_me.bin radeon/CYPRESS_pfp.bin \
radeon/CYPRESS_rlc.bin radeon/JUNIPER_me.bin radeon/JUNIPER_pfp.bin \
radeon/JUNIPER_rlc.bin carl9170-1.fw"
CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"
--
Regards,
Gregory.
next parent reply other threads:[~2011-12-09 5:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <i5Y4q-1XO-9@gated-at.bofh.it>
[not found] ` <i5MFY-7Um-9@gated-at.bofh.it>
[not found] ` <i5JI6-2X1-3@gated-at.bofh.it>
[not found] ` <i5K1s-3Em-9@gated-at.bofh.it>
[not found] ` <i5L7b-5rY-7@gated-at.bofh.it>
[not found] ` <i5Zaa-3PK-5@gated-at.bofh.it>
2011-12-09 5:50 ` Gregory Shearman [this message]
2011-12-09 6:55 ` Re:Re: [gentoo-user] Can't build firmware into kernel Lavender
[not found] <i6mJs-1ui-3@gated-at.bofh.it>
[not found] ` <i6laG-7az-9@gated-at.bofh.it>
[not found] ` <i65pg-5Kj-17@gated-at.bofh.it>
[not found] ` <i6lu1-7Rg-5@gated-at.bofh.it>
[not found] ` <i6GI9-15N-5@gated-at.bofh.it>
2011-12-11 4:42 ` Gregory Shearman
2011-12-10 2:42 Claudio Roberto França Pereira
2011-12-09 9:47 ` Lavender
2011-12-10 3:06 ` Re:Re: " Lavender
2011-12-10 4:25 ` Mick
-- strict thread matches above, loose matches on Subject: below --
2011-12-09 2:01 Re:Re: " Lavender
2011-12-08 13:47 ` James Broadhead
2011-12-08 10:44 ` Lavender
2011-12-08 10:59 ` James Broadhead
2011-12-08 12:15 ` Lavender
2011-12-09 3:08 ` Lavender
2011-12-09 6:59 ` Mick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111209055050.GA8274@pacific.net.au \
--to=zekeyg@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox