From: Jingoo Han <jg1.han@samsung.com>
To: linux-fbdev@vger.kernel.org
Subject: RE: usage of height and width in fb_var_screeninfo
Date: Mon, 26 Mar 2012 08:15:17 +0000 [thread overview]
Message-ID: <000b01cd0b28$9471b650$bd5522f0$%han@samsung.com> (raw)
In-Reply-To: <CAGA24ML642uOP1tEp+VOTe0OZQ9S3HnP8Zi+N1n8X-QsjP9P2w@mail.gmail.com>
On Thu, Mar 22, 2012 at 8:53, Jun Nie <niej0001@gmail.com> wrote:
> Does anyone happen to know the usage of below member in
> fb_var_screeninfo? I do not know whether mm stand for geometry size or
> memory, can not find its usage in any driver neither. We considering
> to use it as zoomed size.
>
> struct fb_var_screeninfo {
> __u32 height; /* height of picture in mm */
> __u32 width; /* width of picture in mm */
>
Yes, right. Both thins are geometry sizes of LCD panel in millimeters.
Some OS platform needs these parameters.
Good luck.
Best regards,
Jingoo Han
prev parent reply other threads:[~2012-03-26 8:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 11:52 usage of height and width in fb_var_screeninfo Jun Nie
2012-03-22 12:15 ` Geert Uytterhoeven
2012-03-26 8:15 ` Jingoo Han [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='000b01cd0b28$9471b650$bd5522f0$%han@samsung.com' \
--to=jg1.han@samsung.com \
--cc=linux-fbdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox