From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107168] Allow to load firmware during run-time (after initialization)
Date: Mon, 09 Jul 2018 15:49:26 +0000 [thread overview]
Message-ID: <bug-107168-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1175 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107168
Bug ID: 107168
Summary: Allow to load firmware during run-time (after
initialization)
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: pmenzel+bugs.freedesktop@molgen.mpg.de
Building the radeon driver into the Linux kernel, that means not as a module,
*without* an initrd image, the firmware is not loaded.
The firmware is present on the filesystem in `/lib/firmware/`, but it has not
been mounted yet.
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.)
It’d be great if the driver supported to load firmware after the initialization
phase.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2463 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-07-09 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 15:49 bugzilla-daemon [this message]
2018-07-09 15:53 ` [Bug 107168] Allow to load firmware during run-time (after initialization) bugzilla-daemon
2018-07-09 16:02 ` bugzilla-daemon
2018-07-09 16:26 ` bugzilla-daemon
2018-07-09 16:33 ` bugzilla-daemon
2018-07-09 16:42 ` bugzilla-daemon
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=bug-107168-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).