All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Mayritsch <bit.coyote@gmail.com>
To: Rudolf J Streif <rudolf.streif@ibeeto.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: [meta-raspberrypi] RPi 7" Touch Display
Date: Fri, 17 May 2019 22:14:05 +0200	[thread overview]
Message-ID: <CAD04zYoGXx3+ipjFgN4f6he3HPfaL4MzG3Ub2v4Se6ri=KE-pA@mail.gmail.com> (raw)
In-Reply-To: <09f13d52-4fc1-6720-bceb-683f0b336b6b@ibeeto.com>

[-- Attachment #1: Type: text/plain, Size: 1686 bytes --]

I don't know if it's helpful, but I'm struggling with a similar issue on my
RPi 3 B+, where the official touchscreen, as well as, the HDMI don't output
any graphics, although detected correctly. (See:
https://lists.yoctoproject.org/pipermail/yocto/2019-May/045277.html)
After experimenting with sumo, thud and the latest master recipes, I
remembered a conversation on Andrei's GitHub project (
https://github.com/agherzan/meta-raspberrypi/issues/228), which isn't
exactly related to my issue, but I gave it a try to switch the machine from
"raspberrypi3-64" to "raspberrypi3" in order to get a 32 bit version of the
same build (of master) for core-image-x11.
However, ... this image works for the DSI port, as well as, for the HDMI.

This isn't a real solution, but at least a point to start investigating the
problem and comparing the two builds. Will try to find some time, during
the coming week, to do so, ... although I'm not experienced with the RPis -
maybe I can find something.

Regards,
Bernhard



Am Do., 16. Mai 2019 um 19:34 Uhr schrieb Rudolf J Streif <
rudolf.streif@ibeeto.com>:

> No, unfortunately not. HDMI works just fine but no video on the touch
> display.
>
> On 5/16/19 9:46 AM, Andrei Gherzan wrote:
> > Hi,
> >
> > On 16/05/2019 17.24, Rudolf J Streif wrote:
> >> Thank you, Paul. I did read Andrei's excellent documentation and
> >> enabled I2C and SPI etc.
> > And it didn't work?
> >
> --
> -----
> Rudolf J Streif
> CEO/CTO ibeeto
> +1.855.442.3396 x700
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

[-- Attachment #2: Type: text/html, Size: 3883 bytes --]

  reply	other threads:[~2019-05-17 20:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16 15:31 [meta-raspberrypi] RPi 7" Touch Display Rudolf J Streif
2019-05-16 15:39 ` Paul Barker
2019-05-16 16:24   ` Rudolf J Streif
2019-05-16 16:46     ` Andrei Gherzan
2019-05-16 17:33       ` Rudolf J Streif
2019-05-17 20:14         ` Bernhard Mayritsch [this message]
2019-05-16 16:01 ` Andrei Gherzan
2019-05-16 16:22   ` Rudolf J Streif
2019-05-19  5:13   ` Khem Raj
2019-05-19  6:02     ` Rudolf Streif
2019-05-19 16:11       ` Khem Raj
2019-05-19 20:26         ` Rudolf J Streif
2019-05-21  1:21         ` Rudolf J Streif

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='CAD04zYoGXx3+ipjFgN4f6he3HPfaL4MzG3Ub2v4Se6ri=KE-pA@mail.gmail.com' \
    --to=bit.coyote@gmail.com \
    --cc=rudolf.streif@ibeeto.com \
    --cc=yocto@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.