Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
pt:manual:deblob_a_kernel_patch [2022/03/08 02:39] i3_relativism ↷ Page moved from pt:installation:deblob_a_kernel_patch to pt:manual:deblob_a_kernel_patch |
pt:manual:deblob_a_kernel_patch [2024/11/04 22:18] (current) luck02 [How to use deblob-check to deblob kernel patches?] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ... (WIP) | ... (WIP) | ||
| - | ====== | + | ====== |
| Sometimes, there are drivers aren't available from official Linux kernels such as specific drivers and device trees for ARM architecture adapted for certain SoCs, however a lot of them contains nonfree drivers or blobs, then is needed deblob them to protect your freedom. | Sometimes, there are drivers aren't available from official Linux kernels such as specific drivers and device trees for ARM architecture adapted for certain SoCs, however a lot of them contains nonfree drivers or blobs, then is needed deblob them to protect your freedom. | ||
| - | ===== What is a blob? ===== | + | ===== O que é um bloco? ===== |
| A **Blob** is a piece of object code distributed without source, usually firmware to run some device. That firmware is distributed only in object code form, under a nonfree license. | A **Blob** is a piece of object code distributed without source, usually firmware to run some device. That firmware is distributed only in object code form, under a nonfree license. | ||
| Line 37: | Line 37: | ||
| </ | </ | ||
| - | In this case, you should check if those references were deblobbed in deblob-x.y of the kernel version that you are using. You can get it at the [[http:// | + | In this case, you should check if those references were deblobbed in deblob-x.y of the kernel version that you are using. You can get it at the [[http:// |
| If those references aren't available in Linux-libre source yet, then you should check if those references aren't false positives. If the first reference (eg. request_firmware_direct) is requesting a blob, then you should rename **request_firmware_direct** to **reject_firmware_direct** and if the second one (wl18xx-conf.bin) is a blob, you must replace it with ** / | If those references aren't available in Linux-libre source yet, then you should check if those references aren't false positives. If the first reference (eg. request_firmware_direct) is requesting a blob, then you should rename **request_firmware_direct** to **reject_firmware_direct** and if the second one (wl18xx-conf.bin) is a blob, you must replace it with ** / | ||