On Thu, Dec 1, 2022 at 12:05 AM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Wed, 2022-11-30 at 06:55 -0800, Sven via lists.yoctoproject.org
> wrote:
> > I have intermittent problems with a recipe that creates a user that
> > is member of groups that are created by a different
Agreed with Rudolf.
If the layer maintainer didn't bother to do at least do one build with new
release and adjust LAYERSERIES_COMPAT, then I don't consider that layer
well maintained (it could be someone else who uses the layer, tests it with
new release and sends PR to adjust
On Wed, Nov 30, 2022, 20:27 Zoran wrote:
> Hello to Yocto community,
>
> As I am much more passive yocto wise these few years ( working on
> Android build systems and around, this is also a nightmare, I should
> say ;-) ), I have one Yocto question which I never really understood.
>
> I will ask
Hello to Yocto community,
As I am much more passive yocto wise these few years ( working on
Android build systems and around, this is also a nightmare, I should
say ;-) ), I have one Yocto question which I never really understood.
I will ask it by example. I have one layer for the CAN tools and
Delete CONFIG_HIGHMEM and CONFIG_BACKLIGHT_PWM.
Signed-off-by: Xiaolei Wang
---
bsp/nxp-imx7/nxp-imx7.cfg | 3 ---
1 file changed, 3 deletions(-)
diff --git a/bsp/nxp-imx7/nxp-imx7.cfg b/bsp/nxp-imx7/nxp-imx7.cfg
index 308c5c32..db1b1944 100644
--- a/bsp/nxp-imx7/nxp-imx7.cfg
+++
Enable CONFIG_NOP_USB_XCEIV config for nxp-imx7.
Signed-off-by: Xiaolei Wang
---
bsp/nxp-imx7/nxp-imx7.cfg | 1 +
1 file changed, 1 insertion(+)
diff --git a/bsp/nxp-imx7/nxp-imx7.cfg b/bsp/nxp-imx7/nxp-imx7.cfg
index db1b1944..743acd76 100644
--- a/bsp/nxp-imx7/nxp-imx7.cfg
+++
enable CONFIG_ARM_IMX_CPUFREQ_DT config, this is supported
by imx7. Some places also rely on cpufreq, like imx_thermal.
Signed-off-by: Xiaolei Wang
---
bsp/nxp-imx7/nxp-imx7.cfg | 1 +
1 file changed, 1 insertion(+)
diff --git a/bsp/nxp-imx7/nxp-imx7.cfg b/bsp/nxp-imx7/nxp-imx7.cfg
index
According to upstream commit 96796c914b84("arm64: Kconfig.platforms:
Re-organized Broadcom menu"), it needs to enable kernel config ARCH_BCM
for raspberry pi platform.
Signed-off-by: Meng Li
---
bsp/bcm-2xxx-rpi/bcm-2xxx-rpi.cfg | 1 +
1 file changed, 1 insertion(+)
diff --git
From: Limeng
Hi Bruce,
Could you please help to merge this patch into yocto-kernel-cache, branch is
only master?
diffstat info ad below:
bcm-2xxx-rpi.cfg |1 +
1 file changed, 1 insertion(+)
thanks,
Limeng
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
One way I have gotten around this is by using an .inc file to create the
users/groups and then the recipes that need the user/group require/include
that .inc file.
On Wed, Nov 30, 2022 at 3:05 PM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Wed, 2022-11-30 at 06:55 -0800,
On Wed, 2022-11-30 at 06:55 -0800, Sven via lists.yoctoproject.org
wrote:
> I have intermittent problems with a recipe that creates a user that
> is member of groups that are created by a different recipe. This is
> the recipe that creates the groups:
>
> # recipe-a.bb
> inherit useradd
>
On Wed, 30 Nov 2022 at 09:28, Lukasz Majewski wrote:
> 2. There are ptest available [2] to validate if the Y2038 problem works
> correctly.
>
> 3. Support for running ptests mentioned in point 2. is already
> available in the poky repository [3].
I just ran these tests in (32 bit) qemux86 on top
Well, historically we used to have the OpenEmbedded Happy Hour after the
sessions on the second day of the Yocto Project Summit and ask people to
re-join a different Zoom room to socialize. This time around there's a
dedicated YP Summit social time reserved, so to avoid switchig Zooms, we
On Wed, 2022-11-30 at 17:56 +0100, Alexandre Belloni wrote:
> On 30/11/2022 16:46:17+, Ross Burton wrote:
> > On 30 Nov 2022, at 14:20, Richard Purdie via lists.yoctoproject.org
> > wrote:
> > > > > * Could we optionally disable some of the glibc 32 bit function calls
> > > > > to ensure
On 30/11/2022 16:46:17+, Ross Burton wrote:
> On 30 Nov 2022, at 14:20, Richard Purdie via lists.yoctoproject.org
> wrote:
> >>> * Could we optionally disable some of the glibc 32 bit function calls
> >>> to ensure they're not being used?
> >>
> >> Could you be more specific here? Would
On 30 Nov 2022, at 14:20, Richard Purdie via lists.yoctoproject.org
wrote:
>>> * Could we optionally disable some of the glibc 32 bit function calls
>>> to ensure they're not being used?
>>
>> Could you be more specific here? Would you like to disable some
>> syscalls?
>
> I'm meaning
On Wed, Nov 30, 2022 at 12:08 AM Alexander Kanavin
wrote:
>
> On Tue, 29 Nov 2022 at 16:45, Stephen Jolley wrote:
> > We’d welcome a proposal/series on how to move forward with the Y2038 work
> > for 32 bit platforms.
>
> I have the following proposal:
>
> 1. A branch is made where:
> a.
Hi,
I have intermittent problems with a recipe that creates a user that is member
of groups that are created by a different recipe. This is the recipe that
creates the groups:
# recipe-a.bb
inherit useradd
USERADD_PACKAGES = "${PN}"
GROUPADD_PARAM:${PN} = "--system gpio;--system i2c"
This is
On Wed, 2022-11-30 at 14:36 +0100, Lukasz Majewski wrote:
> > On Wed, 2022-11-30 at 09:07 +0100, Alexander Kanavin wrote:
> > > On Tue, 29 Nov 2022 at 16:45, Stephen Jolley
> > > wrote:
> > > > We’d welcome a proposal/series on how to move forward with the
> > > > Y2038 work for 32 bit
Hi Richard,
> On Wed, 2022-11-30 at 09:07 +0100, Alexander Kanavin wrote:
> > On Tue, 29 Nov 2022 at 16:45, Stephen Jolley
> > wrote:
> > > We’d welcome a proposal/series on how to move forward with the
> > > Y2038 work for 32 bit platforms.
> >
> > I have the following proposal:
> >
> >
On Wed, 2022-11-30 at 09:07 +0100, Alexander Kanavin wrote:
> On Tue, 29 Nov 2022 at 16:45, Stephen Jolley wrote:
> > We’d welcome a proposal/series on how to move forward with the Y2038 work
> > for 32 bit platforms.
>
> I have the following proposal:
>
> 1. A branch is made where:
> a.
I have a question here:
If I something like below in my recipe
SYSTEMD_SERVICE:${PN} = "${@bb.utils.contains('DISTRO_FEATURES', 'systemd',
'one.service', '', d)}"
Then, can I add multiple files with:
SYSTEMD_SERVICE:${PN} = "${@bb.utils.contains('DISTRO_FEATURES', 'systemd',
'one.service
On Wed, 2022-11-30 at 13:07 +0100, Alexander Kanavin wrote:
> On Wed, 30 Nov 2022 at 12:40, Richard Purdie
> wrote:
>
> > To be clear, we don't run ptests on 32 bit targets, only on qemux86-64
> > and qemuarm64 where we have KVM available. We do run image, sdk and
> > eSDK tests on our supported
On Wed, 30 Nov 2022 13:07:27 +0100
"Alexander Kanavin" wrote:
> On Wed, 30 Nov 2022 at 12:40, Richard Purdie
> wrote:
>
> > To be clear, we don't run ptests on 32 bit targets, only on
> > qemux86-64 and qemuarm64 where we have KVM available. We do run
> > image, sdk and eSDK tests on our
On Wed, 30 Nov 2022 at 11:52, Stephen John Smoogen wrote:
> Going from various problems I saw with systems with smaller time wraps,
> setting a time after wrap occurs misses most of the problems which wall
> occur. Many systems will work fine with either 'negative' or 'smaller dates'
> but
On Wed, 30 Nov 2022 at 12:40, Richard Purdie
wrote:
> To be clear, we don't run ptests on 32 bit targets, only on qemux86-64
> and qemuarm64 where we have KVM available. We do run image, sdk and
> eSDK tests on our supported qemu targets, 32 and 64 bit.
I think kvm does allow 32 bit guest on a
On Wed, 2022-11-30 at 12:02 +0100, Alexandre Belloni via
lists.openembedded.org wrote:
> On 30/11/2022 09:07:50+0100, Alexander Kanavin wrote:
> > On Tue, 29 Nov 2022 at 16:45, Stephen Jolley
> > wrote:
> > > We’d welcome a proposal/series on how to move forward with the Y2038 work
> > > for 32
On Wed, 30 Nov 2022 05:52:03 -0500
"Stephen John Smoogen" wrote:
> On Wed, 30 Nov 2022 at 03:08, Alexander Kanavin
> wrote:
>
> > On Tue, 29 Nov 2022 at 16:45, Stephen Jolley
> > wrote:
> > > We’d welcome a proposal/series on how to move forward with the
> > > Y2038
> > work for 32 bit
On 30/11/2022 09:07:50+0100, Alexander Kanavin wrote:
> On Tue, 29 Nov 2022 at 16:45, Stephen Jolley wrote:
> > We’d welcome a proposal/series on how to move forward with the Y2038 work
> > for 32 bit platforms.
>
> I have the following proposal:
>
> 1. A branch is made where:
> a.
On Wed, 30 Nov 2022 at 03:08, Alexander Kanavin
wrote:
> On Tue, 29 Nov 2022 at 16:45, Stephen Jolley
> wrote:
> > We’d welcome a proposal/series on how to move forward with the Y2038
> work for 32 bit platforms.
>
> I have the following proposal:
>
> 1. A branch is made where:
> a.
On Wed, 30 Nov 2022 at 10:40, Lukasz Majewski wrote:
> It would be even better if the meta-y2038 could be dropped and _all_
> its functionality could be merged to poky.
>
> That would be _awesome_.
>
> Please just be aware that this meta layer has some fixes for some
> packages (for Y2038 ready
Hi Alexander,
> On Wed, 30 Nov 2022 at 09:28, Lukasz Majewski wrote:
> > Please find a few comments:
> >
> > 1. There is already provided meta-y2038 [1] to test if 32 bit
> > systems correctly support Y2038 problem. It uses qemu machines from
> > OE/Yocto
> >
> > 2. There are ptest available [2]
On Wed, 30 Nov 2022 at 09:28, Lukasz Majewski wrote:
> Please find a few comments:
>
> 1. There is already provided meta-y2038 [1] to test if 32 bit systems
> correctly support Y2038 problem. It uses qemu machines from OE/Yocto
>
> 2. There are ptest available [2] to validate if the Y2038 problem
Hi Alexander,
> On Tue, 29 Nov 2022 at 16:45, Stephen Jolley
> wrote:
> > We’d welcome a proposal/series on how to move forward with the
> > Y2038 work for 32 bit platforms.
>
> I have the following proposal:
>
> 1. A branch is made where:
> a. "-D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64" is
On Tue, 29 Nov 2022 at 16:45, Stephen Jolley wrote:
> We’d welcome a proposal/series on how to move forward with the Y2038 work for
> 32 bit platforms.
I have the following proposal:
1. A branch is made where:
a. "-D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64" is enabled globally.
b. qemu is always
35 matches
Mail list logo
