From: Andrey Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: legendary_bibo@hotmail.com
Subject: Re: Where's the code for inputs in Grub?
Date: Mon, 2 Jun 2014 17:50:01 +0400 [thread overview]
Message-ID: <20140602175001.355ac19c@opensuse.site> (raw)
In-Reply-To: <BLU180-W24027F19CF7C09EB938320FD240@phx.gbl>
В Thu, 29 May 2014 09:24:13 -0600
Gerard Butler <legendary_bibo@hotmail.com> пишет:
> I'm looking for the .c file that tells grub about how to handle keyboard inputs? I want to see if I can use that as a base to write a module to take input from game controllers.
Look under grub-core/term. Your driver would need to implement function
for getting keys and register itself with grub_term_register_input() so
it becomes available for grub core.
prev parent reply other threads:[~2014-06-02 13:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 15:24 Where's the code for inputs in Grub? Gerard Butler
2014-06-02 13:50 ` Andrey Borzenkov [this message]
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=20140602175001.355ac19c@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
--cc=legendary_bibo@hotmail.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;
as well as URLs for NNTP newsgroup(s).