<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 - Feature Request: Support for Firmware Version Detection."
href="https://bugs.freedesktop.org/show_bug.cgi?id=97912">97912</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Feature Request: Support for Firmware Version Detection.
</td>
</tr>
<tr>
<th>Product</th>
<td>Wayland
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</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>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>libinput
</td>
</tr>
<tr>
<th>Assignee</th>
<td>wayland-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>oiaohm@gmail.com
</td>
</tr></table>
<p>
<div>
<pre>I know from the XDC2016 conference at this stage the Linux Kernel at minimum
does not provide framework to get the firmware versions of the devices in use.
Going forwards this is going to be a issue. Windows 10 has automatic update
that have been ruining people days. So someone running Linux fires up windows
returns to Linux now mouse/keyboard.... could now have a major glitch.
Even under Linux with UEFI there is work to allow Linux systems to be install
firmware updates for that.
Current method dealing with firmware changes is basically wack-a-mole.
For proactive dealing with firmware changes framework to get what firmware
version the devices libinput and possible other sections are interface with.
Then a framework to compare what was the pass working configuration and what is
the systems current configuration so that user can be informed if some firmware
has change and what device it is. This would allow users to take a proactive
response to a firmware change not wait until they happen to use it at random.
Now if some hardware has a workaround and the firmware version has changed and
libinput can detect it there is a possibility for something interface to offer
the user the option to turn the workaround off to see if it still required or
not.
How intelligently libinput can handle firmware change is limited by the missing
feature to in fact find out about firmware version so system can detect change.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>