From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] Limit the kbdrate application to x86, mips and sparc.
Date: Mon, 24 Jun 2013 16:23:34 +0100 [thread overview]
Message-ID: <1372087414.9930.34.camel@ted> (raw)
In-Reply-To: <51C86361.6020703@linux.intel.com>
On Mon, 2013-06-24 at 08:18 -0700, Saul Wold wrote:
> On 06/24/2013 12:45 AM, jhuang0 wrote:
> >
> >
> > On 6/24/2013 3:23 PM, Paul Barker wrote:
> >> On 24 Jun 2013 07:28, <jackie.huang@windriver.com
> >> <mailto:jackie.huang@windriver.com>> wrote:
> >> >
> >> > From: Jackie Huang <jackie.huang@windriver.com
> >> <mailto:jackie.huang@windriver.com>>
> >> >
> >> > 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.
> >> >
> >>
> >> > ++#if !( defined(__i386__) \
> >> > ++ || defined(__x86_64__) \
> >> > ++ || defined(__mips__) \
> >> > ++ || defined(__sparc___))
> >> > ++
> >> > ++ fprintf(stderr,
> >> > ++ "ERROR: %s should only be used on MIPS, x86 and
> >> Sparc archicture boards\n", basename(argv[0]));
> >> > ++ exit(1);
> >> > ++#endif
> >>
> >> Would it be better to detect the target platform in the build system and
> >> skip building the kbdrate program for architectures it won't work on
> >> rather than building and installing a known broken program?
> >
> > Yeah, it should be better, I will check if we can do that.
> >
> Use COMPATIBLE_MACHINE
We're after to take out a single binary, not the whole recipe?
Cheers,
Richard
next prev parent reply other threads:[~2013-06-24 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 6:27 [PATCH 0/1] kbd: Limit the kbdrate application to x86, mips and sparc jackie.huang
2013-06-24 6:27 ` [PATCH 1/1] " jackie.huang
2013-06-24 7:23 ` Paul Barker
2013-06-24 7:45 ` jhuang0
2013-06-24 15:18 ` Saul Wold
2013-06-24 15:23 ` Richard Purdie [this message]
2013-06-25 1:19 ` 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=1372087414.9930.34.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.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