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 replace the config in an existing
recipe and make it permanent without creating/replacing the whole
package?
I'ts a single file that has to be inserted/used at the correct point
in the build. I'd say it's not rocket science but that's exactly what
it is for. LOL
On 1/28/20, Rudolf J Streif <rudolf.str...@ibeeto.com> wrote:
> 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 recipes-kernel/linux/linux-yocto.inc
>
> LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
>
> LINUX_VERSION ?= "5.5"
>
> LINUX_VERSION_EXTENSION ?= "-mykernel"
>
> PV = "${LINUX_VERSION}+git${SRCPV}"
>
> SRC_URI =
> “git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git;protocol=git;nocheckout=1"
>
> SRC_URI += "file://defconfig"
>
> SRCREV = "d5226fa6dbae0569ee43ecfc08bdcd6770fc4755"
>
> COMPATIBLE_MACHINE = "qemux86|qemux86-64"
> <<<<<
>
> :rjs
>
> On 1/28/20 7:15 PM, Kent Dorfman wrote:
>> 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 the persistent authoritative config as part of the
>> yocto layer.
>>
>> I have tried a variety of different approaches:
>> * using devtool, then loading my .config into the expanded source, but
>> "devtool finish" throws out my changes!
>>
>> * doing "bitbake menuconfig", can build a kernel using my config, but
>> it doesn't stay persistent in yocto
>>
>> * doing elaborate sort/merges on the yocto .config and my prefered
>> one...undefined behaviour
>>
>> and the build always seems to revert to either the original yocto
>> config, or a kludge of my options with a bunch of defaults I did not
>> specify.
>>
>> How can I take my existing .config and force yocto to use it, and it
>> only, forevermore?
>>
>>
>
> --
> -----
> Rudolf J Streif
> CEO/CTO ibeeto
> +1.855.442.3386 x700
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#48197): https://lists.yoctoproject.org/g/yocto/message/48197
Mute This Topic: https://lists.yoctoproject.org/mt/70234133/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
