Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot Touchscreen goes to coordinates 0 0
Date: Thu, 21 Jan 2021 22:22:26 +0100	[thread overview]
Message-ID: <20210121222226.279be2e9@gmx.net> (raw)
In-Reply-To: <CAONQdNmac47XOqi2kec20PbdohXW4jYov-sM3hDvDTsKZZmXTw@mail.gmail.com>

Hello Sebasti?n,

On Tue, 19 Jan 2021 23:56:12 -0300, Sebasti?n Conti <sebaconti19@gmail.com> wrote:

> I think is a usb touchscreen that is plug and play and have speakers, but
> when I am trying to run a example from qt that you can draw, it draws a
> line from coordinates 0 0 to where my finger is.
> After installing evtest and building buildroot, the final coordinates of
> every touch are 0x 0y.
> 
> If I test evest on other linux distro it works perfectly.
> 
> Thanks
> 
> Init screen: https://i.stack.imgur.com/1NqWY.jpg
> 
> 
> Qt example: https://i.stack.imgur.com/xcnq4.jpg

Looks strange...

> 
> 
> Evtest: https://i.stack.imgur.com/Hqzce.jpg

As evtest (more or less) only shows the decoded events coming from
the kernel/driver, I would suspect some hardware/driver defect
(maybe kernel version dependent)..., did you test the exact same
touchscreen hardware on the same board with an different distro
(which kernel versions)?

As a second check your can try out as an alternative the libinput
debug events feature (see [1])...

Regards,
Peter

[1] https://wayland.freedesktop.org/libinput/doc/latest/tools.html#libinput-debug-events

  reply	other threads:[~2021-01-21 21:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20  2:56 [Buildroot] Buildroot Touchscreen goes to coordinates 0 0 Sebastián Conti
2021-01-21 21:22 ` Peter Seiderer [this message]
2021-02-09 18:57   ` Sebastián Conti
2021-02-09 19:47   ` Sebastián Conti
2021-02-13 15:44     ` Peter Seiderer

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=20210121222226.279be2e9@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@busybox.net \
    /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