linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Jones <pjones@redhat.com>
To: Marcin Slusarz <marcin.slusarz@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Dave Airlie <airlied@redhat.com>,
	Huang Ying <ying.huang@intel.com>,
	linux-fbdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Alex Zhavnerchik <alex.vizor@gmail.com>
Subject: Re: [PATCH] efifb: fix framebuffer handoff
Date: Mon, 15 Feb 2010 15:36:35 +0000	[thread overview]
Message-ID: <4B796A03.5060909@redhat.com> (raw)
In-Reply-To: <20100213104148.GB2880@joi.lan>

On 02/13/2010 05:41 AM, Marcin Slusarz wrote:
> Commit 4410f3910947dcea8672280b3adecd53cec4e85e
> (fbdev: add support for handoff from firmware to hw framebuffers)
> didn't add fb_destroy operation to efifb. Fix it and change
> aperture_size to match size passed to request_mem_region.
> 
> See: http://bugzilla.kernel.org/show_bug.cgi?id\x15151
> 
> Reported-by: Alex Zhavnerchik <alex.vizor@gmail.com>
> Tested-by: Alex Zhavnerchik <alex.vizor@gmail.com>
> Cc: Peter Jones <pjones@redhat.com>
> Cc: Huang Ying <ying.huang@intel.com>
> Cc: Dave Airlie <airlied@redhat.com>
> Cc: linux-fbdev@vger.kernel.org
> Signed-off-by: Marcin Slusarz <marcin.slusarz@gmail.com>

Looks good.

Acked by: Peter Jones <pjones@redhat.com>

> ---
>  drivers/video/efifb.c |   11 ++++++++++-
>  1 files changed, 10 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/video/efifb.c b/drivers/video/efifb.c
> index eb12182..d25df51 100644
> --- a/drivers/video/efifb.c
> +++ b/drivers/video/efifb.c
> @@ -161,8 +161,17 @@ static int efifb_setcolreg(unsigned regno, unsigned red, unsigned green,
>  	return 0;
>  }
>  
> +static void efifb_destroy(struct fb_info *info)
> +{
> +	if (info->screen_base)
> +		iounmap(info->screen_base);
> +	release_mem_region(info->aperture_base, info->aperture_size);
> +	framebuffer_release(info);
> +}
> +
>  static struct fb_ops efifb_ops = {
>  	.owner		= THIS_MODULE,
> +	.fb_destroy	= efifb_destroy,
>  	.fb_setcolreg	= efifb_setcolreg,
>  	.fb_fillrect	= cfb_fillrect,
>  	.fb_copyarea	= cfb_copyarea,
> @@ -281,7 +290,7 @@ static int __init efifb_probe(struct platform_device *dev)
>  	info->par = NULL;
>  
>  	info->aperture_base = efifb_fix.smem_start;
> -	info->aperture_size = size_total;
> +	info->aperture_size = size_remap;
>  
>  	info->screen_base = ioremap(efifb_fix.smem_start, efifb_fix.smem_len);
>  	if (!info->screen_base) {


-- 
        Peter

Computer games don't affect kids; I mean if Pac-Man affected us as
kids, we'd all be running around in darkened rooms, munching magic
pills and listening to repetitive electronic music.
		-- Not actually Kristian Wilson, Nintendo, Inc, 1989

      reply	other threads:[~2010-02-15 15:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-10 19:55 [PATCH] efifb: fix framebuffer handoff Marcin Slusarz
2010-02-13 10:41 ` Marcin Slusarz
2010-02-15 15:36   ` Peter Jones [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=4B796A03.5060909@redhat.com \
    --to=pjones@redhat.com \
    --cc=airlied@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=alex.vizor@gmail.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcin.slusarz@gmail.com \
    --cc=ying.huang@intel.com \
    /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).