On Thu, Dec 1, 2022 at 1:38 PM Richard Purdie
wrote:
>
> On Thu, 2022-12-01 at 12:32 -1000, Steve Sakoman wrote:
> > also remove obsolete fedora releases for kirkstone
>
> Please don't remove the obsolete ones, we leave the old ones here as a
> record in case we do end up wanting to know which
Signed-off-by: Steve Sakoman
---
config.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/config.py b/config.py
index de9356a..bf7126e 100644
--- a/config.py
+++ b/config.py
@@ -153,7 +153,7 @@ all_workers = workers + workers_bringup + workers_buildperf
+ workers_arm
#
On Thu, 2022-12-01 at 12:32 -1000, Steve Sakoman wrote:
> also remove obsolete fedora releases for kirkstone
Please don't remove the obsolete ones, we leave the old ones here as a
record in case we do end up wanting to know which distros we did test.
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
also remove obsolete fedora releases for kirkstone
Signed-off-by: Steve Sakoman
---
config.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/config.py b/config.py
index de9356a..082c853 100644
--- a/config.py
+++ b/config.py
@@ -153,7 +153,7 @@ all_workers = workers +
merged.
Bruce
In message: [yocto-kernel-cache][yocto-5.15][PATCH 1/3] nxp-imx7: enable
CONFIG_ARM_IMX_CPUFREQ_DT config
on 01/12/2022 Xiaolei Wang wrote:
> enable CONFIG_ARM_IMX_CPUFREQ_DT config, this is supported
> by imx7. Some places also rely on cpufreq, like imx_thermal.
>
>
In message: [yocto-kernel-cache]: bcm-2xxx-rpi: bcm-2xxx-rpi: enable kernel
config ARCH_BCM for raspberry pi platform
on 01/12/2022 Meng Li wrote:
> From: Limeng
>
> Hi Bruce,
>
> Could you please help to merge this patch into yocto-kernel-cache, branch is
> only master?
merged to master.
In message: [linux-yocto] [linux-yocto preempt-rt kernel v5.15]: nxp-s32g:
update to align with NXP SDK BSP35 RC7
on 30/11/2022 Zhantao Tang wrote:
> Hi Bruce,
>
>
> There are 13 new patches from bsp35 internal share repo, would you please
> help to
> merge the patches into branch
In message: [linux-yocto] [linux-yocto std kernel v5.15]: nxp-s32g: update to
align with NXP SDK BSP35 RC7
on 30/11/2022 Zhantao Tang wrote:
> Hi Bruce,
>
>
> There are 13 new patches from NXP SDK bsp35 internal share repo, would you
> please help to merge the patches
> into the
In message: [linux-yocto] [yocto-kernel-cache yocto-5.15]: nxp-s32g: enable
SCMI based cpufreq
on 30/11/2022 Zhantao Tang wrote:
>
> Hi Bruce,
>
> There is an patch of yocto-kernel-cache to update kernel configs for nxp-s32g
> bsp,
> Would you please help to merge this patch into
Do not bother... This is a war between me and the entire YOCTO
community of founders... It has been going for a while. Lot of INTEL
guys and former INTEL guys against former INTEL guy. Me.
But, I came here with Peace. It seems some people could not overcome their EGOs.
I am trying to ask for a
Greetings !
I am working on NXP's i.MX6UL SoC . I have built yocto successfully for the
same . I want to use to my own custom linux kernel source which is cloned in my
local PC in some specific directory (suppose in Desktop) , without using
default kernel source installed during the yocto
On Thu, 1 Dec 2022 at 17:41, Rudolf J Streif wrote:
>
>
> > Recently I've also seen this:
> > LAYERSERIES_COMPAT_phytec = "${LAYERSERIES_COMPAT_core}"
> >
> Oh no, now the entire Yocto Project world knows about this hack. Now we
> need a sanity checker for this in the insane class. :)
It's a
Recently I've also seen this:
LAYERSERIES_COMPAT_phytec = "${LAYERSERIES_COMPAT_core}"
Oh no, now the entire Yocto Project world knows about this hack. Now we
need a sanity checker for this in the insane class. :)
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
Hi Iggy,
On 12/1/22 13:55, Iggy via lists.yoctoproject.org wrote:
Hi,
I have a .inc file that contains this information:
# Set the MACHINE string, expected to eventually replace the long list of
# build settings below
EXTRA_OECMAKE += "-DRDK_MACHINE=${@d.getVar('MACHINE', False)} "
# Set the
Hi all,
Thanks for the pointers. I'm actually on kirkstone-4.0. I'll try the
work-arounds.
Best regards,
Sven
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58706): https://lists.yoctoproject.org/g/yocto/message/58706
Mute This Topic:
Agreed. Will revert.
Zee
___
On Thu, Dec 1, 2022 at 1:48 PM Ross Burton wrote:
>
> On 1 Dec 2022, at 12:46, Zoran Stojsavljevic
> wrote:
> > But, could you, please, allow me to have my own original cannelloni
> > recipe (yes, I developed it with some help from this community) on my
> >
Hi,
I have a .inc file that contains this information:
# Set the MACHINE string, expected to eventually replace the long list of
# build settings below
EXTRA_OECMAKE += "-DRDK_MACHINE=${@d.getVar('MACHINE', False)} "
# Set the region and platform type (defaults to Xi6 and UK)
On 1 Dec 2022, at 12:46, Zoran Stojsavljevic
wrote:
> But, could you, please, allow me to have my own original cannelloni
> recipe (yes, I developed it with some help from this community) on my
> own terms? I DID not copy it from anywhere. It is an ORIGINAL.
As I explained in the bug I filed in
Martin, U R too fast. Speedy Gonzales. ;-)
I do agree that this is the bad practice to change licences for the
known recipes. For the can-utils and socketcand. I'll revert this back
to GPLv2.
But, could you, please, allow me to have my own original cannelloni
recipe (yes, I developed it with
Ross,
It is now broken even in hardknott. I tried it, just as I tried it
before (it worked before).
I have no idea what the ERROR is:
zoran.s@NBK0005U:~/projects2/yocto/bbb-yocto/build$ bitbake -k
core-image-minimal
Loading cache: 100% |
On Thu, Dec 1, 2022 at 12:09 PM Ross Burton wrote:
> On 1 Dec 2022, at 04:27, Zoran via lists.yoctoproject.org
> wrote:
> > I do not understand why we need to explicitly name releases for such
> > simple generic layers?!
>
> The compatibility is because over time things change: override syntax
On 1 Dec 2022, at 04:27, Zoran via lists.yoctoproject.org
wrote:
> I do not understand why we need to explicitly name releases for such
> simple generic layers?!
The compatibility is because over time things change: override syntax has
changed, classes get added or removed, functionality may
On Thu, 2022-12-01 at 11:09 +0100, Alexander Kanavin wrote:
> And this is the commit that did this:
> https://git.phytec.de/meta-phytec/commit/conf/layer.conf?id=8261e896d2b43211e7377feb38e919336d47c39f
>
> Shame on you, phytec. Shame on you. What you do in your layers perhaps
> doesn't matter so
On Thu, 2022-12-01 at 11:27 +0100, Alexander Kanavin wrote:
> On Wed, 30 Nov 2022 at 14:15, Richard Purdie
> wrote:
> > * We need to have a 32 bit ptest run on the autobuilder (qemux86 should
> > work, not sure we can make qemuarm fast). Whether this is manually
> > triggered, not sure. We could
On Wed, 30 Nov 2022 at 14:15, Richard Purdie
wrote:
> * We need to have a 32 bit ptest run on the autobuilder (qemux86 should
> work, not sure we can make qemuarm fast). Whether this is manually
> triggered, not sure. We could have a smaller set of ptests to run for
> it?
I just ran qemux86 full
On Thu, 1 Dec 2022 at 08:51, Martin Jansa wrote:
>
>> I think there are some open bugs for useradd issues like this. It is
>> supposed to work but sounds like there are races. If there isn't a bug
>> open for it, there probably should be.
>
>
>
And this is the commit that did this:
https://git.phytec.de/meta-phytec/commit/conf/layer.conf?id=8261e896d2b43211e7377feb38e919336d47c39f
Shame on you, phytec. Shame on you. What you do in your layers perhaps
doesn't matter so much, but you also give everyone a bad example to
follow.
Alex
On
Hi Alexander,
> 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
28 matches
Mail list logo
