From: Trevor Woerner <twoerner@gmail.com>
To: yocto-patches@lists.yoctoproject.org
Subject: Re: [yocto-patches] [meta-rockchip][PATCH 4/4] rauc demo: add
Date: Wed, 19 Jun 2024 08:20:45 -0400 [thread overview]
Message-ID: <20240619122044.GA18676@localhost> (raw)
In-Reply-To: <f08a3f8d-2928-4a00-8671-09f991ab55f0@cherry.de>
On Wed 2024-06-19 @ 01:55:59 PM, Quentin Schulz via lists.yoctoproject.org wrote:
> Hi Trevor,
>
> On 6/19/24 6:52 AM, Trevor Woerner via lists.yoctoproject.org wrote:
> [...]
> > > > diff --git a/classes-recipe/rk-rauc-demo.bbclass b/classes-recipe/rk-rauc-demo.bbclass
> > > > new file mode 100644
> > > > index 000000000000..25e105b53d09
> > > > --- /dev/null
> > > > +++ b/classes-recipe/rk-rauc-demo.bbclass
> > > > @@ -0,0 +1,8 @@
> > > > +inherit features_check
> > > > +
> > > > +REQUIRED_DISTRO_FEATURES += "systemd rauc"
> > > > +REQUIRED_MACHINE_FEATURES += "rk-u-boot-env"
> > > > +
> > > > +# 'RK_RAUC_DEMO' indicates the user wants to use the
> > > > +# rauc demo configuration from this layer
> > > > +OVERRIDES .= "${@ ':rk-rauc-demo' if bb.utils.to_boolean(d.getVar('RK_RAUC_DEMO'), False) else ''}"
> > >
> > > This very much smells like we should have a DISTRO for this instead no? What
> > > made you decide to go for a class?
> > >
> > > Also, why is here and also in the global class just below? This should be in
> > > the global class only to apply to all recipes?
> >
> > I want the build to fail if the user doesn't enable "rk-u-boot-env" in
> > MACHINE_FEATURES; you can't do RAUC if you can't save the U-Boot environment.
> > Second I want the build to fail if the user doesn't specify "rauc" in
> > DISTRO_FEATURES; the RAUC layer doens't work unless this is enabled. Therefore
> > I want to do a features_check somewhere, and the way features_check is
> > implemented means you need a class (?), specifically you need a classes-recipe
> > bbclass.
> >
> > If you do a features_check in classes/ it will fail because feature_check is
> > is oe-core's classes-recipe and it won't be found from a bbclass in classes/.
> > Perhaps I did it wrong, but this is what I found.
> >
> > Secondly if you look in meta-rauc you see that they're using a similar class
> > mechanism for the "rauc" override, is that not a common idiom? I'm simply
> > following that example with meta-rockchip's "rk-rauc-demo" override. If
> > there's a better way I'm happy to try it.
> >
>
> Can you point at some files? git grep OVERRIDES and git grep features_check
> returns nothing in the master branch of meta-rauc, so I probably am not
> looking in the right places or with the right terms.
Oops, I meant meta-rauc-community, and I was referring to just the overrides
thing, not the features_check thing:
https://github.com/rauc/meta-rauc-community/blob/master/meta-rauc-raspberrypi/classes/rauc-integration.bbclass
> [...]
> > On the other hand, if you're trying to understand what the partitions are and
> > what's available where and with what options, isn't /etc/fstab the first thing
> > you look at?
> >
>
> I run `mount` on my running target :)
>
> Cheers,
> Quentin
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#350): https://lists.yoctoproject.org/g/yocto-patches/message/350
> Mute This Topic: https://lists.yoctoproject.org/mt/106253218/900817
> Group Owner: yocto-patches+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto-patches/leave/13168745/900817/63955952/xyzzy [twoerner@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
next prev parent reply other threads:[~2024-06-19 12:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 23:08 [meta-rockchip][PATCH 1/4] rename root partition Trevor Woerner
2024-05-22 23:08 ` [meta-rockchip][PATCH 2/4] specify root partition type Trevor Woerner
2024-05-23 7:59 ` [yocto-patches] " Quentin Schulz
2024-05-22 23:08 ` [meta-rockchip][PATCH 3/4] u-boot: remove upstreamed dependency Trevor Woerner
2024-05-23 8:02 ` [yocto-patches] " Quentin Schulz
2024-05-22 23:08 ` [meta-rockchip][PATCH 4/4] rauc demo: add Trevor Woerner
2024-05-23 12:53 ` [yocto-patches] " Quentin Schulz
2024-06-19 4:52 ` Trevor Woerner
2024-06-19 5:19 ` Trevor Woerner
2024-06-19 11:55 ` Quentin Schulz
2024-06-19 12:20 ` Trevor Woerner [this message]
2024-05-23 7:52 ` [yocto-patches] [meta-rockchip][PATCH 1/4] rename root partition Quentin Schulz
2024-05-23 20:29 ` Trevor Woerner
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=20240619122044.GA18676@localhost \
--to=twoerner@gmail.com \
--cc=yocto-patches@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 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.