linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Igor Luri <iluri@fagorautomation.es>
To: linuxppc-embedded@ozlabs.org
Subject: mpc5xxx keyboard BUG found
Date: Fri, 17 Mar 2006 12:38:48 +0100	[thread overview]
Message-ID: <441A9FC8.3020205@fagorautomation.es> (raw)

We have an MPC5200LiteB board with a Microsoft USB keyboard atached and 
we have realized that some keys don't work properly, like up, down, lef 
and right arrows, PageUp, PageDown etc.

We have found that when those keys are pressed, first it sends a special 
scancode 0xe0 and then pressed key scancode.

Modifiying mpc5xxx_translate function to ignore the first scancode
 

                 // special prefix scancodes..
                  if (scancode == 0xe0 || scancode == 0xe1) {
                        return 0;
                  } 

our keyboard works well. Other cpus ignorates this special scancode or  
it evaluates.

Now, mpc5xxx_translate looks like this:

int mpc5xxx_translate(unsigned char scancode, unsigned char *keycode,
               char raw_mode)
{
    
  // special prefix scancodes..
  if (scancode == 0xe0 || scancode == 0xe1) {
        return 0;
  }  

  //0xFF is sent by a few keyboards, ignore it. 0x00 is error
  if (scancode == 0x00 || scancode == 0xff) {
    return 0;
  }
  *keycode = scancode;
  return 1;
}

             reply	other threads:[~2006-03-17 11:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-17 11:38 Igor Luri [this message]
2006-03-17 18:50 ` mpc5xxx keyboard BUG found Jarno Manninen
  -- strict thread matches above, loose matches on Subject: below --
2006-03-20  8:18 IGOR LURI
2006-03-20  8:44 ` Jarno Manninen

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=441A9FC8.3020205@fagorautomation.es \
    --to=iluri@fagorautomation.es \
    --cc=linuxppc-embedded@ozlabs.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).