From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 3EA6AE00708; Wed, 21 Oct 2015 11:25:19 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.0 SPF_HELO_PASS SPF: HELO matches SPF record * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from ptmx.org (ptmx.org [178.63.28.110]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 371F9E006D5 for ; Wed, 21 Oct 2015 11:25:12 -0700 (PDT) Received: from [192.168.178.14] (chello062178118086.5.14.vie.surfer.at [62.178.118.86]) by ptmx.org (Postfix) with ESMTPSA id F1E2623245; Wed, 21 Oct 2015 20:25:10 +0200 (CEST) To: Otavio Salvador References: <562543CC.5040705@pseudoterminal.org> <56254D6E.4070409@pseudoterminal.org> <56273EE6.90307@pseudoterminal.org> <5627D27A.5060704@pseudoterminal.org> <5627D556.4010505@pseudoterminal.org> From: Carlos Rafael Giani Message-ID: <5627D886.1060701@pseudoterminal.org> Date: Wed, 21 Oct 2015 20:25:10 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Cc: "meta-freescale@yoctoproject.org" , Sundararaj Prabhu Subject: Re: [meta-fsl-arm-extra] errors while building boundary kernel 3.14.28 X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Oct 2015 18:25:19 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Am 2015-10-21 um 20:21 schrieb Otavio Salvador: > On Wed, Oct 21, 2015 at 4:11 PM, Carlos Rafael Giani > wrote: >> Ah, found it. Something else is missing from the kernel. >> >> galcore: Unknown symbol v7_dma_flush_range (err 0) >> galcore: Unknown symbol v7_dma_map_area (err 0) >> galcore: Unknown symbol v7_dma_flush_range (err 0) >> >> I recall that these symbols have to be exposed explcitely, because they >> aren't exposed by default. > This was the first patch I pointed you to apply. > The strange thing is that this *is* applied already. I am checking if perhaps for some reason MULTI_CACHE is defined.