| 1 |
On Wednesday 01 Feb 2017 20:06:10 Ian Zimmerman wrote: |
| 2 |
> On 2017-02-01 22:34, Mick wrote: |
| 3 |
> > Device Drivers ---> |
| 4 |
> > |
| 5 |
> > Generic Driver Options ---> |
| 6 |
> > |
| 7 |
> > [*] Include in-kernel firmware blobs in kernel binary |
| 8 |
> > (intel-ucode/06-46-01 <other_CPU_firmware_follows_here>) |
| 9 |
> > |
| 10 |
> > External firmware blobs to build into the kernel binary |
| 11 |
> > |
| 12 |
> > (/lib/firmware/) Firmware blobs root directory |
| 13 |
> |
| 14 |
> That's exactly what I did too after seeing the root article in this |
| 15 |
> thread, and yes it works. |
| 16 |
> |
| 17 |
> I am puzzled by one thing, though: according to the Help text for the |
| 18 |
> first kernel option above (Include in-kernel firmware blobs), that |
| 19 |
> should actually compile in the firmware that ships with the kernel |
| 20 |
> itself, for _all_ compiled drivers. Yet I see at the end of "make |
| 21 |
> install": |
| 22 |
> |
| 23 |
> INSTALL /lib/firmware/4.4.46/radeon/R100_cp.bin |
| 24 |
> INSTALL /lib/firmware/4.4.46/radeon/R200_cp.bin |
| 25 |
> INSTALL /lib/firmware/4.4.46/radeon/R300_cp.bin |
| 26 |
> INSTALL /lib/firmware/4.4.46/radeon/R420_cp.bin |
| 27 |
> INSTALL /lib/firmware/4.4.46/radeon/RS690_cp.bin |
| 28 |
> INSTALL /lib/firmware/4.4.46/radeon/RS600_cp.bin |
| 29 |
> INSTALL /lib/firmware/4.4.46/radeon/R520_cp.bin |
| 30 |
> INSTALL /lib/firmware/4.4.46/radeon/R600_pfp.bin |
| 31 |
> INSTALL /lib/firmware/4.4.46/radeon/R600_me.bin |
| 32 |
> INSTALL /lib/firmware/4.4.46/radeon/RV610_pfp.bin |
| 33 |
> INSTALL /lib/firmware/4.4.46/radeon/RV610_me.bin |
| 34 |
> INSTALL /lib/firmware/4.4.46/radeon/RV630_pfp.bin |
| 35 |
> INSTALL /lib/firmware/4.4.46/radeon/RV630_me.bin |
| 36 |
> INSTALL /lib/firmware/4.4.46/radeon/RV620_pfp.bin |
| 37 |
> INSTALL /lib/firmware/4.4.46/radeon/RV620_me.bin |
| 38 |
> INSTALL /lib/firmware/4.4.46/radeon/RV635_pfp.bin |
| 39 |
> INSTALL /lib/firmware/4.4.46/radeon/RV635_me.bin |
| 40 |
> INSTALL /lib/firmware/4.4.46/radeon/RV670_pfp.bin |
| 41 |
> INSTALL /lib/firmware/4.4.46/radeon/RV670_me.bin |
| 42 |
> INSTALL /lib/firmware/4.4.46/radeon/RS780_pfp.bin |
| 43 |
> INSTALL /lib/firmware/4.4.46/radeon/RS780_me.bin |
| 44 |
> INSTALL /lib/firmware/4.4.46/radeon/RV770_pfp.bin |
| 45 |
> INSTALL /lib/firmware/4.4.46/radeon/RV770_me.bin |
| 46 |
> INSTALL /lib/firmware/4.4.46/radeon/RV730_pfp.bin |
| 47 |
> INSTALL /lib/firmware/4.4.46/radeon/RV730_me.bin |
| 48 |
> INSTALL /lib/firmware/4.4.46/radeon/RV710_pfp.bin |
| 49 |
> INSTALL /lib/firmware/4.4.46/radeon/RV710_me.bin |
| 50 |
> |
| 51 |
> and checking afterwards, yes these files are there, and by their mod |
| 52 |
> times they were created by the latest make install step. |
| 53 |
> |
| 54 |
> So, why are these firmware bits not built in now? |
| 55 |
|
| 56 |
I was puzzled in a similar fashion and played with adding the ucode blob file |
| 57 |
path first at the start and then at the end, of the in-kernel firmware blobs |
| 58 |
string. I think all these firmware blobs are being built in the kernel and |
| 59 |
loaded. In my case I looked in dmesg to see if the Radeon blob was l being |
| 60 |
loaded: |
| 61 |
|
| 62 |
[ 0.594298] [drm] Detected VRAM RAM=1024M, BAR=256M |
| 63 |
[ 0.594439] [drm] RAM width 128bits DDR |
| 64 |
[ 0.594867] [TTM] Zone kernel: Available graphics memory: 2008558 kiB |
| 65 |
[ 0.595037] [TTM] Initializing pool allocator |
| 66 |
[ 0.595188] [TTM] Initializing DMA pool allocator |
| 67 |
[ 0.595387] [drm] radeon: 1024M of VRAM memory ready |
| 68 |
[ 0.595533] [drm] radeon: 1024M of GTT memory ready. |
| 69 |
[ 0.595725] [drm] Loading RV730 Microcode <==< |
| 70 |
|
| 71 |
So I am guessing they are there ... in the kernel binary. No idea why the |
| 72 |
build output on the terminal changes. :-/ |
| 73 |
-- |
| 74 |
Regards, |
| 75 |
Mick |
Archives