From: Carles Pina i Estany <carles@pina.cat>
To: grub-devel@gnu.org
Subject: Re: [PATCH] Correcting GRUB_CONSOLE_KEY_NPAGE/PPAGE
Date: Sun, 24 Aug 2008 16:29:44 +0200 [thread overview]
Message-ID: <20080824142944.GA9470@pina.cat> (raw)
In-Reply-To: <20080824130216.GA5808@pina.cat>
Hi,
I was just thinking now...
On Aug/24/2008, Carles Pina i Estany wrote:
> * include/grub/powerpc/ieee1275/console.h (GRUB_TERM_NPAGE):
> Changed to 0x5100.
> (GRUB_TERM_PPAGE): Changed to 0x4900.
>
> * include/grub/sparc64/ieee1275/console.h: Likewise.
>
> * include/grub/i386/pc/console.h: Likewise.
>
> * include/grub/efi/console.h: Likewise.
I was just thinking... is there any reason that we have the same macros
in 4 different files?
Why not having just a grub/console_scancodes.h:
#ifndef GRUB_CONSOLE_SCAN_CODES
#define GRUB_CONSOLE_KEY_LEFT 0x4B00
#define GRUB_CONSOLE_KEY_RIGHT 0x4D00
#define GRUB_CONSOLE_KEY_UP 0x4800
#define GRUB_CONSOLE_KEY_DOWN 0x5000
#define GRUB_CONSOLE_KEY_IC 0x5200
#define GRUB_CONSOLE_KEY_DC 0x5300
#define GRUB_CONSOLE_KEY_BACKSPACE 0x0008
#define GRUB_CONSOLE_KEY_HOME 0x4700
#define GRUB_CONSOLE_KEY_END 0x4F00
#define GRUB_CONSOLE_KEY_NPAGE 0x5100
#define GRUB_CONSOLE_KEY_PPAGE 0x4900
#endif
and include this file from the other 4 files?
Thanks,
--
Carles Pina i Estany GPG id: 0x17756391
http://pinux.info
next prev parent reply other threads:[~2008-08-24 14:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-24 13:02 [PATCH] Correcting GRUB_CONSOLE_KEY_NPAGE/PPAGE Carles Pina i Estany
2008-08-24 14:29 ` Carles Pina i Estany [this message]
2008-08-24 16:09 ` Vesa Jääskeläinen
2008-08-24 18:11 ` Carles Pina i Estany
2008-09-24 10:23 ` Robert Millan
2008-08-30 11:50 ` Robert Millan
2008-09-05 17:00 ` Carles Pina i Estany
2008-08-24 18:34 ` [PATCH] Correcting GRUB_CONSOLE_KEY_NPAGE/PPAGE (summary) Carles Pina i Estany
2008-09-24 10:25 ` Robert Millan
2008-09-24 10:22 ` [PATCH] Correcting GRUB_CONSOLE_KEY_NPAGE/PPAGE Robert Millan
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=20080824142944.GA9470@pina.cat \
--to=carles@pina.cat \
--cc=grub-devel@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.
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.