linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kristoffer Ericson <kristoffer.ericson@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: H Hartley Sweeten <hartleys@visionengravers.com>,
	linux-input@vger.kernel.org
Subject: Re: Rawmode keyboard for your....
Date: Mon, 20 Apr 2009 13:04:30 +0200	[thread overview]
Message-ID: <20090420130430.cf95a039.kristoffer.ericson@gmail.com> (raw)
In-Reply-To: <200904200004.49651.dmitry.torokhov@gmail.com>

On Mon, 20 Apr 2009 00:04:49 -0700
Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:

> On Thursday 26 March 2009 11:30:43 H Hartley Sweeten wrote:
> > On Thursday, March 26, 2009 10:59 AM, Kristoffer Ericson wrote:
> > > Greetings,
> >
> > Hello
> >
> > > What exactly does this build warning imply?
> > > We have a fully working keyboard driver for the Jornada 700-series
> > > and would really like to get rid of this.
> > >
> > >
> > >  CC      drivers/char/keyboard.o
> > > drivers/char/keyboard.c:1126:2: warning: #warning "Cannot generate
> >
> > rawmode keyboard for your architecture yet."
> >
> > > drivers/char/keyboard.c:1126:2: warning: #warning "Cannot generate
> >
> > rawmode keyboard for your architecture yet."
> >
> > It means just what it says, if you put the keyboard into VC_RAW mode you
> > will not get the expected key codes.
> >
> > But... Hmm... Jornada 700-series is arm/mach-sa1100 (CONFIG_ARM)...
> >
> > Looks like if you enable CONFIG_KEYBOARD_ATKBD the build warning message
> > will go away.
> >
> 
> I think we should just remove the warning. It does not make much sense
> anymore. I intend to apply the patch below.

Sounds like a good idea. Thanks!

> 
> -- 
> Dmitry
> 
> Input: keyboard - remove warning about raw mode not supported
> 
> This warning made sense when legacy keyboard driver was preferred
> driver in X, but now that evdev driver is the default we can remove
> the warning.
> 
> Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
> ---
> 
>  drivers/char/keyboard.c |    2 --
>  1 files changed, 0 insertions(+), 2 deletions(-)
> 
> 
> diff --git a/drivers/char/keyboard.c b/drivers/char/keyboard.c
> index de26a97..737be95 100644
> --- a/drivers/char/keyboard.c
> +++ b/drivers/char/keyboard.c
> @@ -1123,8 +1123,6 @@ static int emulate_raw(struct vc_data *vc, unsigned int 
> keycode,
>  
>  #define HW_RAW(dev)	0
>  
> -#warning "Cannot generate rawmode keyboard for your architecture yet."
> -
>  static int emulate_raw(struct vc_data *vc, unsigned int keycode, unsigned 
> char up_flag)
>  {
>  	if (keycode > 127)
> 
> 
> 


-- 
Kristoffer Ericson <kristoffer.ericson@gmail.com>

      reply	other threads:[~2009-04-20 11:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26 17:59 Rawmode keyboard for your Kristoffer Ericson
2009-03-26 18:30 ` H Hartley Sweeten
2009-04-20  7:04   ` Dmitry Torokhov
2009-04-20 11:04     ` Kristoffer Ericson [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=20090420130430.cf95a039.kristoffer.ericson@gmail.com \
    --to=kristoffer.ericson@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hartleys@visionengravers.com \
    --cc=linux-input@vger.kernel.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 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).