All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: meta-freescale@yoctoproject.org
Subject: Re: [boundary-imx] Enquiry boundary-imx_4.1.15_1.0.0_ga kernel with egalax touch support on sabrelite
Date: Thu, 12 Jan 2017 14:14:16 +0100	[thread overview]
Message-ID: <66e9b60c-d9ea-47c3-d317-7897e08d8ff8@mlbassoc.com> (raw)
In-Reply-To: <CAP9ODKprC7R4eFmPpRbb7NqP7Ef8hYRnafdxV1xgcPhgBNQttw@mail.gmail.com>

On 2017-01-12 14:09, Otavio Salvador wrote:
> Hello,
>
> On Thu, Dec 29, 2016 at 5:42 AM, Shrikant Bobade
> <bobadeshrikant@gmail.com> wrote:
>> I used boundary-eval-image-nitrogen6x-krogoth-next.sdcard.gz
>> https://boundarydevices.com/krogoth-next-yocto-release/ on imx6q-sabrelite
>> target along with 10Inch Hannstar LVDS Display connected.
>>
>> Observed the egalax touch is not working out of box. Does anyone else faced
>> similar issue?
>> Is Hannstar LVDS display supported by default?
>
> Do you mind to test with other test images?
>
> http://blink.ossystems.com.br/manufacturer/boundary
>
> Those uses new kernel and provides new boot scripts. It may provide a
> better result. Make sure to also use the latest production release for
> U-Boot provided by them.
>

Note that Ian (Boundary Devices) just sent some patches for what
seems to be this problem.  It may be easier to just check against
those.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2017-01-12 13:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-29  7:42 [boundary-imx] Enquiry boundary-imx_4.1.15_1.0.0_ga kernel with egalax touch support on sabrelite Shrikant Bobade
2017-01-12 13:09 ` Otavio Salvador
2017-01-12 13:14   ` Gary Thomas [this message]
2017-01-13  0:10     ` Ian Coolidge
2017-01-16 14:34       ` Shrikant Bobade
2017-01-16 17:33         ` Ian Coolidge

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=66e9b60c-d9ea-47c3-d317-7897e08d8ff8@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=meta-freescale@yoctoproject.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 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.