From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 3/3] Fix video support for vision2 board
Date: Wed, 03 Nov 2010 14:09:32 +0100 [thread overview]
Message-ID: <4CD15F0C.8090207@denx.de> (raw)
In-Reply-To: <1288753349-31698-1-git-send-email-renato.frias@gmail.com>
On 11/03/2010 04:02 AM, Renato Frias wrote:
> From: Renato Frias <renato.frias@freescale.com>
>
> Adds arguments to the mx51_fb_init call.
>
> Signed-off-by: Renato Frias <renato.frias@freescale.com>
> ---
> Changes for v2:
> - Includes fix to vision2 (this commit) on the patch set
>
> - ret = mx51_fb_init(&nec_nl6448bc26_09c);
> + ret = mx51_fb_init(&nec_nl6448bc26_09c, 0, 18);
I think there is aa misunderstanding at this point. You introduce a new
parameter (pix_fmt), that is used in the driver only to set up the
vl_bpix field of the panel_info structure.The field vl_bpixis the number
of bits x pixel that u-boot supports, in the range 1-4 (see defines
LCD_COLOR* in lcd.h), as we can display in u-boot bitmaps up to 16
colors. The same apply for the previous patch for mx51evk.
The first question I have is if we really need this parameter. In the
driver (bpp_to_pixfmt function) we do not support really less than 16
colors, so setting always panel_info.vl_bpix to LCD_COLOR16 seems to me
correct.
And the driver itself does not use internally this parameter and instead
of it takes interface_pix_fmt to set up the IPU.
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
prev parent reply other threads:[~2010-11-03 13:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 3:02 [U-Boot] [PATCH v2 3/3] Fix video support for vision2 board Renato Frias
2010-11-03 13:09 ` Stefano Babic [this message]
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=4CD15F0C.8090207@denx.de \
--to=sbabic@denx.de \
--cc=u-boot@lists.denx.de \
/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