<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WONTFIX - Allow to load firmware during run-time (after initialization)" href="https://bugs.freedesktop.org/show_bug.cgi?id=107168#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WONTFIX - Allow to load firmware during run-time (after initialization)" href="https://bugs.freedesktop.org/show_bug.cgi?id=107168">bug 107168</a> from <a class="email" href="mailto:alexdeucher@gmail.com" title="Alex Deucher <alexdeucher@gmail.com>"> Alex Deucher</a> <pre>(In reply to Paul Menzel from <a href="show_bug.cgi?id=107168#c2">comment #2</a>) > (In reply to Alex Deucher from <a href="show_bug.cgi?id=107168#c1">comment #1</a>) > > You need the firmware for initialization. > > What’s the technical reason for this. Why can’t certain parts of the > hardware be initialized later on? You can't do anything other than very limited modesetting until the firmwares are loaded. You might as well just use the efifb driver and then load the driver later after the filesystem is available. There's not really anything you can initialize without firmware. MC and SMC firmware are required to adjust the clocks which is required for performance and for bandwidth requirements for high res display configurations. You can't use the SDMA hardware without firmware so that means no GPU memory management or GPU VM updates and you are limited to 256 MB of vram (PCI BAR size) on most platforms. You can't use the gfx/compute engines without the CP firmware. You can't use the multi-media engines without firmware. Etc. Not to mention you now have multiple code paths to validate at the hw and sw level.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>