From patchwork Tue May 9 04:56:25 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Matthias Schwarzott X-Patchwork-Id: 41235 Received: from mail.tu-berlin.de ([130.149.7.33]) by www.linuxtv.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d7xCN-00030f-LG; Tue, 09 May 2017 04:56:35 +0000 X-tubIT-Incoming-IP: 209.132.180.67 Received: from vger.kernel.org ([209.132.180.67]) by mail.tu-berlin.de (exim-4.84_2/mailfrontend-6) with esmtp id 1d7xCL-0006sM-4N; Tue, 09 May 2017 06:56:35 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754152AbdEIE4b (ORCPT + 1 other); Tue, 9 May 2017 00:56:31 -0400 Received: from smtp.gentoo.org ([140.211.166.183]:47736 "EHLO smtp.gentoo.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751213AbdEIE4a (ORCPT ); Tue, 9 May 2017 00:56:30 -0400 Received: from [IPv6:2001:a62:204:ce01:831:5fee:13cd:5b2f] (unknown [IPv6:2001:a62:204:ce01:831:5fee:13cd:5b2f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: zzam) by smtp.gentoo.org (Postfix) with ESMTPSA id 3CDFC3416F6; Tue, 9 May 2017 04:56:28 +0000 (UTC) To: Linux Media Mailing List , Hans Verkuil From: Matthias Schwarzott Subject: Unknown symbol put_vaddr_frames when using media_build Message-ID: <6ea4c402-9523-2345-9dd3-0fb041f07f27@gentoo.org> Date: Tue, 9 May 2017 06:56:25 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 Content-Language: en-GB Sender: linux-media-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-media@vger.kernel.org X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.5.9.45116 X-PMX-Spam: Gauge=IIIIIIII, Probability=8%, Report=' HTML_00_01 0.05, HTML_00_10 0.05, MSGID_ADDED_BY_MTA 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_1500_1599 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, NO_CTA_URI_FOUND 0, NO_URI_FOUND 0, NO_URI_HTTPS 0, __CP_MEDIA_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_FROM 0, __HAS_LIST_ID 0, __HAS_MSGID 0, __HAS_X_MAILING_LIST 0, __MIME_TEXT_ONLY 0, __MIME_TEXT_P 0, __MIME_TEXT_P1 0, __MIME_VERSION 0, __MOZILLA_USER_AGENT 0, __NO_HTML_TAG_RAW 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __TO_NAME 0, __TO_NAME_DIFF_FROM_ACC 0, __TO_REAL_NAMES 0, __USER_AGENT 0' Hi! Whenever I compile the media drivers using media_build against a recent kernel, I get this message when loading them: [ 5.848537] media: Linux media interface: v0.10 [ 5.881440] Linux video capture interface: v2.00 [ 5.881441] WARNING: You are using an experimental version of the media stack. ... [ 6.166390] videobuf2_memops: Unknown symbol put_vaddr_frames (err 0) [ 6.166394] videobuf2_memops: Unknown symbol get_vaddr_frames (err 0) [ 6.166396] videobuf2_memops: Unknown symbol frame_vector_destroy (err 0) [ 6.166398] videobuf2_memops: Unknown symbol frame_vector_create (err 0) That means I am not able to load any drivers being based on videobuf2_memops without manual actions. I used kernel 4.11.0, but it does not matter which kernel version exactly is used. My solution for that has been to modify mm/Kconfig of my kernel like this and then enable FRAME_VECTOR in .config But I do not like that solution. I would prefer one of these solutions: 1. Have media_build apply its fallback the same way as for older kernels that do not even have the the FRAME_VECTOR support. 2. Get the above patch merged (plus description etc.). What do you think? Regards Matthias diff --git a/mm/Kconfig b/mm/Kconfig index 9b8fccb969dc..cfa6a80d1a0a 100644 --- a/mm/Kconfig +++ b/mm/Kconfig @@ -701,7 +701,7 @@ config ZONE_DEVICE If FS_DAX is enabled, then say Y. config FRAME_VECTOR - bool + tristate "frame vector" config ARCH_USES_HIGH_VMA_FLAGS bool