From: Vyacheslav Yurkov <uvv.mail@gmail.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] manuals: kernel-dev: Fix BSP in recipe space
Date: Mon, 26 Feb 2024 10:30:04 +0100 [thread overview]
Message-ID: <d830331b-f366-4a0b-b83d-8219c32a2e4f@gmail.com> (raw)
In-Reply-To: <CADkTA4NVhyHwRkjoodbxb6gvJM3y5UiW5WkyHha-dTuH2xs=wg@mail.gmail.com>
On 23.02.2024 14:44, Bruce Ashfield wrote:
> On Wed, Feb 21, 2024 at 2:26 AM Vyacheslav Yurkov <uvv.mail@gmail.com> wrote:
>> File fetcher doesn't have destsuffix parameter.
>>
> While the file fetcher doesn't have that option, it was the fact that
> it didn't have it that kept things working.
>
> If you use subdir, then in fact, a recipe space BSP doesn't work at
> all as the tools can't find the BSP definition.
>
> The kernel-yocto bbclass is what is using this to set up search paths
> for kernel features when it sees the type=kmeta.
>
> The option could have had a less confusing name (since it is
> effectively passthrough like "type=kmeta", but that's not something
> that I'm willing to change right now (I'll do it post release)
>
> But the documents are correct, you do need destsuffix or the
> recipe-space BSP will not work.
>
> Bruce
>
Oh, interesting. Perhaps the recipe-space BSP works this way, but the
recipe-space additions for other parts of 'kmeta' didn't work for me.
Whenever I wanted to extend kernel features that yocto-kernel-cache
didn't have, I had to use subdir.
Slava
prev parent reply other threads:[~2024-02-26 9:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 7:26 [PATCH] manuals: kernel-dev: Fix BSP in recipe space Vyacheslav Yurkov
2024-02-21 8:59 ` [docs] " Michael Opdenacker
2024-02-23 13:44 ` Bruce Ashfield
2024-02-26 9:30 ` Vyacheslav Yurkov [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=d830331b-f366-4a0b-b83d-8219c32a2e4f@gmail.com \
--to=uvv.mail@gmail.com \
--cc=bruce.ashfield@gmail.com \
--cc=docs@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).