From: Simon Busch <morphis@gravedo.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] ecore: remove fix-ecore-fb-initialization.patch
Date: Mon, 16 Aug 2010 19:54:00 +0200 [thread overview]
Message-ID: <4C697B38.5070408@gravedo.de> (raw)
In-Reply-To: <1281813967.2127.1.camel@saphir>
Am 14.08.2010 21:26, schrieb Michael 'Mickey' Lauer:
> Am Freitag, den 13.08.2010, 23:52 +0200 schrieb Stefan Schmidt:
>> Hello.
>>
>> On Tue, 2010-08-10 at 21:29, Simon Busch wrote:
>>> Removing the fix-ecore-fb-initialization patch as it let ecore open the supplied
>>> touchscreen device twice which results in an error on platforms where the touchscreen
>>> device node can be opened only once. Furthermore I doubt that it is necessary to open the
>>> touchscreen device node more than one time.
>>
>> Sounds good, but I want to hear Mickey on this before pushing it as it is his
>> patch.
>
> NACK. Last time I checked, this patch was still necessary to fix
> touchscreen access using Ecore on pure framebuffer. There may be
> better approaches to it, but removing it now will break ecore on fb.
>
> Regards,
I think the best solution to work around this is using tsmd: our
touchscreen daemon which opens the touchscreen device node and forwards
it to a uninput device which can be opened more than on time.
Will write a recipe for it and send it in for integration.
regards,
morphis
prev parent reply other threads:[~2010-08-16 17:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 19:29 [PATCH] ecore: remove fix-ecore-fb-initialization.patch Simon Busch
2010-08-13 21:52 ` Stefan Schmidt
2010-08-14 0:33 ` Martin Jansa
2010-08-14 19:26 ` Michael 'Mickey' Lauer
2010-08-15 11:47 ` Simon Busch
2010-08-16 17:54 ` Simon Busch [this message]
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=4C697B38.5070408@gravedo.de \
--to=morphis@gravedo.de \
--cc=openembedded-devel@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