<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Allow to load firmware during run-time (after initialization)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107136">107136</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Allow to load firmware during run-time (after initialization)
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>DRI git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>pmenzel+bugs.freedesktop@molgen.mpg.de
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Building the i915 driver into the Linux kernel, that means not as a module,
*without* an initrd image, the message below is shown.
[ 0.427657] i915 0000:00:02.0: Direct firmware load for
i915/skl_dmc_ver1_27.bin failed with error -2
[ 0.428121] i915 0000:00:02.0: Failed to load DMC firmware
i915/skl_dmc_ver1_27.bin. Disabling runtime power management.
[ 0.428650] i915 0000:00:02.0: DMC firmware homepage:
<a href="https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915">https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915</a>
The firmware is present on the filesystem, but it has not been mounted yet.
$ ls -l /lib/firmware/i915/skl_dmc_ver1_27.bin
-rw-rw-r-- 1 root root 8928 Jun 6 19:23
/lib/firmware/i915/skl_dmc_ver1_27.bin
The firmware can be added using `EXTRA_FIRMWARE`, but that makes it difficult
if the Linux kernel should be shared between different systems using different
hardware generations.
The best solution would be to not require firmware at all as in earlier
hardware generations.
As a workaround it’d be great if the driver supported to load firmware after
the initialization phase.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>