All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: jackie.huang@windriver.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1 v2] kbd: Limit the kbdrate application to x86, mips and sparc
Date: Fri, 12 Jul 2013 09:34:36 +0100	[thread overview]
Message-ID: <1373618076.21102.48.camel@pb-ThinkPad-R50e> (raw)
In-Reply-To: <3393c80c31d82ac23afcddd39b1b24a9b5c1e696.1373607104.git.jackie.huang@windriver.com>

On Fri, 2013-07-12 at 13:42 +0800, jackie.huang@windriver.com wrote:
> The code relies on hardware specific memory locations to access
> and modify the keyboard repeat rate.  It also requires read/write
> access to /dev/port which doesn't exist on every architecture's
> root fs. The defect was raised for Qemu PowerPC but it also fails on
> ARM.  The keyboard emulation in qemuppc is for an ADB (Apple Desktop
> Bus) device and not compatible with an Intel driver.  There's also no
> indication in the documentation that the code should work on anything
> other than Intel architecture but it also works on MIPS.

This reasoning seems slightly spurious.  There do exist ARM and PPC
machines where kbdrate works, it's just that the hardware emulated by
qemuarm and qemuppc doesn't happen to fall into that category.  Equally,
there are certainly mips machines (and might conceivably be some
x86/sparc ones) where it doesn't work.  So I don't think you can make
any sensible determination about the supportedness or not of kbdrate
based on TARGET_ARCH alone.  

Of course, the right answer really is for rate setting to go through the
kernel driver (which knows what sort of hardware it is using) rather
than for kbdrate to go poking at random I/O ports.

p.




  reply	other threads:[~2013-07-12  8:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-12  5:42 [PATCH 0/1 v2] kbd: Limit the kbdrate application to x86, mips and sparc jackie.huang
2013-07-12  5:42 ` [PATCH 1/1 " jackie.huang
2013-07-12  8:34   ` Phil Blundell [this message]
2013-07-15  3:02     ` jhuang0

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=1373618076.21102.48.camel@pb-ThinkPad-R50e \
    --to=pb@pbcl.net \
    --cc=jackie.huang@windriver.com \
    --cc=openembedded-core@lists.openembedded.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.