From: Cao Minh Hiep <cm-hiep@jinso.co.jp>
To: linux-sh@vger.kernel.org
Subject: Rcar Gen2: DU: Bootlogs Error and show image error
Date: Fri, 20 Nov 2015 07:39:28 +0000 [thread overview]
Message-ID: <564ECE30.9000206@jinso.co.jp> (raw)
Hi Laurent-san
Thanks for your kindness support!
I don't mean to bother you!
But as you know, we have reported to you before, have some problems
related to DU driver.
We couldn't show a image on the display. We found the messages as showed
below:
-----
Boot logs on Rcar-H2:
rcar-du feb00000.display: failed to initialize encoder
/i2c@e6520000/hdmi@39 (-38), skipping
rcar-du feb00000.display: fb0: frame buffer device
-----
Boot logs on Rcar-M2:
rcar-du feb00000.display: failed to initialize encoder
/i2c@e6530000/hdmi@39 (-g
rcar-du feb00000.display: error: no encoder could be initialized
rcar-du feb00000.display: failed to initialize DRM/KMS (-22)
rcar-du: probe of feb00000.display failed with error -22
-----
This is tested on linux stable v4.3.
Please have a look when you have time.
Best Regards,
Jinso/Cao Minh Hiep.
next reply other threads:[~2015-11-20 7:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 7:39 Cao Minh Hiep [this message]
2015-11-25 1:08 ` Rcar Gen2: DU: Bootlogs Error and show image error Laurent Pinchart
2015-11-26 2:48 ` Cao Minh Hiep
2015-11-27 0:39 ` Laurent Pinchart
2015-11-27 6:13 ` Cao Minh Hiep
2015-12-02 7:23 ` Cao Minh Hiep
2015-12-13 19:45 ` Laurent Pinchart
2016-06-29 23:58 ` Laurent Pinchart
-- strict thread matches above, loose matches on Subject: below --
2015-11-12 14:12 [PATCH] pinctrl: sh-pfc: r8a7795: Rename SEL_SCIF to SEL_SATA Geert Uytterhoeven
[not found] ` <56725823.5080003@jinso.co.jp>
[not found] ` <5771D098.5000706@jinso.co.jp>
2016-08-03 22:19 ` Rcar Gen2: DU: Bootlogs Error and show image error Laurent Pinchart
2016-08-04 6:54 ` Hiep Cao Minh
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=564ECE30.9000206@jinso.co.jp \
--to=cm-hiep@jinso.co.jp \
--cc=linux-sh@vger.kernel.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.