From: "Eric Bénard" <eric@eukrea.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: tslib in fsl-image-gui
Date: Fri, 12 Jul 2013 16:53:23 +0200 [thread overview]
Message-ID: <20130712165323.090fab24@e6520eb> (raw)
In-Reply-To: <CAP9ODKohz2GrP0KUNUeeAdcYtqSwaQVmJQFH+NW-zx2HB-KHsg@mail.gmail.com>
Le Fri, 12 Jul 2013 10:33:35 -0300,
Otavio Salvador <otavio@ossystems.com.br> a écrit :
> On Fri, Jul 12, 2013 at 6:10 AM, Petr Kolesnikov <petr@kolesnikov.eu> wrote:
> > I went into same issue a few days ago. The tslib is compiled against yocto
> > kernel headers 3.8 while we are using quiet old imx kernel 2.6.35. The
> > EV_VERSION has been incremented in kernel 2.6.37.
> >
> > So there are two approaches. Compile tslib against imx kernel headers, that
> > is most likely the right way. The second (dirty) way is to patch tslib to
> > accept version 0x010000, that is working fine too.
>
> An easier one is to make a patch to 2.6.35 which fixes the EV_VERSION there.
>
no 2.6.35 has the EV_VERSION value corresponding the the ev API of
this kernel version so that's not the right thing to do.
tslib has this commit which triggers the problem by allowing old kernels
to run tslib compiled with newer headers but not the reverse :
https://github.com/kergoth/tslib/commit/412d99d8b92c12545f939972146a38c5074f3dcb
so for i.MX53 tslib may need a patch to relax the check.
Eric
next prev parent reply other threads:[~2013-07-12 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 1:58 tslib in fsl-image-gui Alexey Mednyy
2013-06-28 12:26 ` Trevor Woerner
2013-07-12 9:10 ` Petr Kolesnikov
2013-07-12 13:33 ` Otavio Salvador
2013-07-12 14:53 ` Eric Bénard [this message]
2013-07-12 15:08 ` Otavio Salvador
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=20130712165323.090fab24@e6520eb \
--to=eric@eukrea.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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.