From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v2 05/29] atmel_lcdfb: use display information in info
Date: Tue, 28 Jun 2011 08:10:13 +0000 [thread overview]
Message-ID: <4E098C65.9040207@atmel.com> (raw)
In-Reply-To: <1308043507-11083-6-git-send-email-laurent.pinchart@ideasonboard.com>
Laurent,
Le 14/06/2011 11:24, Laurent Pinchart :
> We must not use any information in the passed var besides xoffset,
> yoffset and vmode as otherwise applications might abuse it.
>
> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Cc: Nicolas Ferre <nicolas.ferre@atmel.com>
> ---
> drivers/video/atmel_lcdfb.c | 15 +++++++++------
> 1 files changed, 9 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/video/atmel_lcdfb.c b/drivers/video/atmel_lcdfb.c
> index 4484c72..8b5d755 100644
> --- a/drivers/video/atmel_lcdfb.c
> +++ b/drivers/video/atmel_lcdfb.c
> @@ -39,7 +39,8 @@
> | FBINFO_HWACCEL_YPAN)
>
> static inline void atmel_lcdfb_update_dma2d(struct atmel_lcdfb_info *sinfo,
> - struct fb_var_screeninfo *var)
> + struct fb_var_screeninfo *var,
> + struct fb_info *info)
> {
>
> }
> @@ -50,14 +51,16 @@ static inline void atmel_lcdfb_update_dma2d(struct atmel_lcdfb_info *sinfo,
> | FBINFO_HWACCEL_YPAN)
>
> static void atmel_lcdfb_update_dma2d(struct atmel_lcdfb_info *sinfo,
> - struct fb_var_screeninfo *var)
> + struct fb_var_screeninfo *var,
> + struct fb_info *info)
> {
> u32 dma2dcfg;
> u32 pixeloff;
>
> - pixeloff = (var->xoffset * var->bits_per_pixel) & 0x1f;
> + pixeloff = (var->xoffset * info->var.bits_per_pixel) & 0x1f;
>
> - dma2dcfg = ((var->xres_virtual - var->xres) * var->bits_per_pixel) / 8;
> + dma2dcfg = (info-var.xres_virtual - info->var.xres)
------------------------^^^
Wolfram Sang identified this error: it cannot compile!
Thank you Wolfram.
> + * info->var.bits_per_pixel / 8;
> dma2dcfg |= pixeloff << ATMEL_LCDC_PIXELOFF_OFFSET;
> lcdc_writel(sinfo, ATMEL_LCDC_DMA2DCFG, dma2dcfg);
>
> @@ -249,14 +252,14 @@ static void atmel_lcdfb_update_dma(struct fb_info *info,
> unsigned long dma_addr;
>
> dma_addr = (fix->smem_start + var->yoffset * fix->line_length
> - + var->xoffset * var->bits_per_pixel / 8);
> + + var->xoffset * info->var.bits_per_pixel / 8);
>
> dma_addr &= ~3UL;
>
> /* Set framebuffer DMA base address and pixel offset */
> lcdc_writel(sinfo, ATMEL_LCDC_DMABADDR1, dma_addr);
>
> - atmel_lcdfb_update_dma2d(sinfo, var);
> + atmel_lcdfb_update_dma2d(sinfo, var, info);
> }
>
> static inline void atmel_lcdfb_free_video_memory(struct atmel_lcdfb_info *sinfo)
*When* the error will be corrected, you can submit it to linux-fbdev
with my:
Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
Thanks, best regards,
--
Nicolas Ferre
next prev parent reply other threads:[~2011-06-28 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 9:24 [PATCH v2 05/29] atmel_lcdfb: use display information in info not in var for panning Laurent Pinchart
2011-06-28 8:10 ` Nicolas Ferre [this message]
2011-06-28 9:09 ` Laurent Pinchart
2011-06-28 9:13 ` [PATCH v2 05/29] atmel_lcdfb: use display information in info Wolfram Sang
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=4E098C65.9040207@atmel.com \
--to=nicolas.ferre@atmel.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).