From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: DongCV <cv-dong@jinso.co.jp>
Cc: "Wolfram Sang" <wsa@sang-engineering.com>,
duclm <lm-duc@jinso.co.jp>,
"Ryusuke Sakato" <ryusuke.sakato.bx@renesas.com>,
"Kuninori Morimoto" <kuninori.morimoto.gx@renesas.com>,
"Magnus Damm" <magnus.damm@gmail.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
稲吉 <h-inayoshi@jinso.co.jp>,
"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>,
Dung:人ソ <nv-dung@jinso.co.jp>,
"Cao Minh Hiep" <cm-hiep@jinso.co.jp>,
"Laurent Pinchart" <laurent.pinchart+renesas@ideasonboard.com>,
"Simon Horman" <horms+renesas@verge.net.au>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
na-hoan@jinso.co.jp
Subject: Re: The failure summary report of GEN2 for linux stable v4.10-rc2
Date: Thu, 19 Jan 2017 00:26:36 +0200 [thread overview]
Message-ID: <1988000.69YelQnMiB@avalon> (raw)
In-Reply-To: <d7f4a948-37a2-e912-6e25-5690ad8ecef9@jinso.co.jp>
Dear Dong,
On Tuesday 17 Jan 2017 15:05:32 DongCV wrote:
> Dear Mr Laurent
>
> Thank you for your quick reply.
> I've retested the HDMI output on Lager(H2) with v4.10-rc2.
>
> The results:
>
> Enabled CMA:
>
> The HDMI cable unplugged: Could not recognize the display.
> The HDMI cable plugged: Recognized the display-> test fail.
>
> The VGA cable unplugged: Recognized the display-> test fail.
> The VGA cable plugged: Recognized the display-> test fail.
>
>
> Disabled CMA: The same to the case of enabled CMA.
>
> I attach the test procedures and test tool, test result.
> Please have a look at it.
I'm afraid there was a bit of misunderstanding. I was referring to the "Lager:
Bad image quality when shown on HDMI display" issue, not the "DISPLAY-UNIT:
Does not support 640x480 resolution" and "DISPLAY-UNIT: Does not support 16-
bit for color numbers" issues. I should have been more precise, I'm very sorry
about that.
Could you please share your detailed test procedure, kernel configuration and
test binaries for the "Lager: Bad image quality when shown on HDMI display"
issue ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2017-01-18 22:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 9:29 The failure summary report of GEN2 for linux stable v4.10-rc2 "カオ・ヴァン・ドン"
2017-01-16 15:34 ` Laurent Pinchart
[not found] ` <d7f4a948-37a2-e912-6e25-5690ad8ecef9@jinso.co.jp>
2017-01-18 6:53 ` DongCV
2017-01-18 22:47 ` Laurent Pinchart
2017-01-18 22:26 ` Laurent Pinchart [this message]
[not found] ` <8a056d37-3de9-30ac-74bc-e1393d1b193a@jinso.co.jp>
2017-01-19 23:49 ` Laurent Pinchart
2017-01-20 3:11 ` DongCV
2017-01-20 12:36 ` Laurent Pinchart
2017-01-23 7:58 ` Hiep Cao Minh
2017-02-14 21:53 ` Laurent Pinchart
2017-02-17 10:49 ` Hiep Cao Minh
[not found] ` <2653919.pRB2KAMlVt@avalon>
2017-02-22 12:23 ` Hiep Cao Minh
2017-02-22 17:41 ` Laurent Pinchart
2017-02-24 0:52 ` Hiep Cao Minh
2017-01-17 2:40 ` The failure summary report of GEN3 for linux upstream v4.10-rc2 Hoan
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=1988000.69YelQnMiB@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=cm-hiep@jinso.co.jp \
--cc=cv-dong@jinso.co.jp \
--cc=geert+renesas@glider.be \
--cc=h-inayoshi@jinso.co.jp \
--cc=horms+renesas@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lm-duc@jinso.co.jp \
--cc=magnus.damm@gmail.com \
--cc=na-hoan@jinso.co.jp \
--cc=nv-dung@jinso.co.jp \
--cc=ryusuke.sakato.bx@renesas.com \
--cc=wsa@sang-engineering.com \
--cc=yoshihiro.shimoda.uh@renesas.com \
/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