From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [Bug Report] DU: Error messages at boot log and can't show image on RGB Display.
Date: Wed, 13 May 2015 21:56:20 +0000 [thread overview]
Message-ID: <1784861.2EDxqCpMCH@avalon> (raw)
In-Reply-To: <5552F298.2020201@jinso.co.jp>
Hello,
On Wednesday 13 May 2015 15:43:36 Cao Minh Hiep wrote:
> Hi All.
>
> We are testing Linux upstream version-4.1-rc2 on Lager.
> We found a Error message of DU(Display Unit) at boot logs:
> The Warning messages is showed as below:
> "rcar-du feb00000.display: encoder initialization failed, skipping"
> Then we tried to show a .bmp image on RGB Display via RGB port. But it
> didn't work.
>
> Testing method:
> 1. Connect RGB Display to RGB port on Lager.
> 2. Show a BMP image on Display by this command:
> # bmap /dev/fb0 ./image.bmp
>
> We'd like to report this problem first.
> There are no error message at version v4.0 stable.
> And showed the image on RGB Display normally at version v4.0 stable.
> We are looking for the error patch that added between v4.0 and v4.1-rc2.
I've tried v4.1-rc2 and haven't experienced that problem. It might be related
to kernel configuration, could you please share your .config file ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2015-05-13 21:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 6:43 [Bug Report] DU: Error messages at boot log and can't show image on RGB Display Cao Minh Hiep
2015-05-13 21:56 ` Laurent Pinchart [this message]
2015-05-14 3:18 ` Cao Minh Hiep
2015-05-14 9:27 ` Cao Minh Hiep
2015-05-26 15:02 ` Laurent Pinchart
2015-05-29 1:11 ` Cao Minh Hiep
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=1784861.2EDxqCpMCH@avalon \
--to=laurent.pinchart@ideasonboard.com \
--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.