From: Ricardo Wurmus <rekado@elephly.net>
To: Stefan Huchler <stefan.huchler@mail.de>
Cc: help-guix@gnu.org
Subject: Re: how to add hwdb of keyboard
Date: Tue, 15 Sep 2020 01:46:36 +0200 [thread overview]
Message-ID: <87y2lbx6oz.fsf@elephly.net> (raw)
In-Reply-To: <87k0wwniiw.fsf@mail.de>
Hi Stefan,
it took me a while to reply to your original message, because I didn’t
know what hwdb was supposed to mean. The code snippet in this mail made
it clearer to me.
> I forked now the eudev definition to add my hwdb data:
>
> (add-before 'build-hwdb 'add-my-hwdb-file
> (lambda* (#:key outputs #:allow-other-keys)
> (let ((out (assoc-ref outputs "out")))
> (call-with-output-file
> (string-append out "/etc/udev/hwdb.d/90-X220-keyboard.hwdb")
> (lambda (port)
> (display
> "keyboard:dmi:bvn*:bvr*:bd*:svnLENOVO*:pn*:pvrThinkPadX220*\n" port)
> (display "KEYBOARD_KEY_7b=compose\n" port)
> (display "KEYBOARD_KEY_39=enter\n" port)
> (display "KEYBOARD_KEY_79=space\n" port)
> (display "KEYBOARD_KEY_70=tab\n" port)
> (display "KEYBOARD_KEY_0f=backspace\n" port)
> (display "KEYBOARD_KEY_3a=home\n" port)
> (display "KEYBOARD_KEY_1c=end\n" port)
> (display "KEYBOARD_KEY_0e=backspace\n" port)
> (display "KEYBOARD_KEY_7d=backspace\n"
> port))))))
>
> Is there a way to make guix system priotise my modified eudev over the
> upstream one?
No, you would need to rebuild with your eudev as a replacement. But
let’s take a step back: is it possible to provide this hwdb with the
udev-service? If not, perhaps we should augment the udev-service to not
only accept udev rules, but also custom hwdb files.
--
Ricardo
next prev parent reply other threads:[~2020-09-14 23:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 16:47 how to add hwdb of keyboard Stefan Huchler
2020-09-11 23:51 ` Stefan Huchler
2020-09-14 21:41 ` Stefan Huchler
2020-09-14 23:46 ` Ricardo Wurmus [this message]
2020-09-15 1:44 ` Stefan Huchler
2020-09-19 21:34 ` Stefan Huchler
2020-09-20 6:51 ` Ricardo Wurmus
2020-09-20 10:28 ` Stefan Huchler
2020-09-20 6:52 ` Ricardo Wurmus
2020-09-20 10:33 ` Stefan Huchler
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2lbx6oz.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=stefan.huchler@mail.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).