From: Magnus Damm <magnus.damm@gmail.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 3/5] fbdev: sh_mobile_lcdc: increase maximum framebuffer
Date: Mon, 27 Dec 2010 02:02:58 +0000 [thread overview]
Message-ID: <AANLkTi=zRpLDg3Oqv+gq8sMAiidVoDojigQb9rn826aC@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1011041200050.13123@axis700.grange>
Hi Guennadi,
On Sun, Dec 26, 2010 at 6:44 AM, Guennadi Liakhovetski
<g.liakhovetski@gmx.de> wrote:
> Paul, apart from increasing the fb size to 1080p, this patch also fixes a
> regression, which leads to unusable by applications framebuffer on some
> platforms, including migor. This happens, when one of parameters lies
> outside of limits, being checked in sh_mobile_check_var(). On migor it is
>
> .left_margin = 0,
>
> Then the fb-console is working, but, e.g., mplayer is not. So, we need
> this patch in 2.6.37 too, please. Unfortunately, it also introduces a
> wrong format printk format, which a later patch of yours fixes, so, you
> might want to push that patch too, although, that's not that important.
It's great that you work on fixing this issue, thank you.
In the long run I wonder if it's best to try to get rid of the
MAX_XRES/MAX_YRES stuff from the LCDC driver. I understand that you
need to allocate the frame buffer memory early on, but it would be
much better if the maximum values could be kept in platform data. The
maximum resolution varies with CPU type, so a one-for-all modification
like this may break older platforms.
Thanks,
/ magnus
next prev parent reply other threads:[~2010-12-27 2:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 11:06 [PATCH 3/5] fbdev: sh_mobile_lcdc: increase maximum framebuffer size Guennadi Liakhovetski
2010-12-27 2:02 ` Magnus Damm [this message]
2010-12-27 13:41 ` [PATCH 3/5] fbdev: sh_mobile_lcdc: increase maximum framebuffer Guennadi Liakhovetski
2010-12-28 2:48 ` Magnus Damm
-- strict thread matches above, loose matches on Subject: below --
2010-12-25 21:44 Guennadi Liakhovetski
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='AANLkTi=zRpLDg3Oqv+gq8sMAiidVoDojigQb9rn826aC@mail.gmail.com' \
--to=magnus.damm@gmail.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;
as well as URLs for NNTP newsgroup(s).