From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Add video support for mx51evk
Date: Tue, 2 Nov 2010 10:18:10 +0100 [thread overview]
Message-ID: <20101102101810.020df6e6@wker> (raw)
In-Reply-To: <4CCFB244.2000909@denx.de>
Hi,
On Tue, 02 Nov 2010 07:40:04 +0100
Stefano Babic <sbabic@denx.de> wrote:
...
> > There is also a second issue where I would like to know your thoughts. Very
> > early on system initialization, when LCD is enabled, there is a call to
> > "lcd_setmem" from board.c. By that time, the video variables,
> > "panel_info", are
> > not set yet. Thus U-Boot doesn't reserve the appropriate amount of
> > memory for
> > the display. I was going to set "panel_info" variable on mx51evk.c, but
> > I would like to know how you solved it for vision2 first.
>
> Thanks for pointing out, I have already seen the point, but at the end I
> forget to fix it ;-). Probably because there is no side-effects on this
> board, but this does not mean that the issue should not fixed for
> vision2, too.
>
> The problem arises from the fact that the setup of the display
> parameters was static and everything was solved at compile time. With
> the framebuffer for the MX51, I needed the possibility to change
> dinamically the parameters, because the board can have different LCD
> displays.
>
> Consider this, I do not think the actual computation in lcd_setmem() is
> correct. We need to compute the maximum amount of memory to be reserved
> to the framebuffer, not the value requested by the current display
> interface. We could add a CONFIG_SYS_VIDEO_SIZE that contains the
> maximum amount of memory needed, because the value is strictly
> board-dependent, and change lcd_setmem to use it. Anatolij, what do you
> think about this ?
We should reserve the amount of memory we actually need for the
used display configuration, I think. Reserving the maximum amount
would be needed if we have to support switching the display
resolution at runtime, but I don't think that this is needed in
your case. Therefore I prefer the solution that reserves the
actually needed amount of memory.
Best regards,
Anatolij
next prev parent reply other threads:[~2010-11-02 9:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 5:29 [U-Boot] Add video support for mx51evk Frias Renato-B13784
2010-11-02 6:40 ` Stefano Babic
2010-11-02 8:35 ` Wolfgang Denk
2010-11-02 8:59 ` Stefano Babic
2010-11-02 9:42 ` Wolfgang Denk
2010-11-02 9:49 ` Stefano Babic
2010-11-02 13:34 ` Wolfgang Denk
2010-11-02 16:01 ` Stefano Babic
2010-11-02 19:41 ` Wolfgang Denk
2010-11-02 9:18 ` Anatolij Gustschin [this message]
2010-11-03 0:04 ` Renato Frias
-- strict thread matches above, loose matches on Subject: below --
2010-11-02 5:15 Frias Renato-B13784
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=20101102101810.020df6e6@wker \
--to=agust@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