From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>,
Sundararaj Prabhu <Prabhu.Sundararaj@freescale.com>
Subject: Re: [meta-fsl-arm-extra] errors while building boundary kernel 3.14.28
Date: Wed, 21 Oct 2015 20:25:10 +0200 [thread overview]
Message-ID: <5627D886.1060701@pseudoterminal.org> (raw)
In-Reply-To: <CAP9ODKq0a_-pG_YFWEFpmj94dDw5gATyjZBbH06QvXrMb2oTyQ@mail.gmail.com>
Am 2015-10-21 um 20:21 schrieb Otavio Salvador:
> On Wed, Oct 21, 2015 at 4:11 PM, Carlos Rafael Giani
> <dv@pseudoterminal.org> 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.
prev parent reply other threads:[~2015-10-21 18:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 19:26 [meta-fsl-arm-extra] errors while building boundary kernel 3.14.28 Carlos Rafael Giani
2015-10-19 19:46 ` Otavio Salvador
2015-10-19 20:07 ` Carlos Rafael Giani
2015-10-19 20:12 ` Gary Thomas
2015-10-19 20:33 ` Carlos Rafael Giani
2015-10-20 11:21 ` Otavio Salvador
2015-10-21 7:29 ` Carlos Rafael Giani
2015-10-21 7:30 ` Carlos Rafael Giani
2015-10-21 12:31 ` Otavio Salvador
2015-10-21 17:59 ` Carlos Rafael Giani
2015-10-21 18:01 ` Otavio Salvador
2015-10-21 18:02 ` Sundararaj Prabhu
2015-10-21 18:11 ` Carlos Rafael Giani
2015-10-21 18:21 ` Otavio Salvador
2015-10-21 18:25 ` Carlos Rafael Giani [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=5627D886.1060701@pseudoterminal.org \
--to=dv@pseudoterminal.org \
--cc=Prabhu.Sundararaj@freescale.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio.salvador@ossystems.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.