lkml.org 
[lkml]   [2017]   [Aug]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 4.4 50/58] drm/virtio: fix framebuffer sparse warning
    Date
    4.4-stable review patch.  If anyone has any objections, please let me know.

    ------------------

    From: Gerd Hoffmann <kraxel@redhat.com>


    [ Upstream commit 71d3f6ef7f5af38dea2975ec5715c88bae92e92d ]

    virtio uses normal ram as backing storage for the framebuffer, so we
    should assign the address to new screen_buffer (added by commit
    17a7b0b4d9749f80d365d7baff5dec2f54b0e992) instead of screen_base.

    Reported-by: Michael S. Tsirkin <mst@redhat.com>
    Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    ---
    drivers/gpu/drm/virtio/virtgpu_fb.c | 2 +-
    1 file changed, 1 insertion(+), 1 deletion(-)

    --- a/drivers/gpu/drm/virtio/virtgpu_fb.c
    +++ b/drivers/gpu/drm/virtio/virtgpu_fb.c
    @@ -338,7 +338,7 @@ static int virtio_gpufb_create(struct dr
    info->fbops = &virtio_gpufb_ops;
    info->pixmap.flags = FB_PIXMAP_SYSTEM;

    - info->screen_base = obj->vmap;
    + info->screen_buffer = obj->vmap;
    info->screen_size = obj->gem_base.size;
    drm_fb_helper_fill_fix(info, fb->pitches[0], fb->depth);
    drm_fb_helper_fill_var(info, &vfbdev->helper,

    \
     
     \ /
      Last update: 2017-08-09 21:46    [W:3.520 / U:0.284 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site