From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Displaying characters on the display in u-boot
Date: Wed, 27 Mar 2013 16:00:54 +0100 [thread overview]
Message-ID: <20130327160054.6f97a717@crub> (raw)
In-Reply-To: <9827C66E1D129C4183B8AD771A4A57709A02936174@EXGMBX01.sasken.com>
Hi,
please keep the U-Boot list address on Cc, other users may
find the discussion helpful.
On Wed, 27 Mar 2013 19:40:33 +0530
Bhargav A K <bhargav.ak@sasken.com> wrote:
...
> Now I will have to define video_set_lut() also, isn't it ?
It depends. What U-Boot version do you use? If you use mainline
U-Boot recent versions like v2013.01.01, then this function
already exists as a week default empty function. You do not always
need video_set_lut() functionality unless you want to use a frame
buffer configuration with 8 bits per pixel colour depth.
> Can I please get more information on what I have to handle inside the function ?
This video_set_lut() function is only needed if you use 8 bits per
pixel frame buffer. I doubt that you want to use it since the
splash screen quality will be really bad in this color depth mode.
If you want to use this depth, then this function should fill the
color palette (look up table) of the display controller using the
index argument of the function as an index into look-up table and
using other arguments as values for the look-up table entries
under that index.
> Also, Is there any place where I can of getting more information on the structure members
> of "struct GraphicDevice" ?
the needed struct members are more or less self-explanatory, so
these are not documented anywhere, I think. You need to init
only:
winSizeX - the width of the display in pixels
winSizeY - the height of the display in pixels
gdfBytesPP - frame buffer color depth in bytes per pixel
gdfIndex - graphics data format of the frame buffer,
it is one of
GDF__8BIT_INDEX
GDF_15BIT_555RGB
GDF_16BIT_565RGB
GDF_32BIT_X888RGB
GDF_24BIT_888RGB
GDF__8BIT_332RGB
frameAdrs - the starting frame buffer address in the video ram
You do not need to initialise other members.
Thanks,
Anatolij
next prev parent reply other threads:[~2013-03-27 15:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 8:27 [U-Boot] Displaying characters on the display in u-boot Bhargav A K
2013-03-27 11:39 ` Anatolij Gustschin
[not found] ` <9827C66E1D129C4183B8AD771A4A57709A02936174@EXGMBX01.sasken.com>
2013-03-27 15:00 ` Anatolij Gustschin [this message]
2013-03-27 15:35 ` Bhargav A K
2013-03-27 16:27 ` Anatolij Gustschin
2013-03-27 16:34 ` Bhargav A K
2013-04-19 15:59 ` Bhargav A K
2013-04-27 20:20 ` Bhargav A K
2013-04-28 14:22 ` Anatolij Gustschin
2013-05-10 10:30 ` Bhargav A K
2013-05-10 11:38 ` Anatolij Gustschin
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=20130327160054.6f97a717@crub \
--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