From: Tom Fitzhenry <tom@tom-fitzhenry.me.uk>
To: 55805@debbugs.gnu.org
Cc: Tom Fitzhenry <tom@tom-fitzhenry.me.uk>
Subject: [bug#55805] [PATCH] gnu: linux-libre: enable hidraw by default
Date: Sun, 5 Jun 2022 14:02:22 +0200 [thread overview]
Message-ID: <20220605120222.1902-1-tom@tom-fitzhenry.me.uk> (raw)
* gnu/packages/linux.scm (%default-extra-linux-options): Enable CONFIG_HIDRAW.
hidraw is needed to create /dev/hidraw* devices, commonly used for U2F
devices, e.g. via libu2f-host.
CONFIG_HIDRAW is not enabled in the mainline arm64 defconfig, but is enabled
on:
* the mainline x86_64 defconfig
* gnu/packages/aux-files/linux-libre/*arm64.conf
HIDRAW's Kconfig documentation advises "If unsure, say Y."[0]
Tested by compiling and running linux-libre-arm64-generic, and observing that
/dev/hidraw* devices are created, and SSH-via-U2F now works.
0. Linux kernel, drivers/hid/Kconfig
Link: https://www.kernel.org/doc/Documentation/hid/hidraw.txt
Signed-off-by: Tom Fitzhenry <tom@tom-fitzhenry.me.uk>
---
gnu/packages/linux.scm | 2 ++
1 file changed, 2 insertions(+)
diff --git a/gnu/packages/linux.scm b/gnu/packages/linux.scm
index 4fc0ac16af..12e0db23c4 100644
--- a/gnu/packages/linux.scm
+++ b/gnu/packages/linux.scm
@@ -687,6 +687,8 @@ (define %default-extra-linux-options
("CONFIG_MEMCG_KMEM" . #t)
("CONFIG_CPUSETS" . #t)
("CONFIG_PROC_PID_CPUSET" . #t)
+ ;; Enable hidraw by default
+ ("CONFIG_HIDRAW" . #t)
;; Allow disk encryption by default
("CONFIG_DM_CRYPT" . m)
;; Modules required for initrd:
base-commit: 8334e7c36ba7266fdbcf783d80c02a072cf1347b
--
2.36.1
next reply other threads:[~2022-06-05 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-05 12:02 Tom Fitzhenry [this message]
2022-06-05 12:23 ` [bug#55805] [PATCH] gnu: linux-libre: enable hidraw by default Pavel Shlyak
2022-06-05 13:15 ` Tobias Geerinckx-Rice via Guix-patches via
2022-06-05 13:46 ` Tom Fitzhenry
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=20220605120222.1902-1-tom@tom-fitzhenry.me.uk \
--to=tom@tom-fitzhenry.me.uk \
--cc=55805@debbugs.gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.