Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: Saul Wold <sgw@linux.intel.com>,
	Bruce Ashfield <bruce.ashfield@gmail.com>,
	 OpenEmbedded <openembedded-core@lists.openembedded.org>
Subject: hidraw support in the kernel(s)
Date: Mon, 11 Sep 2017 10:48:46 +0200	[thread overview]
Message-ID: <1505119726.9633.18.camel@intel.com> (raw)

Hello!

I am currently trying to get fwupd [1] working. For updating a Lenovo
Unifying Dongle (the USB thingie which connects to wireless mice and
keyboards), the kernel has to support hidraw, aka CONFIG_HIDRAW,
otherwise fwupd does not find the dongle.

http://www.signal11.us/oss/udev/ is an article that seems to explain
the underlying API used by fwupd. Other apps might also need it. The
recommendation is to enable it unless there are reasons not to do so:
http://cateee.net/lkddb/web-lkddb/HIDRAW.html

So is there a reason why CONFIG_HIDRAW is disabled in linux-intel and
(presumably, I haven't checked) linux-yocto for intel-corei7-64?

What would be the right way of enabling it? On by default as part of
some existing kernel feature perhaps? Or a new feature?

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.




             reply	other threads:[~2017-09-11  8:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-11  8:48 Patrick Ohly [this message]
2017-09-11 13:19 ` hidraw support in the kernel(s) Bruce Ashfield

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=1505119726.9633.18.camel@intel.com \
    --to=patrick.ohly@intel.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@linux.intel.com \
    /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