[PATCH v4] staging: vboxvideo: Add vboxvideo to drivers/staging

Daniel Vetter daniel at ffwll.ch
Wed Jun 28 13:05:22 UTC 2017


On Wed, Jun 28, 2017 at 2:46 PM, Hans de Goede <hdegoede at redhat.com> wrote:
> On 27-06-17 06:25, kbuild test robot wrote:
>>
>> Hi Hans,
>>
>> [auto build test ERROR on staging/staging-testing]
>> [also build test ERROR on v4.12-rc7 next-20170626]
>> [if your patch is applied to the wrong git tree, please drop us a note to
>> help improve the system]
>>
>> url:
>> https://github.com/0day-ci/linux/commits/Hans-de-Goede/staging-vboxvideo-Add-vboxvideo-to-drivers-staging/20170627-035353
>> config: x86_64-randconfig-n0-06270721 (attached as .config)
>> compiler: gcc-4.8 (Debian 4.8.4-1) 4.8.4
>> reproduce:
>>          # save the attached .config to linux build tree
>>          make ARCH=x86_64
>>
>> All errors (new ones prefixed by >>):
>>
>>>> ERROR: "framebuffer_release" [drivers/staging/vboxvideo/vboxvideo.ko]
>>>> undefined!
>>>> ERROR: "fb_set_suspend" [drivers/staging/vboxvideo/vboxvideo.ko]
>>>> undefined!
>>>> ERROR: "fb_dealloc_cmap" [drivers/staging/vboxvideo/vboxvideo.ko]
>>>> undefined!
>>>> ERROR: "unregister_framebuffer" [drivers/staging/vboxvideo/vboxvideo.ko]
>>>> undefined!
>
>
> Hmm, this is likely caused by building with a Kconfig with FBDEV disabled.
>
> The attached patch should fix this. I will send out a v5 with this squashed
> in later
> today.

If you use the drm fbdev helper library (all of it) then this should
all Just Work. Calling any fb core function from a drm driver directly
is a bug most likely.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch


More information about the dri-devel mailing list