On Wed, Jan 29, 2020 at 5:52 PM Kent Dorfman
wrote:
> OK guys. I was able to make it work with a higher priority layer and
> a bbappend file.
>
> The difference with my config file is that mine actually defines all
> the CONFIG_ options but many of them are =n to override selections
> made
OK guys. I was able to make it work with a higher priority layer and
a bbappend file.
The difference with my config file is that mine actually defines all
the CONFIG_ options but many of them are =n to override selections
made elsewhere. I just hope that the kernel config is smart enough in
all
Kent,
On 1/29/20 4:53 AM, Kent Dorfman wrote:
> I'd prefer to not go that route.It's a modified "vendor supplied"
> kernel from an internal tarball source, and for IA/QA reasons we're
> NOT going to refer to any external GIT repos.
Well that could be an internal git repository too. You
Hi Kent,
On Wed, Jan 29, 2020 at 1:53 PM Kent Dorfman
wrote:
> I'd prefer to not go that route.It's a modified "vendor supplied"
> kernel from an internal tarball source, and for IA/QA reasons we're
> NOT going to refer to any external GIT repos.
>
> There must be a recipe for your "vendor
Hi Kent,
On Wed, Jan 29, 2020 at 07:53:38AM -0500, Kent Dorfman wrote:
> I'd prefer to not go that route.It's a modified "vendor supplied"
> kernel from an internal tarball source, and for IA/QA reasons we're
> NOT going to refer to any external GIT repos.
>
> Can someone tell me how to just
Hi Kent,
Create your own kernel recipe and provide a defconfig for it:
SRC_URI += "file://defconfig"
For example to build a bleeding kernel directly from Linus' repo:
>
DESCRIPTION = "Linux Kernel from kernel.org Git Repository"
SECTION = "kernel"
LICENSE = "GPLv2"
require
I have a yocto generated sdk that includes a customized kernel. I do
NOT want to play with incremental config files. What I want is to
insert a .config file of my own choosing (generated outside of yocto)
into the kernel build, have it use only my .config, and then have that
.config remain as
