<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 11, 2017 at 4:48 AM, Patrick Ohly <span dir="ltr"><<a href="mailto:patrick.ohly@intel.com" target="_blank">patrick.ohly@intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello!<br>
<br>
I am currently trying to get fwupd [1] working. For updating a Lenovo<br>
Unifying Dongle (the USB thingie which connects to wireless mice and<br>
keyboards), the kernel has to support hidraw, aka CONFIG_HIDRAW,<br>
otherwise fwupd does not find the dongle.<br>
<br>
<a href="http://www.signal11.us/oss/udev/" rel="noreferrer" target="_blank">http://www.signal11.us/oss/<wbr>udev/</a> is an article that seems to explain<br>
the underlying API used by fwupd. Other apps might also need it. The<br>
recommendation is to enable it unless there are reasons not to do so:<br>
<a href="http://cateee.net/lkddb/web-lkddb/HIDRAW.html" rel="noreferrer" target="_blank">http://cateee.net/lkddb/web-<wbr>lkddb/HIDRAW.html</a><br>
<br>
So is there a reason why CONFIG_HIDRAW is disabled in linux-intel and<br>
(presumably, I haven't checked) linux-yocto for intel-corei7-64?<br></blockquote><div><br></div><div>The only reason it wouldn't be enabled is simply that we haven't had a </div><div>use case for it (up until now), and (for the most part) anything that isn't</div><div>strictly needed (or has a known peripheral) is disabled to keep the default</div><div>kernel's smaller.</div><div><br></div><div>For this option, it doesn't add much size to the kernel, has broad arch</div><div>support and could be generally useful .. so there really isn't much of an</div><div>issue enabling it in the core configs.</div><div><br></div><div>A lot of the HID enablement is currently in BSP fragments, but that tends</div><div>to limit their ability to be reused.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
What would be the right way of enabling it? On by default as part of<br>
some existing kernel feature perhaps? Or a new feature?<br></blockquote><div><br></div><div>There are several features that already deal with HID devices, so it could</div><div>be added there (i.e. features/iio/iio.cfg) done there, or create a similar feature</div><div>if there's a reason do not enable what is in the existing fragments when this</div><div>one is used.</div><div><br></div><div>Once the option is in a fragment, it is a matter of just ensuring that either a</div><div>ktype (i.e. standard) includes it, if we want it everywhere .. or the relevant</div><div>BSPs include it if you want to limit it.</div><div><br></div><div>And finally, KERNEL_FEATURES are available if you want it to be optionally</div><div>enabled via a kernel recipe.</div><div><br></div><div>Cheers,</div><div><br></div><div>Bruce</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Best Regards, Patrick Ohly<br>
<br>
The content of this message is my personal opinion only and although<br>
I am an employee of Intel, the statements I make here in no way<br>
represent Intel's position on the issue, nor am I authorized to speak<br>
on behalf of Intel on this matter.<br>
<br>
<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"</div>
</div></div>