From: "akuster" <akuster808@gmail.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>,
"Robert Berger@yocto.user" <robert.berger.yocto.user@gmail.com>
Cc: Joshua Watt <JPEWhacker@gmail.com>,
docs@lists.yoctoproject.org, Paul Barker <pbarker@konsulko.com>
Subject: Re: [docs][PATCH] kernel-dev: Add FAQ for how to use a vanilla kernel
Date: Tue, 20 Oct 2020 15:09:21 -0700 [thread overview]
Message-ID: <a860f167-4f08-a48c-45b2-2de4c617ea00@gmail.com> (raw)
In-Reply-To: <CADkTA4N+dJv_QqtEiJBxdcZXE5SxkDjDJF-+4Sz6n4+wVDYRKw@mail.gmail.com>
On 10/20/20 2:14 PM, Bruce Ashfield wrote:
> On Tue, Oct 20, 2020 at 5:05 PM Robert Berger@yocto.user
> <robert.berger.yocto.user@gmail.com> wrote:
>> Hi,
>>
>> On 20/10/2020 21:14, Joshua Watt wrote:
>>> On Tue, Oct 20, 2020 at 12:03 PM Joshua Watt <jpewhacker@gmail.com> wrote:
>>>> +.. note::
>>>> + You will notice that this is will still pull the kernel source from `the
>>>> + Yocto Kernel git repo
>>>> + <https://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto/>`_, however it is
>>>> + using the default value for :term:`KBRANCH` (e.g. ``"v5.8/standard/base"``)
>>>> + which is an exact mirror of the upstream kernel.
>>> This is a lie. I thought it was the upstream mirror, but it's not.
>>> v5.8/base is the mirror and this one has a few extra patches.
>>>
>> And exactly because only Bruce knows (most of the time) what is in all
>> those funny branches why not use upstream (kernel.org) for a vanilla kernel?
>>
> We are documented how the single linux-yocto repository can be used to
> track tip (master), or any of the -stable upstream kernels
> (<version>/base), or the yocto specifics (<version>/standard/base),
> without needing to create 'x' recipes to do it. It is just a branch
> switch away.
>
> Someone can always use upstream in their own kernel recipe, we are
> just using this doc to describe what's in oe-core itself.
this is what I just did for the meta-odroid.
https://gitlab.com/akuster/meta-odroid/-/blob/master/recipes-kernel/linux/linux-yocto_5.8.bbappend
It you don't have your own kernel fragments, it could be simpler.
-armin
>
> Bruce
>
>> Robert
>
>
>
>
>
next prev parent reply other threads:[~2020-10-20 22:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 17:03 [docs][PATCH] kernel-dev: Add FAQ for how to use a vanilla kernel Joshua Watt
2020-10-20 18:14 ` Joshua Watt
2020-10-20 21:05 ` Robert Berger
2020-10-20 21:14 ` Bruce Ashfield
2020-10-20 21:34 ` Joshua Watt
2020-10-20 22:09 ` akuster [this message]
2020-10-20 22:04 ` akuster
2020-10-20 18:45 ` Quentin Schulz
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=a860f167-4f08-a48c-45b2-2de4c617ea00@gmail.com \
--to=akuster808@gmail.com \
--cc=JPEWhacker@gmail.com \
--cc=bruce.ashfield@gmail.com \
--cc=docs@lists.yoctoproject.org \
--cc=pbarker@konsulko.com \
--cc=robert.berger.yocto.user@gmail.com \
/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.