From: Patrick Ohly <patrick.ohly@intel.com>
To: Fan Zhang <fzhang@sgl.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: How to config kernel in my own meta layer?
Date: Sat, 23 Dec 2017 15:49:56 +0100 [thread overview]
Message-ID: <1514040596.10775.7.camel@intel.com> (raw)
In-Reply-To: <f5f50e1c-defb-149f-f795-921f4c1e648b@sgl.com>
On Thu, 2017-12-21 at 10:32 -0500, Fan Zhang wrote:
> Greetings,
>
> I have a recipes that requires 128MB of CMA allocation for DMA. I
> followed the instruction in http://www.yoctoproject.org/docs/1.6/ker
> nel-dev/kernel-dev.html#changing-the-configuration and did the
> following:
>
> My recipes structure:
>
>
> meta-mylayer\recipes-my\uio-test\
>
> 1. Then in uio-test folder, I have uio-test.bb
>
[...]
> My question: I think the cfg file is being parsed because if I change
> the folder name files to something else, bitbake will complaint about
> not being able to find uio-test.cfg. However, the final .config in
> built do not have the CMA allocated.
I suspect there's a fundamental misunderstanding. Your uio-test.bb is a
separate recipe, and therefore its content has no effect whatsoever on
the kernel configuration.
The right place to add your "file://uio-test.cfg" is in a .bbappend for
the kernel that you are building. But as Bruce said, that kernel must
be derived from linux-yocto.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
prev parent reply other threads:[~2017-12-23 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 15:32 How to config kernel in my own meta layer? Fan Zhang
2017-12-22 14:21 ` Bruce Ashfield
2017-12-23 14:49 ` Patrick Ohly [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=1514040596.10775.7.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=fzhang@sgl.com \
--cc=yocto@yoctoproject.org \
/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.