Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Zhai, Edwin" <edwin.zhai@intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/3] xinput-calibrator: Add 0.7.5 as new recipe
Date: Wed, 03 Aug 2011 15:53:16 +0800	[thread overview]
Message-ID: <4E38FE6C.3010005@intel.com> (raw)
In-Reply-To: <1311686782.2344.236.camel@rex>



Richard Purdie wrote:
>
> On Tue, 2011-07-26 at 14:53 +0200, Koen Kooi wrote:
> > This one looks suspicously like the one in meta-oe. Apart from that,
> > is it really needed in oe-core?
>
> Given that the xcalibrate extension has been removed from the xserver I
> think we're going to either need to migrate the tools like xtscal or
> adopt other tools. Certainly OE-Core should have a consistent story for
> touchscreens...
>

RP,
There is another recipe pointercal-xinput that provides script for 
calibration based on xinput_calibrator's output. So moving xinput, 
xinput_calibrator and pointercal-xinput from meta-oe to oe-core make a 
consistent story?

If no objection, I'll do this...
>
> Cheers,
>
> Richard
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>



  parent reply	other threads:[~2011-08-03  7:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-26 12:30 [PATCH 0/3] utils for touchscreen calibration edwin.zhai
2011-07-26 12:30 ` [PATCH 1/3] xinput: Add 1.5.3 as new recipes edwin.zhai
2011-07-26 12:30 ` [PATCH 2/3] xinput-calibrator: Add 0.7.5 as new recipe edwin.zhai
2011-07-26 12:53   ` Koen Kooi
2011-07-26 13:26     ` Richard Purdie
2011-07-26 13:36       ` Koen Kooi
2011-08-03  7:53       ` Zhai, Edwin [this message]
2011-08-03 15:00         ` Khem Raj
2011-08-03 15:13           ` Koen Kooi
2011-07-27  0:56     ` Zhai, Edwin
2011-07-26 12:30 ` [PATCH 3/3] evtest: Add 1.25 " edwin.zhai

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=4E38FE6C.3010005@intel.com \
    --to=edwin.zhai@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox