Re: [linux-yocto][yocto-kernel-cache][yocto-6.1][PATCH] nxp-lx2xxx: add support NXP PCF2131 RTC

2024-05-16 Thread Bruce Ashfield
merged.

Bruce

In message: [linux-yocto][yocto-kernel-cache][yocto-6.1][PATCH] nxp-lx2xxx: add 
support NXP PCF2131 RTC
on 15/05/2024 Xulin Sun wrote:

> Add support NXP PCF2131 RTC for LX2160A-RDB Rev.D.
> 
> Signed-off-by: Xulin Sun 
> ---
>  bsp/nxp-lx2xxx/nxp-lx2xxx.cfg | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/bsp/nxp-lx2xxx/nxp-lx2xxx.cfg b/bsp/nxp-lx2xxx/nxp-lx2xxx.cfg
> index f8008cb7..c0321756 100644
> --- a/bsp/nxp-lx2xxx/nxp-lx2xxx.cfg
> +++ b/bsp/nxp-lx2xxx/nxp-lx2xxx.cfg
> @@ -138,6 +138,7 @@ CONFIG_I2C_MUX_PCA954x=y
>  CONFIG_RTC_CLASS=y
>  CONFIG_RTC_DRV_PCF2127=y
>  CONFIG_RTC_DRV_FSL_FTM_ALARM=y
> +CONFIG_RTC_DRV_PCF2131=y
>  
>  CONFIG_DMADEVICES=y
>  CONFIG_FSL_EDMA=y
> -- 
> 2.35.5
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13939): 
https://lists.yoctoproject.org/g/linux-yocto/message/13939
Mute This Topic: https://lists.yoctoproject.org/mt/106106960/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] [yocto-autobuilder2] schedulers: update branchdefaults for scarthgap

2024-05-15 Thread Steve Sakoman
Signed-off-by: Steve Sakoman 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63097): https://lists.yoctoproject.org/g/yocto/message/63097
Mute This Topic: https://lists.yoctoproject.org/mt/106117557/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][yocto-kernel-cache][yocto-6.1][PATCH] nxp-lx2xxx: add support NXP PCF2131 RTC

2024-05-14 Thread Xulin Sun via lists.yoctoproject.org
Add support NXP PCF2131 RTC for LX2160A-RDB Rev.D.

Signed-off-by: Xulin Sun 
---
 bsp/nxp-lx2xxx/nxp-lx2xxx.cfg | 1 +
 1 file changed, 1 insertion(+)

diff --git a/bsp/nxp-lx2xxx/nxp-lx2xxx.cfg b/bsp/nxp-lx2xxx/nxp-lx2xxx.cfg
index f8008cb7..c0321756 100644
--- a/bsp/nxp-lx2xxx/nxp-lx2xxx.cfg
+++ b/bsp/nxp-lx2xxx/nxp-lx2xxx.cfg
@@ -138,6 +138,7 @@ CONFIG_I2C_MUX_PCA954x=y
 CONFIG_RTC_CLASS=y
 CONFIG_RTC_DRV_PCF2127=y
 CONFIG_RTC_DRV_FSL_FTM_ALARM=y
+CONFIG_RTC_DRV_PCF2131=y
 
 CONFIG_DMADEVICES=y
 CONFIG_FSL_EDMA=y
-- 
2.35.5


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13936): 
https://lists.yoctoproject.org/g/linux-yocto/message/13936
Mute This Topic: https://lists.yoctoproject.org/mt/106106960/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto] [yocto-kernel-cache kernel v6.1]: aptiv-s32g: update to compatible with SDK BSP40

2024-05-13 Thread Bruce Ashfield
merged!

Bruce

In message: [yocto-kernel-cache kernel v6.1]: aptiv-s32g: update to compatible 
with SDK BSP40
on 11/05/2024 Zhantao Tang wrote:

> Hi Bruce,
> 
> There is a patch to update v6.1 kernel cache for aptiv-s32g bsp,
> would you please help to merge the following patch into
>   yocto-6.1
> branch?
> 
> Thanks,
> Zhantao
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13933): 
https://lists.yoctoproject.org/g/linux-yocto/message/13933
Mute This Topic: https://lists.yoctoproject.org/mt/106032784/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH] nxp-imx9: Enable RTC_DRV_BBNSM for nxp-imx9

2024-05-13 Thread Bruce Ashfield
merged.

Bruce

In message: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH] nxp-imx9: Enable 
RTC_DRV_BBNSM for nxp-imx9
on 09/05/2024 Xiaolei Wang wrote:

> Enable RTC_DRV_BBNSM for nxp-imx9.
> 
> Signed-off-by: Xiaolei Wang 
> ---
>  bsp/nxp-imx9/nxp-imx9.cfg | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg
> index d68b93be..4726803b 100644
> --- a/bsp/nxp-imx9/nxp-imx9.cfg
> +++ b/bsp/nxp-imx9/nxp-imx9.cfg
> @@ -487,6 +487,7 @@ CONFIG_RTC_CLASS=y
>  CONFIG_RTC_DRV_IMX_SC=y
>  CONFIG_RTC_DRV_IMX_RPMSG=y
>  CONFIG_RTC_DRV_SNVS=y
> +CONFIG_RTC_DRV_BBNSM=y
>  
>  #
>  # DMA Devices
> -- 
> 2.25.1
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13931): 
https://lists.yoctoproject.org/g/linux-yocto/message/13931
Mute This Topic: https://lists.yoctoproject.org/mt/105995051/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto] [yocto-kernel-cache kernel v6.1]: aptiv-s32g: update to compatible with SDK BSP40

2024-05-10 Thread Zhantao Tang via lists.yoctoproject.org
Hi Bruce,

There is a patch to update v6.1 kernel cache for aptiv-s32g bsp,
would you please help to merge the following patch into
yocto-6.1
branch?

Thanks,
Zhantao


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13927): 
https://lists.yoctoproject.org/g/linux-yocto/message/13927
Mute This Topic: https://lists.yoctoproject.org/mt/106032784/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Yocto recipe file://DIRECTORY fetcher recursive tracking?

2024-05-09 Thread Alexander Kanavin
On Thu, 9 May 2024 at 12:36, Richard Purdie via lists.yoctoproject.org
 wrote:
> > I have a dummy question regarding the file://DIRECTORY/ in recipe
> > usage, we are using this mechanism to directly point at a source
> > repository with potentially lots of subfolders, etc. Does bitbake
> > track file://DIRECTORY tracks all contents accordingly (i.e something
> > will recursively walk through this directory and checksum each file,
> > then arrive at a final combined checksum?) and if we happen to repo-
> > sync or git-pull to pull new changes in DIRECTORY/, Yocto will be
> > able to detect any changes in this directory and automatically
> > rebuild this recipe.
> >
> > I was getting mixed answers from a few sources, some said this can
> > work, some said it works sometimes but not always. So I would like to
> > get a definitive answer from Yocto forum.
>
> It is meant to work. There have been some bugs in this area in the
> past, I believe they have been fixed. It also doesn't perform well with
> large trees of files from a speed perspective.
>
> Something like git allows for much faster operations as git is designed
> to do tracking of this kind of thing.
>
> So yes, it should work but isn't optimal with really large trees.

I'd also note that pointing to a source checkout that is external to
the layer checkout isn't good for build reproducibility. How do you
ensure each revision of the layer repository maps 1:1 to a specific
revision of the source repo? That's why recipes typically contain
git:// uris with source revisions, or http tarballs with tarball
checksums: to ensure everyone builds from the same source tree. It's
typically not a good idea to refer to anything that is not a part of
the layer.

Alex

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63062): https://lists.yoctoproject.org/g/yocto/message/63062
Mute This Topic: https://lists.yoctoproject.org/mt/105997003/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Yocto recipe file://DIRECTORY fetcher recursive tracking?

2024-05-09 Thread Richard Purdie
On Wed, 2024-05-08 at 12:37 -0700, bibibobibo via lists.yoctoproject.org wrote:
> I have a dummy question regarding the file://DIRECTORY/ in recipe
> usage, we are using this mechanism to directly point at a source
> repository with potentially lots of subfolders, etc. Does bitbake
> track file://DIRECTORY tracks all contents accordingly (i.e something
> will recursively walk through this directory and checksum each file,
> then arrive at a final combined checksum?) and if we happen to repo-
> sync or git-pull to pull new changes in DIRECTORY/, Yocto will be
> able to detect any changes in this directory and automatically
> rebuild this recipe.
> 
> I was getting mixed answers from a few sources, some said this can
> work, some said it works sometimes but not always. So I would like to
> get a definitive answer from Yocto forum.

It is meant to work. There have been some bugs in this area in the
past, I believe they have been fixed. It also doesn't perform well with
large trees of files from a speed perspective.

Something like git allows for much faster operations as git is designed
to do tracking of this kind of thing.

So yes, it should work but isn't optimal with really large trees.

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63060): https://lists.yoctoproject.org/g/yocto/message/63060
Mute This Topic: https://lists.yoctoproject.org/mt/105997003/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Yocto recipe file://DIRECTORY fetcher recursive tracking?

2024-05-09 Thread bibibobibo
Greetings everyone,

I have a dummy question regarding the file://DIRECTORY/ in recipe usage, we are 
using this mechanism to directly point at a source repository with potentially 
lots of subfolders, etc. Does bitbake track file://DIRECTORY ( file://DIRECTORY 
) tracks all contents accordingly (i.e something will recursively walk through 
this directory and checksum each file, then arrive at a final combined 
checksum?) and if we happen to repo-sync or git-pull to pull new changes in 
DIRECTORY/, Yocto will be able to detect any changes in this directory and 
automatically rebuild this recipe.

I was getting mixed answers from a few sources, some said this can work, some 
said it works sometimes but not always. So I would like to get a definitive 
answer from Yocto forum.

Thanks,
Mike

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63058): https://lists.yoctoproject.org/g/yocto/message/63058
Mute This Topic: https://lists.yoctoproject.org/mt/105997003/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][yocto-kernel-cache yocto-6.1][PATCH] nxp-imx9: Enable RTC_DRV_BBNSM for nxp-imx9

2024-05-08 Thread Xiaolei Wang via lists.yoctoproject.org
Enable RTC_DRV_BBNSM for nxp-imx9.

Signed-off-by: Xiaolei Wang 
---
 bsp/nxp-imx9/nxp-imx9.cfg | 1 +
 1 file changed, 1 insertion(+)

diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg
index d68b93be..4726803b 100644
--- a/bsp/nxp-imx9/nxp-imx9.cfg
+++ b/bsp/nxp-imx9/nxp-imx9.cfg
@@ -487,6 +487,7 @@ CONFIG_RTC_CLASS=y
 CONFIG_RTC_DRV_IMX_SC=y
 CONFIG_RTC_DRV_IMX_RPMSG=y
 CONFIG_RTC_DRV_SNVS=y
+CONFIG_RTC_DRV_BBNSM=y
 
 #
 # DMA Devices
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13924): 
https://lists.yoctoproject.org/g/linux-yocto/message/13924
Mute This Topic: https://lists.yoctoproject.org/mt/105995051/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-6.6/master][PATCH V2] bsp/intel-x86: enable PCIe Advanced Error Reporting driver

2024-05-07 Thread Bruce Ashfield
On Tue, May 7, 2024 at 9:31 PM Liu, Yongxin  wrote:
>
> > -Original Message-
> > From: Bruce Ashfield 
> > Sent: Wednesday, May 8, 2024 9:20
> > To: Liu, Yongxin 
> > Cc: Hao, Kexin ; linux-
> > yo...@lists.yoctoproject.org
> > Subject: Re: [linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-
> > 6.6/master][PATCH V2] bsp/intel-x86: enable PCIe Advanced Error Reporting
> > driver
> >
> > CAUTION: This email comes from a non Wind River email account!
> > Do not click links or open attachments unless you recognize the sender and
> > know the content is safe.
> >
> > v2 worked perfectly.
> >
> > It is now merged.
>
> Thanks. But this patch is for yocto-6.1, yocto-6.6 and master.
> I saw it only in yocto-6.1.
> Please help to check.
>

Ooops. My mistake, it is on all the branches now.

Bruce

> Thanks,
> Yongxin
>
>
> >
> > Bruce
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13910): 
https://lists.yoctoproject.org/g/linux-yocto/message/13910
Mute This Topic: https://lists.yoctoproject.org/mt/105971882/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-6.6/master][PATCH V2] bsp/intel-x86: enable PCIe Advanced Error Reporting driver

2024-05-07 Thread Yongxin Liu via lists.yoctoproject.org
> -Original Message-
> From: Bruce Ashfield 
> Sent: Wednesday, May 8, 2024 9:20
> To: Liu, Yongxin 
> Cc: Hao, Kexin ; linux-
> yo...@lists.yoctoproject.org
> Subject: Re: [linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-
> 6.6/master][PATCH V2] bsp/intel-x86: enable PCIe Advanced Error Reporting
> driver
> 
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and
> know the content is safe.
> 
> v2 worked perfectly.
> 
> It is now merged.

Thanks. But this patch is for yocto-6.1, yocto-6.6 and master.
I saw it only in yocto-6.1.
Please help to check.

Thanks,
Yongxin
 

> 
> Bruce


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13909): 
https://lists.yoctoproject.org/g/linux-yocto/message/13909
Mute This Topic: https://lists.yoctoproject.org/mt/105971882/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-6.6/master][PATCH V2] bsp/intel-x86: enable PCIe Advanced Error Reporting driver

2024-05-07 Thread Bruce Ashfield
v2 worked perfectly.

It is now merged.

Bruce

In message: [linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-6.6/master][PATCH 
V2]  bsp/intel-x86: enable PCIe Advanced Error Reporting driver
on 08/05/2024 yongxin@windriver.com wrote:

> From: Yongxin Liu 
> 
> Signed-off-by: Yongxin Liu 
> ---
>  bsp/intel-x86/intel-x86.cfg | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/bsp/intel-x86/intel-x86.cfg b/bsp/intel-x86/intel-x86.cfg
> index 8266bf8f..87e50c06 100644
> --- a/bsp/intel-x86/intel-x86.cfg
> +++ b/bsp/intel-x86/intel-x86.cfg
> @@ -95,6 +95,7 @@ CONFIG_HOTPLUG_PCI=y
>  CONFIG_HOTPLUG_PCI_ACPI=y
>  
>  CONFIG_PCIEPORTBUS=y
> +CONFIG_PCIEAER=y
>  CONFIG_PCIEASPM=y
>  CONFIG_PCIEASPM_DEFAULT=y
>  
> -- 
> 2.43.2
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13908): 
https://lists.yoctoproject.org/g/linux-yocto/message/13908
Mute This Topic: https://lists.yoctoproject.org/mt/105971882/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-6.6/master][PATCH] bsp/intel-x86: enable PCIe Advanced Error Reporting driver

2024-05-07 Thread Kevin Hao
On Tue, May 07, 2024 at 03:45:05PM -0400, Bruce Ashfield via 
lists.yoctoproject.org wrote:
> Make sure you are following the configuration advice here:
> 
> https://docs.yoctoproject.org/contributor-guide/submit-changes.html#fixing-your-from-identity
> 
> And if the issue persists, we'll have to get into some of the discussion here:
> 
>  https://lore.kernel.org/yocto-docs/20240502191839a351b43b@mail.local/T/#t

By the way, Bruce, do you think we could also add linux-yocto to 
lore.kernel.org?
That way, we can conveniently use b4 for sending, applying and reviewing 
patches or
handling pull request?

Thanks,
Kevin


signature.asc
Description: PGP signature

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13907): 
https://lists.yoctoproject.org/g/linux-yocto/message/13907
Mute This Topic: https://lists.yoctoproject.org/mt/105931613/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-6.6/master][PATCH] bsp/intel-x86: enable PCIe Advanced Error Reporting driver

2024-05-07 Thread Yongxin Liu via lists.yoctoproject.org
> -Original Message-
> From: Bruce Ashfield 
> Sent: Wednesday, May 8, 2024 3:45
> To: bruce.ashfi...@gmail.com
> Cc: Liu, Yongxin ; Hao, Kexin
> ; linux-yocto@lists.yoctoproject.org
> Subject: Re: [linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-
> 6.6/master][PATCH] bsp/intel-x86: enable PCIe Advanced Error Reporting
> driver
> 
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and
> know the content is safe.
> 
> Make sure you are following the configuration advice here:
> 
> https://docs.yoctoproject.org/contributor-guide/submit-
> changes.html#fixing-your-from-identity
> 
> And if the issue persists, we'll have to get into some of the discussion
> here:
> 
>  https://lore.kernel.org/yocto-docs/20240502191839a351b43b@mail.local/T/#t
> 
> I'll drop this while I wait for a v2

I have sent a V2 after applying "git config --global sendemail.from 
"yongxin@windriver.com"".
But a new line "From: Yongxin Liu " appears in email 
body.
I don't know whether it matters or not. Please have a try on the V2.

Thanks,
Yongxin


> 
> Bruce
> 
> On Tue, May 7, 2024 at 3:28 PM Bruce Ashfield via lists.yoctoproject.org
>  wrote:
> >
> > I spoke too soon, the mailing list mangled the author field.
> >
> > remote: ##
> > remote: Invalid author Yongxin Liu via lists.yoctoproject.org
> > remote: ##
> >
> > I'm looking for the latest advice on fixing your client so that the
> > list software doesn't do the mangling.
> >
> > So for now, I've dropped the patch.
> >
> > Bruce
> >
> >
> > On Tue, May 7, 2024 at 3:25 PM Bruce Ashfield via
> > lists.yoctoproject.org
> >  wrote:
> > >
> > > merged.
> > >
> > > Bruce
> > >
> > > In message:
> > > [linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-6.6/master][PATCH]
> bsp/intel-x86: enable PCIe Advanced Error Reporting driver on 06/05/2024
> Yongxin Liu via lists.yoctoproject.org wrote:
> > >
> > > > Signed-off-by: Yongxin Liu 
> > > > ---
> > > >  bsp/intel-x86/intel-x86.cfg | 1 +
> > > >  1 file changed, 1 insertion(+)
> > > >
> > > > diff --git a/bsp/intel-x86/intel-x86.cfg
> > > > b/bsp/intel-x86/intel-x86.cfg index 8266bf8f..87e50c06 100644
> > > > --- a/bsp/intel-x86/intel-x86.cfg
> > > > +++ b/bsp/intel-x86/intel-x86.cfg
> > > > @@ -95,6 +95,7 @@ CONFIG_HOTPLUG_PCI=y  CONFIG_HOTPLUG_PCI_ACPI=y
> > > >
> > > >  CONFIG_PCIEPORTBUS=y
> > > > +CONFIG_PCIEAER=y
> > > >  CONFIG_PCIEASPM=y
> > > >  CONFIG_PCIEASPM_DEFAULT=y
> > > >
> > > > --
> > > > 2.43.2
> > > >
> > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> >
> >
> > --
> > - Thou shalt not follow the NULL pointer, for chaos and madness await
> > thee at its end
> > - "Use the force Harry" - Gandalf, Star Trek II
> >
> > 
> >
> 
> 
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await thee
> at its end
> - "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13906): 
https://lists.yoctoproject.org/g/linux-yocto/message/13906
Mute This Topic: https://lists.yoctoproject.org/mt/105931613/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-6.6/master][PATCH V2] bsp/intel-x86: enable PCIe Advanced Error Reporting driver

2024-05-07 Thread Yongxin Liu via lists.yoctoproject.org
From: Yongxin Liu 

Signed-off-by: Yongxin Liu 
---
 bsp/intel-x86/intel-x86.cfg | 1 +
 1 file changed, 1 insertion(+)

diff --git a/bsp/intel-x86/intel-x86.cfg b/bsp/intel-x86/intel-x86.cfg
index 8266bf8f..87e50c06 100644
--- a/bsp/intel-x86/intel-x86.cfg
+++ b/bsp/intel-x86/intel-x86.cfg
@@ -95,6 +95,7 @@ CONFIG_HOTPLUG_PCI=y
 CONFIG_HOTPLUG_PCI_ACPI=y
 
 CONFIG_PCIEPORTBUS=y
+CONFIG_PCIEAER=y
 CONFIG_PCIEASPM=y
 CONFIG_PCIEASPM_DEFAULT=y
 
-- 
2.43.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13905): 
https://lists.yoctoproject.org/g/linux-yocto/message/13905
Mute This Topic: https://lists.yoctoproject.org/mt/105971882/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto][yocto-kernel-cache][yocto-6.6][PATCH] nxp-imx8: add scc and cfg files for NXP IMX8 series platform

2024-05-07 Thread Bruce Ashfield
merged.

Bruce

In message: [linux-yocto][yocto-kernel-cache][yocto-6.6][PATCH] nxp-imx8: add 
scc and cfg files for NXP IMX8 series platform
on 07/05/2024 Xulin Sun wrote:

> Signed-off-by: Xulin Sun 
> ---
>  bsp/nxp-imx8/nxp-imx8-preempt-rt.cfg |  15 +
>  bsp/nxp-imx8/nxp-imx8-preempt-rt.scc |   9 +
>  bsp/nxp-imx8/nxp-imx8-standard.scc   |   7 +
>  bsp/nxp-imx8/nxp-imx8.cfg| 623 +++
>  bsp/nxp-imx8/nxp-imx8.scc|  11 +
>  5 files changed, 665 insertions(+)
>  create mode 100644 bsp/nxp-imx8/nxp-imx8-preempt-rt.cfg
>  create mode 100644 bsp/nxp-imx8/nxp-imx8-preempt-rt.scc
>  create mode 100644 bsp/nxp-imx8/nxp-imx8-standard.scc
>  create mode 100644 bsp/nxp-imx8/nxp-imx8.cfg
>  create mode 100644 bsp/nxp-imx8/nxp-imx8.scc
> 
> diff --git a/bsp/nxp-imx8/nxp-imx8-preempt-rt.cfg 
> b/bsp/nxp-imx8/nxp-imx8-preempt-rt.cfg
> new file mode 100644
> index ..780e974a
> --- /dev/null
> +++ b/bsp/nxp-imx8/nxp-imx8-preempt-rt.cfg
> @@ -0,0 +1,15 @@
> +..
> +.WARNING
> +.
> +. This file is a kernel configuration fragment, and not a full kernel
> +. configuration file.  The final kernel configuration is made up of
> +. an assembly of processed fragments, each of which is designed to
> +. capture a specific part of the final configuration (e.g. platform
> +. configuration, feature configuration, and board specific hardware
> +. configuration).  For more information on kernel configuration, please
> +. consult the product documentation.
> +.
> +..
> +
> +# CONFIG_TRANSPARENT_HUGEPAGE is not set
> +# CONFIG_LEDS_TRIGGER_CPU is not set
> diff --git a/bsp/nxp-imx8/nxp-imx8-preempt-rt.scc 
> b/bsp/nxp-imx8/nxp-imx8-preempt-rt.scc
> new file mode 100644
> index ..d900d656
> --- /dev/null
> +++ b/bsp/nxp-imx8/nxp-imx8-preempt-rt.scc
> @@ -0,0 +1,9 @@
> +define KMACHINE nxp-imx8
> +define KTYPE preempt-rt
> +define KARCH arm64
> +
> +include ktypes/preempt-rt
> +
> +include nxp-imx8.scc
> +
> +kconf hardware nxp-imx8-preempt-rt.cfg
> diff --git a/bsp/nxp-imx8/nxp-imx8-standard.scc 
> b/bsp/nxp-imx8/nxp-imx8-standard.scc
> new file mode 100644
> index ..d94f2dfd
> --- /dev/null
> +++ b/bsp/nxp-imx8/nxp-imx8-standard.scc
> @@ -0,0 +1,7 @@
> +define KMACHINE nxp-imx8
> +define KTYPE standard
> +define KARCH arm64
> +
> +include ktypes/standard
> +
> +include nxp-imx8.scc
> diff --git a/bsp/nxp-imx8/nxp-imx8.cfg b/bsp/nxp-imx8/nxp-imx8.cfg
> new file mode 100644
> index ..642c1489
> --- /dev/null
> +++ b/bsp/nxp-imx8/nxp-imx8.cfg
> @@ -0,0 +1,623 @@
> +CONFIG_ARM64=y
> +CONFIG_SMP=y
> +CONFIG_ARCH_NXP=y
> +CONFIG_ARCH_LAYERSCAPE=y
> +CONFIG_ARCH_MXC=y
> +CONFIG_HAVE_IMX_BUSFREQ=y
> +
> +CONFIG_PM=y
> +CONFIG_CPU_PM=y
> +
> +#
> +# CPU Idle
> +#
> +CONFIG_CPU_IDLE=y
> +CONFIG_ARM_PSCI_CPUIDLE=y
> +CONFIG_ARM_PSCI_CPUIDLE_DOMAIN=y
> +
> +#
> +# CPU Frequency scaling
> +#
> +CONFIG_CPU_FREQ=y
> +CONFIG_CPU_FREQ_GOV_ATTR_SET=y
> +CONFIG_CPU_FREQ_GOV_COMMON=y
> +CONFIG_CPU_FREQ_STAT=y
> +CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
> +CONFIG_CPU_FREQ_GOV_POWERSAVE=y
> +CONFIG_CPU_FREQ_GOV_USERSPACE=y
> +CONFIG_CPU_FREQ_GOV_ONDEMAND=y
> +CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
> +CONFIG_CPU_FREQ_GOV_SCHEDUTIL=y
> +
> +#
> +# CPU frequency scaling drivers
> +#
> +CONFIG_CPUFREQ_DT=y
> +CONFIG_ARM_IMX_CPUFREQ_DT=y
> +
> +#
> +# CAN
> +#
> +CONFIG_CAN=m
> +CONFIG_CAN_FLEXCAN=m
> +
> +CONFIG_PCI=y
> +CONFIG_PCI_MSI=y
> +CONFIG_PCI_IMX6=y
> +CONFIG_PCI_IMX6_HOST=y
> +CONFIG_PHY_FSL_IMX8Q_PCIE=y
> +
> +CONFIG_IMX_DSP=y
> +CONFIG_IMX_SCU=y
> +CONFIG_IMX_SCU_PD=y
> +CONFIG_IMX_SECO_MU=y
> +CONFIG_IMX_ELE_TRNG=y
> +
> +#
> +## MTD
> +#
> +CONFIG_MTD=y
> +CONFIG_MTD_CMDLINE_PARTS=y
> +CONFIG_MTD_BLOCK=y
> +CONFIG_MTD_CFI=y
> +CONFIG_MTD_CFI_ADV_OPTIONS=y
> +CONFIG_MTD_CFI_INTELEXT=y
> +CONFIG_MTD_CFI_AMDSTD=y
> +CONFIG_MTD_CFI_STAA=y
> +CONFIG_MTD_PHYSMAP=y
> +CONFIG_MTD_PHYSMAP_OF=y
> +CONFIG_MTD_DATAFLASH=y
> +CONFIG_MTD_RAW_NAND=y
> +CONFIG_MTD_NAND_DENALI_DT=y
> +CONFIG_MTD_SPI_NOR=y
> +CONFIG_MTD_SST25L=y
> +
> +#
> +## Regulator Driver
> +#
> +CONFIG_PWM=y
> +CONFIG_REGULATOR=y
> +CONFIG_REGULATOR_FIXED_VOLTAGE=y
> +CONFIG_REGULATOR_FAN53555=y
> +CONFIG_REGULATOR_GPIO=y
> +CONFIG_REGULATOR_MAX8973=y
> +CONFIG_REGULATOR_PCA9450=y
> +CONFIG_REGULATOR_PFUZE100=y
> +CONFIG_REGULATOR_PWM=y
> +
> +#
> +# MMC Driver
> +#
> +CONFIG

Re: [linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-6.6/master][PATCH] bsp/intel-x86: enable PCIe Advanced Error Reporting driver

2024-05-07 Thread Bruce Ashfield
Make sure you are following the configuration advice here:

https://docs.yoctoproject.org/contributor-guide/submit-changes.html#fixing-your-from-identity

And if the issue persists, we'll have to get into some of the discussion here:

 https://lore.kernel.org/yocto-docs/20240502191839a351b43b@mail.local/T/#t

I'll drop this while I wait for a v2

Bruce

On Tue, May 7, 2024 at 3:28 PM Bruce Ashfield via
lists.yoctoproject.org
 wrote:
>
> I spoke too soon, the mailing list mangled the author field.
>
> remote: ##
> remote: Invalid author Yongxin Liu via lists.yoctoproject.org
> remote: ##
>
> I'm looking for the latest advice on fixing your client so that the
> list software doesn't do the mangling.
>
> So for now, I've dropped the patch.
>
> Bruce
>
>
> On Tue, May 7, 2024 at 3:25 PM Bruce Ashfield via
> lists.yoctoproject.org
>  wrote:
> >
> > merged.
> >
> > Bruce
> >
> > In message: 
> > [linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-6.6/master][PATCH] 
> > bsp/intel-x86: enable PCIe Advanced Error Reporting driver
> > on 06/05/2024 Yongxin Liu via lists.yoctoproject.org wrote:
> >
> > > Signed-off-by: Yongxin Liu 
> > > ---
> > >  bsp/intel-x86/intel-x86.cfg | 1 +
> > >  1 file changed, 1 insertion(+)
> > >
> > > diff --git a/bsp/intel-x86/intel-x86.cfg b/bsp/intel-x86/intel-x86.cfg
> > > index 8266bf8f..87e50c06 100644
> > > --- a/bsp/intel-x86/intel-x86.cfg
> > > +++ b/bsp/intel-x86/intel-x86.cfg
> > > @@ -95,6 +95,7 @@ CONFIG_HOTPLUG_PCI=y
> > >  CONFIG_HOTPLUG_PCI_ACPI=y
> > >
> > >  CONFIG_PCIEPORTBUS=y
> > > +CONFIG_PCIEAER=y
> > >  CONFIG_PCIEASPM=y
> > >  CONFIG_PCIEASPM_DEFAULT=y
> > >
> > > --
> > > 2.43.2
> > >
> >
> > >
> > >
> > >
> >
> >
> >
> >
>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end
> - "Use the force Harry" - Gandalf, Star Trek II
>
> 
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13899): 
https://lists.yoctoproject.org/g/linux-yocto/message/13899
Mute This Topic: https://lists.yoctoproject.org/mt/105931613/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-6.6/master][PATCH] bsp/intel-x86: enable PCIe Advanced Error Reporting driver

2024-05-07 Thread Bruce Ashfield
I spoke too soon, the mailing list mangled the author field.

remote: ##
remote: Invalid author Yongxin Liu via lists.yoctoproject.org
remote: ##

I'm looking for the latest advice on fixing your client so that the
list software doesn't do the mangling.

So for now, I've dropped the patch.

Bruce


On Tue, May 7, 2024 at 3:25 PM Bruce Ashfield via
lists.yoctoproject.org
 wrote:
>
> merged.
>
> Bruce
>
> In message: 
> [linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-6.6/master][PATCH] 
> bsp/intel-x86: enable PCIe Advanced Error Reporting driver
> on 06/05/2024 Yongxin Liu via lists.yoctoproject.org wrote:
>
> > Signed-off-by: Yongxin Liu 
> > ---
> >  bsp/intel-x86/intel-x86.cfg | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/bsp/intel-x86/intel-x86.cfg b/bsp/intel-x86/intel-x86.cfg
> > index 8266bf8f..87e50c06 100644
> > --- a/bsp/intel-x86/intel-x86.cfg
> > +++ b/bsp/intel-x86/intel-x86.cfg
> > @@ -95,6 +95,7 @@ CONFIG_HOTPLUG_PCI=y
> >  CONFIG_HOTPLUG_PCI_ACPI=y
> >
> >  CONFIG_PCIEPORTBUS=y
> > +CONFIG_PCIEAER=y
> >  CONFIG_PCIEASPM=y
> >  CONFIG_PCIEASPM_DEFAULT=y
> >
> > --
> > 2.43.2
> >
>
> >
> >
> >
>
>
> 
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13898): 
https://lists.yoctoproject.org/g/linux-yocto/message/13898
Mute This Topic: https://lists.yoctoproject.org/mt/105931613/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-6.6/master][PATCH] bsp/intel-x86: enable PCIe Advanced Error Reporting driver

2024-05-07 Thread Bruce Ashfield
merged.

Bruce

In message: 
[linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-6.6/master][PATCH] 
bsp/intel-x86: enable PCIe Advanced Error Reporting driver
on 06/05/2024 Yongxin Liu via lists.yoctoproject.org wrote:

> Signed-off-by: Yongxin Liu 
> ---
>  bsp/intel-x86/intel-x86.cfg | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/bsp/intel-x86/intel-x86.cfg b/bsp/intel-x86/intel-x86.cfg
> index 8266bf8f..87e50c06 100644
> --- a/bsp/intel-x86/intel-x86.cfg
> +++ b/bsp/intel-x86/intel-x86.cfg
> @@ -95,6 +95,7 @@ CONFIG_HOTPLUG_PCI=y
>  CONFIG_HOTPLUG_PCI_ACPI=y
>  
>  CONFIG_PCIEPORTBUS=y
> +CONFIG_PCIEAER=y
>  CONFIG_PCIEASPM=y
>  CONFIG_PCIEASPM_DEFAULT=y
>  
> -- 
> 2.43.2
> 

> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13897): 
https://lists.yoctoproject.org/g/linux-yocto/message/13897
Mute This Topic: https://lists.yoctoproject.org/mt/105931613/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][yocto-kernel-cache][yocto-6.6][PATCH] nxp-imx8: add scc and cfg files for NXP IMX8 series platform

2024-05-07 Thread Xulin Sun via lists.yoctoproject.org
Signed-off-by: Xulin Sun 
---
 bsp/nxp-imx8/nxp-imx8-preempt-rt.cfg |  15 +
 bsp/nxp-imx8/nxp-imx8-preempt-rt.scc |   9 +
 bsp/nxp-imx8/nxp-imx8-standard.scc   |   7 +
 bsp/nxp-imx8/nxp-imx8.cfg| 623 +++
 bsp/nxp-imx8/nxp-imx8.scc|  11 +
 5 files changed, 665 insertions(+)
 create mode 100644 bsp/nxp-imx8/nxp-imx8-preempt-rt.cfg
 create mode 100644 bsp/nxp-imx8/nxp-imx8-preempt-rt.scc
 create mode 100644 bsp/nxp-imx8/nxp-imx8-standard.scc
 create mode 100644 bsp/nxp-imx8/nxp-imx8.cfg
 create mode 100644 bsp/nxp-imx8/nxp-imx8.scc

diff --git a/bsp/nxp-imx8/nxp-imx8-preempt-rt.cfg 
b/bsp/nxp-imx8/nxp-imx8-preempt-rt.cfg
new file mode 100644
index ..780e974a
--- /dev/null
+++ b/bsp/nxp-imx8/nxp-imx8-preempt-rt.cfg
@@ -0,0 +1,15 @@
+..
+.WARNING
+.
+. This file is a kernel configuration fragment, and not a full kernel
+. configuration file.  The final kernel configuration is made up of
+. an assembly of processed fragments, each of which is designed to
+. capture a specific part of the final configuration (e.g. platform
+. configuration, feature configuration, and board specific hardware
+. configuration).  For more information on kernel configuration, please
+. consult the product documentation.
+.
+..
+
+# CONFIG_TRANSPARENT_HUGEPAGE is not set
+# CONFIG_LEDS_TRIGGER_CPU is not set
diff --git a/bsp/nxp-imx8/nxp-imx8-preempt-rt.scc 
b/bsp/nxp-imx8/nxp-imx8-preempt-rt.scc
new file mode 100644
index ..d900d656
--- /dev/null
+++ b/bsp/nxp-imx8/nxp-imx8-preempt-rt.scc
@@ -0,0 +1,9 @@
+define KMACHINE nxp-imx8
+define KTYPE preempt-rt
+define KARCH arm64
+
+include ktypes/preempt-rt
+
+include nxp-imx8.scc
+
+kconf hardware nxp-imx8-preempt-rt.cfg
diff --git a/bsp/nxp-imx8/nxp-imx8-standard.scc 
b/bsp/nxp-imx8/nxp-imx8-standard.scc
new file mode 100644
index ..d94f2dfd
--- /dev/null
+++ b/bsp/nxp-imx8/nxp-imx8-standard.scc
@@ -0,0 +1,7 @@
+define KMACHINE nxp-imx8
+define KTYPE standard
+define KARCH arm64
+
+include ktypes/standard
+
+include nxp-imx8.scc
diff --git a/bsp/nxp-imx8/nxp-imx8.cfg b/bsp/nxp-imx8/nxp-imx8.cfg
new file mode 100644
index ..642c1489
--- /dev/null
+++ b/bsp/nxp-imx8/nxp-imx8.cfg
@@ -0,0 +1,623 @@
+CONFIG_ARM64=y
+CONFIG_SMP=y
+CONFIG_ARCH_NXP=y
+CONFIG_ARCH_LAYERSCAPE=y
+CONFIG_ARCH_MXC=y
+CONFIG_HAVE_IMX_BUSFREQ=y
+
+CONFIG_PM=y
+CONFIG_CPU_PM=y
+
+#
+# CPU Idle
+#
+CONFIG_CPU_IDLE=y
+CONFIG_ARM_PSCI_CPUIDLE=y
+CONFIG_ARM_PSCI_CPUIDLE_DOMAIN=y
+
+#
+# CPU Frequency scaling
+#
+CONFIG_CPU_FREQ=y
+CONFIG_CPU_FREQ_GOV_ATTR_SET=y
+CONFIG_CPU_FREQ_GOV_COMMON=y
+CONFIG_CPU_FREQ_STAT=y
+CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
+CONFIG_CPU_FREQ_GOV_POWERSAVE=y
+CONFIG_CPU_FREQ_GOV_USERSPACE=y
+CONFIG_CPU_FREQ_GOV_ONDEMAND=y
+CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
+CONFIG_CPU_FREQ_GOV_SCHEDUTIL=y
+
+#
+# CPU frequency scaling drivers
+#
+CONFIG_CPUFREQ_DT=y
+CONFIG_ARM_IMX_CPUFREQ_DT=y
+
+#
+# CAN
+#
+CONFIG_CAN=m
+CONFIG_CAN_FLEXCAN=m
+
+CONFIG_PCI=y
+CONFIG_PCI_MSI=y
+CONFIG_PCI_IMX6=y
+CONFIG_PCI_IMX6_HOST=y
+CONFIG_PHY_FSL_IMX8Q_PCIE=y
+
+CONFIG_IMX_DSP=y
+CONFIG_IMX_SCU=y
+CONFIG_IMX_SCU_PD=y
+CONFIG_IMX_SECO_MU=y
+CONFIG_IMX_ELE_TRNG=y
+
+#
+## MTD
+#
+CONFIG_MTD=y
+CONFIG_MTD_CMDLINE_PARTS=y
+CONFIG_MTD_BLOCK=y
+CONFIG_MTD_CFI=y
+CONFIG_MTD_CFI_ADV_OPTIONS=y
+CONFIG_MTD_CFI_INTELEXT=y
+CONFIG_MTD_CFI_AMDSTD=y
+CONFIG_MTD_CFI_STAA=y
+CONFIG_MTD_PHYSMAP=y
+CONFIG_MTD_PHYSMAP_OF=y
+CONFIG_MTD_DATAFLASH=y
+CONFIG_MTD_RAW_NAND=y
+CONFIG_MTD_NAND_DENALI_DT=y
+CONFIG_MTD_SPI_NOR=y
+CONFIG_MTD_SST25L=y
+
+#
+## Regulator Driver
+#
+CONFIG_PWM=y
+CONFIG_REGULATOR=y
+CONFIG_REGULATOR_FIXED_VOLTAGE=y
+CONFIG_REGULATOR_FAN53555=y
+CONFIG_REGULATOR_GPIO=y
+CONFIG_REGULATOR_MAX8973=y
+CONFIG_REGULATOR_PCA9450=y
+CONFIG_REGULATOR_PFUZE100=y
+CONFIG_REGULATOR_PWM=y
+
+#
+# MMC Driver
+#
+CONFIG_MMC=y
+CONFIG_MMC_SDHCI=y
+CONFIG_MMC_SDHCI_PLTFM=y
+CONFIG_MMC_SDHCI_ESDHC_IMX=y
+
+#
+# Controllers with non-SFF native interface
+#
+CONFIG_ATA=y
+CONFIG_MFD_SYSCON=y
+CONFIG_AHCI_IMX=y
+CONFIG_SATA_AHCI=y
+CONFIG_SATA_AHCI_PLATFORM=y
+CONFIG_LEDS_TRIGGERS=y
+
+#
+# Networking
+#
+CONFIG_FEC=y
+CONFIG_AT803X_PHY=y
+CONFIG_REALTEK_PHY=y
+CONFIG_STMMAC_ETH=y
+
+#
+# Input device support
+#
+CONFIG_INPUT=y
+CONFIG_INPUT_KEYBOARD=y
+CONFIG_INPUT_EVDEV=y
+CONFIG_KEYBOARD_ADC=m
+CONFIG_KEYBOARD_GPIO=y
+CONFIG_KEYBOARD_SNVS_PWRKEY=y
+CONFIG_KEYBOARD_IMX_SC_KEY=y
+CONFIG_INPUT_TOUCHSCREEN=y
+CONFIG_TOUCHSCREEN_ATMEL_MXT=m
+CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_I2C=m
+CONFIG_INPUT_MISC=y
+
+#
+# Serial drivers
+#
+
+CONFIG_SERIAL_IMX=y
+CONFIG_SERIAL_IMX_CONSOLE=y
+CONFIG_SERIAL_FSL_LPUART=y
+CONFIG_SERIAL_FSL_LPUART_CONSOLE=y
+CONFIG_SERIAL_FSL_LINFLEXUART=y
+CONFIG_SERIAL_FSL_LINFLEXUART_CONSOLE=y
+
+#
+# SPI
+#
+CONFIG_SPI=y
+CONFIG_SPI_MASTER=y
+CONFIG_SPI_MEM=y

[linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-6.6/master][PATCH] bsp/intel-x86: enable PCIe Advanced Error Reporting driver

2024-05-05 Thread Yongxin Liu via lists.yoctoproject.org
Signed-off-by: Yongxin Liu 
---
 bsp/intel-x86/intel-x86.cfg | 1 +
 1 file changed, 1 insertion(+)

diff --git a/bsp/intel-x86/intel-x86.cfg b/bsp/intel-x86/intel-x86.cfg
index 8266bf8f..87e50c06 100644
--- a/bsp/intel-x86/intel-x86.cfg
+++ b/bsp/intel-x86/intel-x86.cfg
@@ -95,6 +95,7 @@ CONFIG_HOTPLUG_PCI=y
 CONFIG_HOTPLUG_PCI_ACPI=y
 
 CONFIG_PCIEPORTBUS=y
+CONFIG_PCIEAER=y
 CONFIG_PCIEASPM=y
 CONFIG_PCIEASPM_DEFAULT=y
 
-- 
2.43.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13890): 
https://lists.yoctoproject.org/g/linux-yocto/message/13890
Mute This Topic: https://lists.yoctoproject.org/mt/105931613/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] [yocto-autobuilder-helper] config-json: use quillback branch for meta-agl

2024-04-28 Thread Steve Sakoman
kirkstone is no longer supported on master branch

Signed-off-by: Steve Sakoman 
---
 config.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/config.json b/config.json
index 60fe6a4..cc6d45c 100644
--- a/config.json
+++ b/config.json
@@ -1284,7 +1284,7 @@
 },
 "meta-agl": {
 "url" : "https://git.automotivelinux.org/AGL/meta-agl;,
-"branch" : "master",
+"branch" : "quillback",
 "revision" : "HEAD",
 "no-layer-add" : true
 },
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63007): https://lists.yoctoproject.org/g/yocto/message/63007
Mute This Topic: https://lists.yoctoproject.org/mt/105782483/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] [yocto-autobuilder-helper] [PATCH] cve-generate-chartdata: Handle unexpected files in the stats directory

2024-04-26 Thread Richard Purdie
A build of "stable/dunfell-nut" caused incorrect data to be added to the metrics
repo and resulted in script failures. Handle this situation better.

Signed-off-by: Richard Purdie 
---
 scripts/cve-generate-chartdata | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/scripts/cve-generate-chartdata b/scripts/cve-generate-chartdata
index e187f8b..8b9df64 100755
--- a/scripts/cve-generate-chartdata
+++ b/scripts/cve-generate-chartdata
@@ -28,7 +28,11 @@ for branch in os.listdir(args.resultsdir):
 branchdir = os.path.join(args.resultsdir, branch)
 for f in os.listdir(branchdir):
 ts = f.split(".")[0]
-rounded_ts = str(round_to_day(ts))
+try:
+rounded_ts = str(round_to_day(ts))
+except ValueError:
+# Couldn't parse a timestamp from filename
+continue
 if rounded_ts not in counts:
 counts[rounded_ts] = {}
 if branch not in counts[rounded_ts]:
-- 
2.40.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63004): https://lists.yoctoproject.org/g/yocto/message/63004
Mute This Topic: https://lists.yoctoproject.org/mt/105747379/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Yocto common place holder for includes which used multiple recipe

2024-04-23 Thread Altous, Salahaldeen
On Tue, Apr 23, 2024 at 05:27 AM, Alexander Kanavin wrote:

> 
> Yes this should be fine. But don't forget to inherit it in all the
> recipes that would use these variables.
> 
> Here's an example:
> https://git.yoctoproject.org/poky/tree/meta/classes-recipe/gnomebase.bbclass
> 

Thanks I will give a try

> 
> 
> Alex
> 
> On Tue, 23 Apr 2024 at 14:19, Altous, Salahaldeen via
> Lists.Yoctoproject.Org
>  wrote:
> 
>> Hi Alex
>> 
>> thanks for your quick reply.
>> 
>> On Tue, Apr 23, 2024 at 05:02 AM, Alexander Kanavin wrote:
>> 
>> I think you can simply make it a class and put under
>> classes/some.bbclass? Plenty of recipes in oe-core do this, see e.g.
>> gnomebase.bbclass.
>> 
>> I need something like these these variables
>> 
>> EXTERNAL_PROJECT_XXX_TYPE ?= "lib"
>> EXTERNAL_PROJECT_XXX_NAME ?= "lc_xxx"
>> EXTERNAL_PROJECT_XXX_GIT_URI ?=
>> "${COMPANY_GIT_REPO}:test/independent-modules/lc_xxx.git"
>> EXTERNAL_PROJECT_XXX_GIT_BRANCH ?= "development"
>> EXTERNAL_PROJECT_XXX_GIT_TAG ?= "0.4.3-dev"
>> 
>> EXTERNAL_PROJECT_YYY_TYPE ?= "lib"
>> EXTERNAL_PROJECT_YYY_NAME ?= "lc-yyy"
>> EXTERNAL_PROJECT_XXX_GIT_URI ?=
>> "${COMPANY_GIT_REPO}:test/independent-modules/lc_xxx.git"
>> EXTERNAL_PROJECT_YYY_GIT_BRANCH ?= "development"
>> EXTERNAL_PROJECT_YYY_GIT_TAG ?= "0.2.1-dev"
>> 
>> is this something possible with bbclass?
>> 
>> Salahaldeen
>> 
>> 
>> Alex
>> 
>> On Tue, 23 Apr 2024 at 13:57, Altous, Salahaldeen via
>> lists.yoctoproject.org
>>  wrote:
>> 
>> Hi All,
>> 
>> I need a common place holder to share one include files which can be used
>> by multiple recipe (this include files includes some variables like
>> SRC_URL, tag, gitbranch, ..., etc).
>> 
>> I can copy it to each recipe but I am looking for the best practice to
>> share a common inc file for all recipes in meta-xxx which can be found by
>> default and this need to be under meta-xxx folder.
>> 
>> thanks in advance.
>> 
>> 
>> 
>> Regards,
>> 
>> Salahaldeen Altous
> 
> 

Thanks I will give a try

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62989): https://lists.yoctoproject.org/g/yocto/message/62989
Mute This Topic: https://lists.yoctoproject.org/mt/105687839/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Yocto common place holder for includes which used multiple recipe

2024-04-23 Thread Alexander Kanavin
Yes this should be fine. But don't forget to inherit it in all the
recipes that would use these variables.

Here's an example:
https://git.yoctoproject.org/poky/tree/meta/classes-recipe/gnomebase.bbclass

Alex

On Tue, 23 Apr 2024 at 14:19, Altous, Salahaldeen via
Lists.Yoctoproject.Org
 wrote:
>
> Hi Alex
>
> thanks for your quick reply.
>
> On Tue, Apr 23, 2024 at 05:02 AM, Alexander Kanavin wrote:
>
> I think you can simply make it a class and put under
> classes/some.bbclass? Plenty of recipes in oe-core do this, see e.g.
> gnomebase.bbclass.
>
> I need something like these these variables
>
> EXTERNAL_PROJECT_XXX_TYPE ?= "lib"
> EXTERNAL_PROJECT_XXX_NAME ?= "lc_xxx"
> EXTERNAL_PROJECT_XXX_GIT_URI ?= 
> "${COMPANY_GIT_REPO}:test/independent-modules/lc_xxx.git"
> EXTERNAL_PROJECT_XXX_GIT_BRANCH ?= "development"
> EXTERNAL_PROJECT_XXX_GIT_TAG ?= "0.4.3-dev"
>
> EXTERNAL_PROJECT_YYY_TYPE ?= "lib"
> EXTERNAL_PROJECT_YYY_NAME ?= "lc-yyy"
> EXTERNAL_PROJECT_XXX_GIT_URI ?= 
> "${COMPANY_GIT_REPO}:test/independent-modules/lc_xxx.git"
> EXTERNAL_PROJECT_YYY_GIT_BRANCH ?= "development"
> EXTERNAL_PROJECT_YYY_GIT_TAG ?= "0.2.1-dev"
>
> is this something possible with bbclass?
>
> Salahaldeen
>
>
> Alex
>
> On Tue, 23 Apr 2024 at 13:57, Altous, Salahaldeen via
> lists.yoctoproject.org
>  wrote:
>
> Hi All,
>
> I need a common place holder to share one include files which can be used by 
> multiple recipe (this include files includes some variables like SRC_URL, 
> tag, gitbranch, ..., etc).
>
> I can copy it to each recipe but I am looking for the best practice to share 
> a common inc file for all recipes in meta-xxx which can be found by default 
> and this need to be under meta-xxx folder.
>
> thanks in advance.
>
>
>
> Regards,
>
> Salahaldeen Altous
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62988): https://lists.yoctoproject.org/g/yocto/message/62988
Mute This Topic: https://lists.yoctoproject.org/mt/105687839/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Yocto common place holder for includes which used multiple recipe

2024-04-23 Thread Altous, Salahaldeen
Hi Alex

thanks for your quick reply.

On Tue, Apr 23, 2024 at 05:02 AM, Alexander Kanavin wrote:

> 
> I think you can simply make it a class and put under
> classes/some.bbclass? Plenty of recipes in oe-core do this, see e.g.
> gnomebase.bbclass.

I need something like these these variables

EXTERNAL_PROJECT_XXX_TYPE ?= "lib"
EXTERNAL_PROJECT_XXX_NAME ?= "lc_xxx"
EXTERNAL_PROJECT_XXX_GIT_URI ?= 
"${COMPANY_GIT_REPO}:test/independent-modules/lc_xxx.git"
EXTERNAL_PROJECT_XXX_GIT_BRANCH ?= "development"
EXTERNAL_PROJECT_XXX_GIT_TAG ?= "0.4.3-dev"

EXTERNAL_PROJECT_YYY_TYPE ?= "lib"
EXTERNAL_PROJECT_YYY_NAME ?= "lc-yyy"
EXTERNAL_PROJECT_XXX_GIT_URI ?= 
"${COMPANY_GIT_REPO}:test/independent-modules/lc_xxx.git"
EXTERNAL_PROJECT_YYY_GIT_BRANCH ?= "development"
EXTERNAL_PROJECT_YYY_GIT_TAG ?= "0.2.1-dev"

is this something possible with bbclass?

Salahaldeen

> 
> 
> Alex
> 
> On Tue, 23 Apr 2024 at 13:57, Altous, Salahaldeen via
> lists.yoctoproject.org
>  wrote:
> 
>> Hi All,
>> 
>> I need a common place holder to share one include files which can be used
>> by multiple recipe (this include files includes some variables like
>> SRC_URL, tag, gitbranch, ..., etc).
>> 
>> I can copy it to each recipe but I am looking for the best practice to
>> share a common inc file for all recipes in meta-xxx which can be found by
>> default and this need to be under meta-xxx folder.
>> 
>> thanks in advance.
>> 
>> 
>> 
>> Regards,
>> 
>> Salahaldeen Altous
>> 
>> 
>> 
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62987): https://lists.yoctoproject.org/g/yocto/message/62987
Mute This Topic: https://lists.yoctoproject.org/mt/105687839/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Yocto common place holder for includes which used multiple recipe

2024-04-23 Thread Alexander Kanavin
I think you can simply make it a class and put under
classes/some.bbclass? Plenty of recipes in oe-core do this, see e.g.
gnomebase.bbclass.

Alex

On Tue, 23 Apr 2024 at 13:57, Altous, Salahaldeen via
lists.yoctoproject.org
 wrote:
>
> Hi All,
>
> I need a common place holder to share one include files which can be used by 
> multiple recipe (this include files includes some variables like SRC_URL, 
> tag, gitbranch, ..., etc).
>
> I can copy it to each recipe but I am looking for the best practice to share 
> a common inc file for all recipes in meta-xxx which can be found by default 
> and this need to be under meta-xxx folder.
>
> thanks in advance.
>
>
>
> Regards,
>
> Salahaldeen Altous
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62986): https://lists.yoctoproject.org/g/yocto/message/62986
Mute This Topic: https://lists.yoctoproject.org/mt/105687839/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Yocto common place holder for includes which used multiple recipe

2024-04-23 Thread Altous, Salahaldeen
Hi All,

I need a common place holder to share one include files which can be used by 
multiple recipe (this include files includes some variables like SRC_URL, tag, 
gitbranch, ..., etc).

I can copy it to each recipe but I am looking for the best practice to share a 
common inc file for all recipes in meta-xxx which can be found by default and 
this need to be under meta-xxx folder.

thanks in advance.

Regards,

Salahaldeen Altous

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62985): https://lists.yoctoproject.org/g/yocto/message/62985
Mute This Topic: https://lists.yoctoproject.org/mt/105687839/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto] [yocto-kernel-cache kernel v6.1]: nxp-s32g: update to compatible with SDK BSP40

2024-04-22 Thread Bruce Ashfield
In message: [yocto-kernel-cache kernel v6.1]: nxp-s32g: update to compatible 
with SDK BSP40
on 22/04/2024 Zhantao Tang wrote:

> Hi Bruce,
> 
> There is a patch to update v6.1 kernel cache for nxp-s32g bsp,
> would you please help to merge the following patch into
>   yocto-6.1

merged.

Bruce

> branch?
> 
> Thanks,
> Zhantao
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13851): 
https://lists.yoctoproject.org/g/linux-yocto/message/13851
Mute This Topic: https://lists.yoctoproject.org/mt/105665221/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH] nxp-imx9: Enable VIDEO_AP1302

2024-04-22 Thread Bruce Ashfield
merged.

Bruce

In message: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH] nxp-imx9: Enable 
VIDEO_AP1302
on 21/04/2024 Xiaolei Wang wrote:

> Enable VIDEO_AP1302 for imx93, since 
> ap1302_60fps_ar0144_27M_2Lane_awb_tuning.bin
> firmware needs to be loaded, build it as a module
> 
> Signed-off-by: Xiaolei Wang 
> ---
>  bsp/nxp-imx9/nxp-imx9.cfg | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg
> index 5e4cd6dc..d68b93be 100644
> --- a/bsp/nxp-imx9/nxp-imx9.cfg
> +++ b/bsp/nxp-imx9/nxp-imx9.cfg
> @@ -251,6 +251,7 @@ CONFIG_MXC_CAMERA_OV5640_MIPI_V2=y
>  #
>  CONFIG_VIDEO_IMX8_JPEG=m
>  CONFIG_VIDEO_OV5640=y
> +CONFIG_VIDEO_AP1302=m
>  
>  #
>  # Graphics support
> -- 
> 2.25.1
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13850): 
https://lists.yoctoproject.org/g/linux-yocto/message/13850
Mute This Topic: https://lists.yoctoproject.org/mt/105646492/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto] [yocto-kernel-cache kernel v6.1]: nxp-s32g: update to compatible with SDK BSP40

2024-04-22 Thread Zhantao Tang via lists.yoctoproject.org
Hi Bruce,

There is a patch to update v6.1 kernel cache for nxp-s32g bsp,
would you please help to merge the following patch into
yocto-6.1
branch?

Thanks,
Zhantao


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13845): 
https://lists.yoctoproject.org/g/linux-yocto/message/13845
Mute This Topic: https://lists.yoctoproject.org/mt/105665221/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][yocto-kernel-cache yocto-6.1][PATCH] nxp-imx9: Enable VIDEO_AP1302

2024-04-20 Thread Xiaolei Wang via lists.yoctoproject.org
Enable VIDEO_AP1302 for imx93, since 
ap1302_60fps_ar0144_27M_2Lane_awb_tuning.bin
firmware needs to be loaded, build it as a module

Signed-off-by: Xiaolei Wang 
---
 bsp/nxp-imx9/nxp-imx9.cfg | 1 +
 1 file changed, 1 insertion(+)

diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg
index 5e4cd6dc..d68b93be 100644
--- a/bsp/nxp-imx9/nxp-imx9.cfg
+++ b/bsp/nxp-imx9/nxp-imx9.cfg
@@ -251,6 +251,7 @@ CONFIG_MXC_CAMERA_OV5640_MIPI_V2=y
 #
 CONFIG_VIDEO_IMX8_JPEG=m
 CONFIG_VIDEO_OV5640=y
+CONFIG_VIDEO_AP1302=m
 
 #
 # Graphics support
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13844): 
https://lists.yoctoproject.org/g/linux-yocto/message/13844
Mute This Topic: https://lists.yoctoproject.org/mt/105646492/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH] nxp-imx9: Enable GPIO_VF610 for nxp-imx9

2024-04-17 Thread Bruce Ashfield
merged.

Bruce

In message: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH] nxp-imx9: Enable 
GPIO_VF610 for nxp-imx9
on 16/04/2024 Xiaolei Wang wrote:

> Enable GPIO_VF610 for nxp-imx9.
> 
> Signed-off-by: Xiaolei Wang 
> ---
>  bsp/nxp-imx9/nxp-imx9.cfg | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg
> index 8654f93c..5e4cd6dc 100644
> --- a/bsp/nxp-imx9/nxp-imx9.cfg
> +++ b/bsp/nxp-imx9/nxp-imx9.cfg
> @@ -86,6 +86,7 @@ CONFIG_REGULATOR_PCA9450=y
>  CONFIG_REGULATOR_PFUZE100=y
>  CONFIG_REGULATOR_PWM=y
>  CONFIG_PWM_ADP5585=y
> +CONFIG_GPIO_VF610=y
>  
>  #
>  # MMC Driver
> -- 
> 2.25.1
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13831): 
https://lists.yoctoproject.org/g/linux-yocto/message/13831
Mute This Topic: https://lists.yoctoproject.org/mt/105553457/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][yocto-kernel-cache yocto-6.1][PATCH] nxp-imx9: Enable GPIO_VF610 for nxp-imx9

2024-04-16 Thread Xiaolei Wang via lists.yoctoproject.org
Enable GPIO_VF610 for nxp-imx9.

Signed-off-by: Xiaolei Wang 
---
 bsp/nxp-imx9/nxp-imx9.cfg | 1 +
 1 file changed, 1 insertion(+)

diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg
index 8654f93c..5e4cd6dc 100644
--- a/bsp/nxp-imx9/nxp-imx9.cfg
+++ b/bsp/nxp-imx9/nxp-imx9.cfg
@@ -86,6 +86,7 @@ CONFIG_REGULATOR_PCA9450=y
 CONFIG_REGULATOR_PFUZE100=y
 CONFIG_REGULATOR_PWM=y
 CONFIG_PWM_ADP5585=y
+CONFIG_GPIO_VF610=y
 
 #
 # MMC Driver
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13823): 
https://lists.yoctoproject.org/g/linux-yocto/message/13823
Mute This Topic: https://lists.yoctoproject.org/mt/105553457/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto] [yocto-kernel-cache kernel v6.1]: nxp-s32g: update to compatible with SDK BSP40

2024-04-15 Thread Bruce Ashfield
Thanks for the heads up. I've dropped it from my queue.

Bruce

On Mon, Apr 15, 2024 at 4:46 AM Tang, Zhantao 
wrote:

> Hi Bruce,
>
> Please ignore this request, I will send a new one later.
>
> Thanks,
> Zhantao
>
> --
> *From:* linux-yocto@lists.yoctoproject.org <
> linux-yocto@lists.yoctoproject.org> on behalf of Zhantao Tang via
> lists.yoctoproject.org 
> *Sent:* Sunday, April 14, 2024 7:24:58 AM
> *To:* bruce.ashfi...@gmail.com 
> *Cc:* linux-yocto@lists.yoctoproject.org <
> linux-yocto@lists.yoctoproject.org>
> *Subject:* [linux-yocto] [yocto-kernel-cache kernel v6.1]: nxp-s32g:
> update to compatible with SDK BSP40
>
> Hi Bruce,
>
> There is a patch to update v6.1 kernel cache for nxp-s32g bsp,
> would you please help to merge the following patch into
> yocto-6.1
> branch?
>
> Thanks,
> Zhantao
>
>

-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end
- "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13814): 
https://lists.yoctoproject.org/g/linux-yocto/message/13814
Mute This Topic: https://lists.yoctoproject.org/mt/105509335/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto] [yocto-kernel-cache kernel v6.1]: nxp-s32g: update to compatible with SDK BSP40

2024-04-15 Thread Zhantao Tang via lists.yoctoproject.org
Hi Bruce,

Please ignore this request, I will send a new one later.

Thanks,
Zhantao


From: linux-yocto@lists.yoctoproject.org  
on behalf of Zhantao Tang via lists.yoctoproject.org 

Sent: Sunday, April 14, 2024 7:24:58 AM
To: bruce.ashfi...@gmail.com 
Cc: linux-yocto@lists.yoctoproject.org 
Subject: [linux-yocto] [yocto-kernel-cache kernel v6.1]: nxp-s32g: update to 
compatible with SDK BSP40

Hi Bruce,

There is a patch to update v6.1 kernel cache for nxp-s32g bsp,
would you please help to merge the following patch into
yocto-6.1
branch?

Thanks,
Zhantao


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13810): 
https://lists.yoctoproject.org/g/linux-yocto/message/13810
Mute This Topic: https://lists.yoctoproject.org/mt/105509335/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto] [yocto-kernel-cache kernel v6.1]: nxp-s32g: update to compatible with SDK BSP40

2024-04-13 Thread Zhantao Tang via lists.yoctoproject.org
Hi Bruce,

There is a patch to update v6.1 kernel cache for nxp-s32g bsp,
would you please help to merge the following patch into
yocto-6.1
branch?

Thanks,
Zhantao


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13805): 
https://lists.yoctoproject.org/g/linux-yocto/message/13805
Mute This Topic: https://lists.yoctoproject.org/mt/105509335/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 1/1] nxp-imx9: Enable Arm ETHOS NPU

2024-04-05 Thread Bruce Ashfield
merged.

Bruce

In message: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 1/1] nxp-imx9: 
Enable Arm ETHOS NPU
on 03/04/2024 Xiaolei Wang wrote:

> Enable Arm ETHOS NPU.
> 
> Signed-off-by: Xiaolei Wang 
> ---
>  bsp/nxp-imx9/nxp-imx9.cfg | 5 +
>  1 file changed, 5 insertions(+)
> 
> diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg
> index 8ad37abb..8654f93c 100644
> --- a/bsp/nxp-imx9/nxp-imx9.cfg
> +++ b/bsp/nxp-imx9/nxp-imx9.cfg
> @@ -284,6 +284,11 @@ CONFIG_DRM_ITE_IT6263=y
>  #
>  CONFIG_MXC_GPU_VIV=y
>  
> +#
> +# Arm Ethos-U NPU
> +#
> +CONFIG_ETHOSU=y
> +
>  #
>  # I2C encoder or helper chips
>  #
> -- 
> 2.25.1
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13776): 
https://lists.yoctoproject.org/g/linux-yocto/message/13776
Mute This Topic: https://lists.yoctoproject.org/mt/105302004/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto] [yocto-kernel-cache yocto-6.1][PATCH] Revert "features/nf_tables: nft_objref is now builtin"

2024-04-05 Thread Bruce Ashfield
merged.

Bruce

In message: [linux-yocto] [yocto-kernel-cache yocto-6.1][PATCH] Revert 
"features/nf_tables: nft_objref is now builtin"
on 02/04/2024 Lyu, William via lists.yoctoproject.org wrote:

> From: William Lyu 
> 
> This reverts commit dbe1767f364cdbf7dcc75433635678bd39c71e1f.
> 
> The reverted commit removes kernel configuration CONFIG_NFT_OBJREF which
> became builtin starting from kernel v6.2 [1]. However, this kernel
> configuration is still available in kernel v6.1. So, this kernel
> configuration option should NOT be removed from "yocto-kernel-cache" on
> branch "yocto-6.1".
> 
> References
> [1] 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d037abc2414b4539401e0e6aa278bedc4628ad69
> 
> Signed-off-by: William Lyu 
> ---
>  features/nf_tables/nf_tables.cfg | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/features/nf_tables/nf_tables.cfg 
> b/features/nf_tables/nf_tables.cfg
> index 5b0f28df..4debc628 100644
> --- a/features/nf_tables/nf_tables.cfg
> +++ b/features/nf_tables/nf_tables.cfg
> @@ -11,6 +11,7 @@ CONFIG_NFT_LIMIT=m
>  CONFIG_NFT_CONNLIMIT=m
>  CONFIG_NFT_TUNNEL=m
>  CONFIG_NFT_NAT=m
> +CONFIG_NFT_OBJREF=m
>  CONFIG_NFT_QUEUE=m
>  CONFIG_NFT_REJECT=m
>  CONFIG_NFT_REJECT_INET=m
> -- 
> 2.43.0
> 

> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13775): 
https://lists.yoctoproject.org/g/linux-yocto/message/13775
Mute This Topic: https://lists.yoctoproject.org/mt/105291813/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto] [yocto-kernel-cache yocto-6.4][PATCH 1/2] features/nf_tables: nft_objref is now builtin

2024-04-05 Thread Bruce Ashfield
merged.

Bruce

In message: [linux-yocto] [yocto-kernel-cache yocto-6.4][PATCH 1/2] 
features/nf_tables: nft_objref is now builtin
on 02/04/2024 Lyu, William via lists.yoctoproject.org wrote:

> From: William Lyu 
> 
> Backported from commit on branch "yocto-6.6":
> 40ecdcc5e4f5053536cec6e3f74334aa418f07cc
> 
> Starting from kernel v6.2 (including all rc versions),
> CONFIG_NFT_OBJREF has become builtin and cannot be disabled [1]. So,
> this configure option is removed from nf_tables.cfg.
> 
> References
> [1] 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d037abc2414b4539401e0e6aa278bedc4628ad69
> 
> Signed-off-by: William Lyu 
> ---
>  features/nf_tables/nf_tables.cfg | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/features/nf_tables/nf_tables.cfg 
> b/features/nf_tables/nf_tables.cfg
> index 4debc628..5b0f28df 100644
> --- a/features/nf_tables/nf_tables.cfg
> +++ b/features/nf_tables/nf_tables.cfg
> @@ -11,7 +11,6 @@ CONFIG_NFT_LIMIT=m
>  CONFIG_NFT_CONNLIMIT=m
>  CONFIG_NFT_TUNNEL=m
>  CONFIG_NFT_NAT=m
> -CONFIG_NFT_OBJREF=m
>  CONFIG_NFT_QUEUE=m
>  CONFIG_NFT_REJECT=m
>  CONFIG_NFT_REJECT_INET=m
> -- 
> 2.43.0
> 

> 
> 
> 



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13774): 
https://lists.yoctoproject.org/g/linux-yocto/message/13774
Mute This Topic: https://lists.yoctoproject.org/mt/105350943/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto] [yocto-kernel-cache yocto-6.5][PATCH 1/2] features/nf_tables: nft_objref is now builtin

2024-04-05 Thread Bruce Ashfield
merged.

Bruce

In message: [linux-yocto] [yocto-kernel-cache yocto-6.5][PATCH 1/2] 
features/nf_tables: nft_objref is now builtin
on 02/04/2024 Lyu, William via lists.yoctoproject.org wrote:

> From: William Lyu 
> 
> Backported from commit on branch "yocto-6.6":
> 40ecdcc5e4f5053536cec6e3f74334aa418f07cc
> 
> Starting from kernel v6.2 (including all rc versions),
> CONFIG_NFT_OBJREF has become builtin and cannot be disabled [1]. So,
> this configure option is removed from nf_tables.cfg.
> 
> References
> [1] 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d037abc2414b4539401e0e6aa278bedc4628ad69
> 
> Signed-off-by: William Lyu 
> ---
>  features/nf_tables/nf_tables.cfg | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/features/nf_tables/nf_tables.cfg 
> b/features/nf_tables/nf_tables.cfg
> index 4debc628..5b0f28df 100644
> --- a/features/nf_tables/nf_tables.cfg
> +++ b/features/nf_tables/nf_tables.cfg
> @@ -11,7 +11,6 @@ CONFIG_NFT_LIMIT=m
>  CONFIG_NFT_CONNLIMIT=m
>  CONFIG_NFT_TUNNEL=m
>  CONFIG_NFT_NAT=m
> -CONFIG_NFT_OBJREF=m
>  CONFIG_NFT_QUEUE=m
>  CONFIG_NFT_REJECT=m
>  CONFIG_NFT_REJECT_INET=m
> -- 
> 2.43.0
> 

> 
> 
> 



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13773): 
https://lists.yoctoproject.org/g/linux-yocto/message/13773
Mute This Topic: https://lists.yoctoproject.org/mt/105350876/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 1/1] nxp-imx9: Enable Arm ETHOS NPU

2024-04-02 Thread Xiaolei Wang via lists.yoctoproject.org
Enable Arm ETHOS NPU.

Signed-off-by: Xiaolei Wang 
---
 bsp/nxp-imx9/nxp-imx9.cfg | 5 +
 1 file changed, 5 insertions(+)

diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg
index 8ad37abb..8654f93c 100644
--- a/bsp/nxp-imx9/nxp-imx9.cfg
+++ b/bsp/nxp-imx9/nxp-imx9.cfg
@@ -284,6 +284,11 @@ CONFIG_DRM_ITE_IT6263=y
 #
 CONFIG_MXC_GPU_VIV=y
 
+#
+# Arm Ethos-U NPU
+#
+CONFIG_ETHOSU=y
+
 #
 # I2C encoder or helper chips
 #
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13767): 
https://lists.yoctoproject.org/g/linux-yocto/message/13767
Mute This Topic: https://lists.yoctoproject.org/mt/105302004/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto] [yocto-kernel-cache yocto-6.1][PATCH] Revert "features/nf_tables: nft_objref is now builtin"

2024-04-02 Thread Lyu, William via lists.yoctoproject.org
From: William Lyu 

This reverts commit dbe1767f364cdbf7dcc75433635678bd39c71e1f.

The reverted commit removes kernel configuration CONFIG_NFT_OBJREF which
became builtin starting from kernel v6.2 [1]. However, this kernel
configuration is still available in kernel v6.1. So, this kernel
configuration option should NOT be removed from "yocto-kernel-cache" on
branch "yocto-6.1".

References
[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d037abc2414b4539401e0e6aa278bedc4628ad69

Signed-off-by: William Lyu 
---
 features/nf_tables/nf_tables.cfg | 1 +
 1 file changed, 1 insertion(+)

diff --git a/features/nf_tables/nf_tables.cfg b/features/nf_tables/nf_tables.cfg
index 5b0f28df..4debc628 100644
--- a/features/nf_tables/nf_tables.cfg
+++ b/features/nf_tables/nf_tables.cfg
@@ -11,6 +11,7 @@ CONFIG_NFT_LIMIT=m
 CONFIG_NFT_CONNLIMIT=m
 CONFIG_NFT_TUNNEL=m
 CONFIG_NFT_NAT=m
+CONFIG_NFT_OBJREF=m
 CONFIG_NFT_QUEUE=m
 CONFIG_NFT_REJECT=m
 CONFIG_NFT_REJECT_INET=m
-- 
2.43.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13766): 
https://lists.yoctoproject.org/g/linux-yocto/message/13766
Mute This Topic: https://lists.yoctoproject.org/mt/105291813/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto] [yocto-kernel-cache yocto-6.4][PATCH 2/2] features/nf_tables: Add net_fib_* options for greater ptest coverage

2024-04-02 Thread Lyu, William via lists.yoctoproject.org
From: William Lyu 

Backported from commit on branch "yocto-6.6":
70cabea69443e974db04d6dcbe73031d0d726bc1

Several nftables ptest testcases failed due to missing features. The
following kernel configuration options are added as part of the missing
features:

-   NFT_FIB_INET (tristate "Netfilter nf_tables fib inet support")
This option allows using the FIB expression from the inet table.
The lookup will be delegated to the IPv4 or IPv6 FIB depending
on the protocol of the packet.

-   NFT_FIB_IPV4 (tristate "nf_tables fib / ip route lookup support")
This module enables IPv4 FIB lookups, e.g. for reverse path filtering.
It also allows query of the FIB for the route type, e.g. local, unicast,
multicast or blackhole.

-   NFT_FIB_IPV6 (tristate "nf_tables fib / ipv6 route lookup support")
This module enables IPv6 FIB lookups, e.g. for reverse path filtering.
It also allows query of the FIB for the route type, e.g. local, unicast,
multicast or blackhole.

Adding those three kernel configuration options above pass the following
ptest testcases:

-   tests/shell/testcases/parsing/large_rule_pipe
Previously failed due to using rule:
meta nfproto ipv6 fib saddr . iif oif missing drop
-   tests/shell/testcases/nft-f/sample-ruleset
Previously failed due to using rules:
fib saddr . iif oif eq 0 counter drop
fib daddr type { broadcast, multicast, anycast } counter drop
fib daddr type { broadcast, multicast, anycast } counter drop
fib daddr type { broadcast, multicast, anycast } counter drop
-   tests/shell/testcases/optimizations/ruleset
Previously failed due to using rule:
fib daddr type broadcast  drop

Signed-off-by: William Lyu 
---
 features/nf_tables/nft_test.cfg | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/features/nf_tables/nft_test.cfg b/features/nf_tables/nft_test.cfg
index fbebbaba..45ca8e5d 100644
--- a/features/nf_tables/nft_test.cfg
+++ b/features/nf_tables/nft_test.cfg
@@ -1,10 +1,12 @@
 CONFIG_NF_CONNTRACK_TIMEOUT=y
 CONFIG_NF_FLOW_TABLE_INET=m
 CONFIG_NF_FLOW_TABLE=m
+CONFIG_NFT_FIB_INET=y
+CONFIG_NFT_FIB_IPV4=y
+CONFIG_NFT_FIB_IPV6=y
 CONFIG_NFT_FLOW_OFFLOAD=m
 CONFIG_NFT_NUMGEN=m
 CONFIG_NFT_OSF=m
 CONFIG_NFT_QUOTA=m
 CONFIG_NFT_SYNPROXY=m
 CONFIG_NFT_XFRM=m
-
-- 
2.43.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13764): 
https://lists.yoctoproject.org/g/linux-yocto/message/13764
Mute This Topic: https://lists.yoctoproject.org/mt/105291635/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto] [yocto-kernel-cache yocto-6.4][PATCH 1/2] features/nf_tables: nft_objref is now builtin

2024-04-02 Thread Lyu, William via lists.yoctoproject.org
From: William Lyu 

Backported from commit on branch "yocto-6.6":
40ecdcc5e4f5053536cec6e3f74334aa418f07cc

Starting from kernel v6.2 (including all rc versions),
CONFIG_NFT_OBJREF has become builtin and cannot be disabled [1]. So,
this configure option is removed from nf_tables.cfg.

References
[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d037abc2414b4539401e0e6aa278bedc4628ad69

Signed-off-by: William Lyu 
---
 features/nf_tables/nf_tables.cfg | 1 -
 1 file changed, 1 deletion(-)

diff --git a/features/nf_tables/nf_tables.cfg b/features/nf_tables/nf_tables.cfg
index 4debc628..5b0f28df 100644
--- a/features/nf_tables/nf_tables.cfg
+++ b/features/nf_tables/nf_tables.cfg
@@ -11,7 +11,6 @@ CONFIG_NFT_LIMIT=m
 CONFIG_NFT_CONNLIMIT=m
 CONFIG_NFT_TUNNEL=m
 CONFIG_NFT_NAT=m
-CONFIG_NFT_OBJREF=m
 CONFIG_NFT_QUEUE=m
 CONFIG_NFT_REJECT=m
 CONFIG_NFT_REJECT_INET=m
-- 
2.43.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13765): 
https://lists.yoctoproject.org/g/linux-yocto/message/13765
Mute This Topic: https://lists.yoctoproject.org/mt/105291636/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto] [yocto-kernel-cache yocto-6.5][PATCH 1/2] features/nf_tables: nft_objref is now builtin

2024-04-02 Thread Lyu, William via lists.yoctoproject.org
From: William Lyu 

Backported from commit on branch "yocto-6.6":
40ecdcc5e4f5053536cec6e3f74334aa418f07cc

Starting from kernel v6.2 (including all rc versions),
CONFIG_NFT_OBJREF has become builtin and cannot be disabled [1]. So,
this configure option is removed from nf_tables.cfg.

References
[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d037abc2414b4539401e0e6aa278bedc4628ad69

Signed-off-by: William Lyu 
---
 features/nf_tables/nf_tables.cfg | 1 -
 1 file changed, 1 deletion(-)

diff --git a/features/nf_tables/nf_tables.cfg b/features/nf_tables/nf_tables.cfg
index 4debc628..5b0f28df 100644
--- a/features/nf_tables/nf_tables.cfg
+++ b/features/nf_tables/nf_tables.cfg
@@ -11,7 +11,6 @@ CONFIG_NFT_LIMIT=m
 CONFIG_NFT_CONNLIMIT=m
 CONFIG_NFT_TUNNEL=m
 CONFIG_NFT_NAT=m
-CONFIG_NFT_OBJREF=m
 CONFIG_NFT_QUEUE=m
 CONFIG_NFT_REJECT=m
 CONFIG_NFT_REJECT_INET=m
-- 
2.43.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13763): 
https://lists.yoctoproject.org/g/linux-yocto/message/13763
Mute This Topic: https://lists.yoctoproject.org/mt/105291539/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto] [yocto-kernel-cache yocto-6.5][PATCH 2/2] features/nf_tables: Add net_fib_* options for greater ptest coverage

2024-04-02 Thread Lyu, William via lists.yoctoproject.org
From: William Lyu 

Backported from commit on branch "yocto-6.6":
70cabea69443e974db04d6dcbe73031d0d726bc1

Several nftables ptest testcases failed due to missing features. The
following kernel configuration options are added as part of the missing
features:

-   NFT_FIB_INET (tristate "Netfilter nf_tables fib inet support")
This option allows using the FIB expression from the inet table.
The lookup will be delegated to the IPv4 or IPv6 FIB depending
on the protocol of the packet.

-   NFT_FIB_IPV4 (tristate "nf_tables fib / ip route lookup support")
This module enables IPv4 FIB lookups, e.g. for reverse path filtering.
It also allows query of the FIB for the route type, e.g. local, unicast,
multicast or blackhole.

-   NFT_FIB_IPV6 (tristate "nf_tables fib / ipv6 route lookup support")
This module enables IPv6 FIB lookups, e.g. for reverse path filtering.
It also allows query of the FIB for the route type, e.g. local, unicast,
multicast or blackhole.

Adding those three kernel configuration options above pass the following
ptest testcases:

-   tests/shell/testcases/parsing/large_rule_pipe
Previously failed due to using rule:
meta nfproto ipv6 fib saddr . iif oif missing drop
-   tests/shell/testcases/nft-f/sample-ruleset
Previously failed due to using rules:
fib saddr . iif oif eq 0 counter drop
fib daddr type { broadcast, multicast, anycast } counter drop
fib daddr type { broadcast, multicast, anycast } counter drop
fib daddr type { broadcast, multicast, anycast } counter drop
-   tests/shell/testcases/optimizations/ruleset
Previously failed due to using rule:
fib daddr type broadcast  drop

Signed-off-by: William Lyu 
---
 features/nf_tables/nft_test.cfg | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/features/nf_tables/nft_test.cfg b/features/nf_tables/nft_test.cfg
index fbebbaba..45ca8e5d 100644
--- a/features/nf_tables/nft_test.cfg
+++ b/features/nf_tables/nft_test.cfg
@@ -1,10 +1,12 @@
 CONFIG_NF_CONNTRACK_TIMEOUT=y
 CONFIG_NF_FLOW_TABLE_INET=m
 CONFIG_NF_FLOW_TABLE=m
+CONFIG_NFT_FIB_INET=y
+CONFIG_NFT_FIB_IPV4=y
+CONFIG_NFT_FIB_IPV6=y
 CONFIG_NFT_FLOW_OFFLOAD=m
 CONFIG_NFT_NUMGEN=m
 CONFIG_NFT_OSF=m
 CONFIG_NFT_QUOTA=m
 CONFIG_NFT_SYNPROXY=m
 CONFIG_NFT_XFRM=m
-
-- 
2.43.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13762): 
https://lists.yoctoproject.org/g/linux-yocto/message/13762
Mute This Topic: https://lists.yoctoproject.org/mt/105291538/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] yocto-patches mailing list

2024-03-28 Thread Josef Holzmayr
Hi all,

Following some discussions and suggestions to improve, the
yocto-patc...@lists.yoctoproject.org mailing list has been created. We want
to move Yocto Project-specific patches and their discussion over to that
list in order to have a clearer separation and therefore go-to address for
contributions and the corresponding discussions, as well as freeing up the
main yocto@ list for technical discussions.

Greets,
Josef
Yocto Project Community Manager

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62859): https://lists.yoctoproject.org/g/yocto/message/62859
Mute This Topic: https://lists.yoctoproject.org/mt/105204954/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto] [yocto-kernel-cache yocto-6.6][PATCH 1/2] features/nf_tables: nft_objref is now builtin

2024-03-28 Thread Bruce Ashfield
merged to 6.6 and master.

Bruce

In message: [linux-yocto] [yocto-kernel-cache yocto-6.6][PATCH 1/2] 
features/nf_tables: nft_objref is now builtin
on 27/03/2024 Lyu, William via lists.yoctoproject.org wrote:

> From: William Lyu 
> 
> Starting from kernel v6.2 (including all rc versions),
> CONFIG_NFT_OBJREF has become builtin and cannot be disabled [1]. So,
> this configure option is removed from nf_tables.cfg.
> 
> References
> [1] 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d037abc2414b4539401e0e6aa278bedc4628ad69
> 
> Signed-off-by: William Lyu 
> ---
>  features/nf_tables/nf_tables.cfg | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/features/nf_tables/nf_tables.cfg 
> b/features/nf_tables/nf_tables.cfg
> index 4debc628..5b0f28df 100644
> --- a/features/nf_tables/nf_tables.cfg
> +++ b/features/nf_tables/nf_tables.cfg
> @@ -11,7 +11,6 @@ CONFIG_NFT_LIMIT=m
>  CONFIG_NFT_CONNLIMIT=m
>  CONFIG_NFT_TUNNEL=m
>  CONFIG_NFT_NAT=m
> -CONFIG_NFT_OBJREF=m
>  CONFIG_NFT_QUEUE=m
>  CONFIG_NFT_REJECT=m
>  CONFIG_NFT_REJECT_INET=m
> -- 
> 2.43.0
> 

> 
> 
> 



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13752): 
https://lists.yoctoproject.org/g/linux-yocto/message/13752
Mute This Topic: https://lists.yoctoproject.org/mt/105198030/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [v2][linux-yocto][yocto-kernel-cache][yocto-6.1][PATCH] ti-am62: add TSN feature related kernel configs

2024-03-28 Thread Bruce Ashfield
I had a minor merge conflict with this change:

-

commit 8de3d1d2825a5d6fb30279acb583f9778c1da164
Author: Meng Li 
Date:   Thu Feb 22 22:44:26 2024 +0800

ti-am62: enable optee related kernel configs

Add optee feature and enable it in ti-am62 BSP.

Signed-off-by: Meng Li 
Signed-off-by: Bruce Ashfield 

-

but of course it was easy to resolve and this is now
merged.

Bruce

In message: [v2][linux-yocto][yocto-kernel-cache][yocto-6.1][PATCH] ti-am62: 
add TSN feature related kernel configs
on 27/03/2024 Xulin Sun wrote:

> Add TSN feature related kernel configs, and drop the duplicated
> kernel config CONFIG_NET_SCH_TAPRIO with tsn.cfg.
> 
> Signed-off-by: Xulin Sun 
> ---
>  bsp/ti-am62/ti-am62.cfg | 1 -
>  bsp/ti-am62/ti-am62.scc | 1 +
>  2 files changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/bsp/ti-am62/ti-am62.cfg b/bsp/ti-am62/ti-am62.cfg
> index fdef5c2b..2dab2c45 100755
> --- a/bsp/ti-am62/ti-am62.cfg
> +++ b/bsp/ti-am62/ti-am62.cfg
> @@ -251,7 +251,6 @@ CONFIG_TI_K3_AM65_CPSW_SWITCHDEV=y
>  CONFIG_NET_SWITCHDEV=y
>  CONFIG_TI_K3_AM65_CPTS=y
>  CONFIG_TI_AM65_CPSW_TAS=y
> -CONFIG_NET_SCH_TAPRIO=y
>  CONFIG_BRIDGE_VLAN_FILTERING=y
>  
>  #
> diff --git a/bsp/ti-am62/ti-am62.scc b/bsp/ti-am62/ti-am62.scc
> index 9a0dda7f..d8d41953 100644
> --- a/bsp/ti-am62/ti-am62.scc
> +++ b/bsp/ti-am62/ti-am62.scc
> @@ -4,5 +4,6 @@ include cfg/fs/flash_fs.cfg
>  include features/hugetlb/hugetlb.scc
>  # Enable the ability to run 32 bit apps
>  include arch/arm/32bit-compat.scc
> +include features/tsn/tsn.scc
>  
>  kconf hardware ti-am62.cfg
> -- 
> 2.34.1
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13751): 
https://lists.yoctoproject.org/g/linux-yocto/message/13751
Mute This Topic: https://lists.yoctoproject.org/mt/105173754/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto][yocto-kernel-cache][yocto-6.1][PATCH] ti-am62: add kernel configs NET_SCH_CBS & NET_SCH_MQPRIO & NET_SCH_ETF

2024-03-28 Thread Bruce Ashfield
In message: Re: [linux-yocto][yocto-kernel-cache][yocto-6.1][PATCH] ti-am62: 
add kernel configs NET_SCH_CBS & NET_SCH_MQPRIO & NET_SCH_ETF
on 27/03/2024 Kevin Hao wrote:

> On Wed, Mar 27, 2024 at 03:30:35PM +0800, Xulin Sun via 
> lists.yoctoproject.org wrote:
> > Add kernel configs NET_SCH_CBS & NET_SCH_MQPRIO & NET_SCH_ETF to support
> > AM62AX TSN feature.
> > 
> > Signed-off-by: Xulin Sun 
> > ---
> >  bsp/ti-am62/ti-am62.cfg | 3 +++
> >  1 file changed, 3 insertions(+)
> > 
> > diff --git a/bsp/ti-am62/ti-am62.cfg b/bsp/ti-am62/ti-am62.cfg
> > index fdef5c2b..537f4120 100755
> > --- a/bsp/ti-am62/ti-am62.cfg
> > +++ b/bsp/ti-am62/ti-am62.cfg
> > @@ -252,6 +252,9 @@ CONFIG_NET_SWITCHDEV=y
> >  CONFIG_TI_K3_AM65_CPTS=y
> >  CONFIG_TI_AM65_CPSW_TAS=y
> >  CONFIG_NET_SCH_TAPRIO=y
> > +CONFIG_NET_SCH_ETF=y
> > +CONFIG_NET_SCH_CBS=y
> > +CONFIG_NET_SCH_MQPRIO=y
> 
> We can use the feature/tsn.

Thanks for the review Kevin!

I'm grabbing the v2.

Bruce

> 
> Thanks,
> Kevin



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13750): 
https://lists.yoctoproject.org/g/linux-yocto/message/13750
Mute This Topic: https://lists.yoctoproject.org/mt/105173259/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 1/3] nxp-imx9: Delete IMX_SCU since imx93 does not need this driver

2024-03-28 Thread Bruce Ashfield
merged.

Bruce

In message: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 1/3] nxp-imx9: 
Delete IMX_SCU since imx93 does not need this driver
on 26/03/2024 Xiaolei Wang wrote:

> IMX_SCU is specific on imx8, so remove it to avoid warnings
> 
> [NOTE]: 'CONFIG_PINCTRL_IMX_SCU' last val (y) and .config val (n) do not match
> [INFO]: CONFIG_PINCTRL_IMX_SCU : n
> [INFO]: raw config text:
> 
> config PINCTRL_IMX_SCU
>   tristate
>   select PINCTRL_IMX
>   depends on IMX_SCU && PINCTRL
> 
> Config 'PINCTRL_IMX_SCU' has the following Direct dependencies 
> (PINCTRL_IMX_SCU=y):
> IMX_SCU(=y) && PINCTRL(=y)
> Parent dependencies are:
>  PINCTRL [y] IMX_SCU [y]
> [INFO]: config 'CONFIG_PINCTRL_IMX_SCU' was set, but it wasn't 
> assignable, check (parent) dependencies
> 
> [INFO]: selection details for 'CONFIG_PINCTRL_IMX_SCU':
> Symbols currently n-selecting this symbol (no effect):
>   - PINCTRL_IMX8QM
>   - PINCTRL_IMX8QXP
>   - PINCTRL_IMX8DXL
> 
> Signed-off-by: Xiaolei Wang 
> ---
>  bsp/nxp-imx9/nxp-imx9.cfg | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg
> index 41964ea5..29c3b8e3 100644
> --- a/bsp/nxp-imx9/nxp-imx9.cfg
> +++ b/bsp/nxp-imx9/nxp-imx9.cfg
> @@ -164,7 +164,6 @@ CONFIG_SPI_SLAVE=y
>  CONFIG_PINCTRL=y
>  CONFIG_GPIOLIB=y
>  CONFIG_PINCTRL_IMX=y
> -CONFIG_PINCTRL_IMX_SCU=y
>  CONFIG_PINCTRL_IMX93=y
>  CONFIG_GPIO_MAX732X=y
>  CONFIG_GPIO_PCA953X=y
> -- 
> 2.25.1
> 

In message: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 3/3] nxp-imx9: 
Delete MXC_CLK_SCU since imx93 does not need this driver
on 26/03/2024 Xiaolei Wang wrote:

> MXC_CLK_SCU is specific on imx8, so remove it to avoid warnings
> 
> [NOTE]: 'CONFIG_MXC_CLK_SCU' last val (y) and .config val (n) do not match
> [INFO]: CONFIG_MXC_CLK_SCU : n
> [INFO]: raw config text:
> 
> config MXC_CLK_SCU
>   tristate
>   depends on COMMON_CLK
> 
> Config 'MXC_CLK_SCU' has the following Direct dependencies 
> (MXC_CLK_SCU=y):
> COMMON_CLK(=y)
> Parent dependencies are:
>  COMMON_CLK [y]
> [INFO]: config 'CONFIG_MXC_CLK_SCU' was set, but it wasn't assignable, 
> check (parent) dependencies
> 
> [INFO]: selection details for 'CONFIG_MXC_CLK_SCU':
> Symbols currently n-selecting this symbol (no effect):
>   - CLK_IMX8QXP
> 
> Signed-off-by: Xiaolei Wang 
> ---
>  bsp/nxp-imx9/nxp-imx9.cfg | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg
> index c034cb5c..8ad37abb 100644
> --- a/bsp/nxp-imx9/nxp-imx9.cfg
> +++ b/bsp/nxp-imx9/nxp-imx9.cfg
> @@ -511,7 +511,6 @@ CONFIG_DMABUF_HEAPS_DSP=y
>  # Clock driver for ARM Reference designs
>  #
>  CONFIG_MXC_CLK=y
> -CONFIG_MXC_CLK_SCU=y
>  CONFIG_CLK_IMX93=y
>  
>  #
> -- 
> 2.25.1
> 

In message: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 2/3] nxp-imx9: 
Enable NET_DSA for nxp-imx9
on 26/03/2024 Xiaolei Wang wrote:

> Enable NET_DSA for nxp-imx9.
> 
> Signed-off-by: Xiaolei Wang 
> ---
>  bsp/nxp-imx9/nxp-imx9.cfg | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg
> index 29c3b8e3..c034cb5c 100644
> --- a/bsp/nxp-imx9/nxp-imx9.cfg
> +++ b/bsp/nxp-imx9/nxp-imx9.cfg
> @@ -113,6 +113,7 @@ CONFIG_AT803X_PHY=y
>  CONFIG_REALTEK_PHY=y
>  CONFIG_STMMAC_ETH=y
>  CONFIG_FEC_ECAT=y
> +CONFIG_NET_DSA=m
>  CONFIG_NET_DSA_NETC=m
>  CONFIG_NET_DSA_SJA1105=m
>  CONFIG_NET_DSA_SJA1105_PTP=y
> -- 
> 2.25.1
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13749): 
https://lists.yoctoproject.org/g/linux-yocto/message/13749
Mute This Topic: https://lists.yoctoproject.org/mt/105197672/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] [yocto-autobuilder2][PATCH] schedulers: ensure correct branch is used for meta-exein for nanbield

2024-03-27 Thread Alexandre Belloni via lists.yoctoproject.org
From: Alexandre Belloni 

Signed-off-by: Alexandre Belloni 
---
 schedulers.py | 1 +
 1 file changed, 1 insertion(+)

diff --git a/schedulers.py b/schedulers.py
index a30383f255a1..47eedde016cf 100644
--- a/schedulers.py
+++ b/schedulers.py
@@ -91,6 +91,7 @@ branchdefaults = {
 'branch_meta-openembedded': 'nanbield',
 'branch_meta-ti': 'master',
 'branch_meta-virtualization': 'nanbield',
+'branch_meta-exein': 'nanbield',
 'branch_oecore': 'nanbield',
 },
 'mickledore': {
-- 
2.44.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62852): https://lists.yoctoproject.org/g/yocto/message/62852
Mute This Topic: https://lists.yoctoproject.org/mt/105183590/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto] [yocto-kernel-cache yocto-6.6][PATCH 2/2] features/nf_tables: Add net_fib_* options for greater ptest coverage

2024-03-27 Thread Lyu, William via lists.yoctoproject.org
From: William Lyu 

Several nftables ptest testcases failed due to missing features. The
following kernel configuration options are added as part of the missing
features:

-   NFT_FIB_INET (tristate "Netfilter nf_tables fib inet support")
This option allows using the FIB expression from the inet table.
The lookup will be delegated to the IPv4 or IPv6 FIB depending
on the protocol of the packet.

-   NFT_FIB_IPV4 (tristate "nf_tables fib / ip route lookup support")
This module enables IPv4 FIB lookups, e.g. for reverse path filtering.
It also allows query of the FIB for the route type, e.g. local, unicast,
multicast or blackhole.

-   NFT_FIB_IPV6 (tristate "nf_tables fib / ipv6 route lookup support")
This module enables IPv6 FIB lookups, e.g. for reverse path filtering.
It also allows query of the FIB for the route type, e.g. local, unicast,
multicast or blackhole.

Adding those three kernel configuration options above pass the following
ptest testcases:

-   tests/shell/testcases/parsing/large_rule_pipe
Previously failed due to using rule:
meta nfproto ipv6 fib saddr . iif oif missing drop
-   tests/shell/testcases/nft-f/sample-ruleset
Previously failed due to using rules:
fib saddr . iif oif eq 0 counter drop
fib daddr type { broadcast, multicast, anycast } counter drop
fib daddr type { broadcast, multicast, anycast } counter drop
fib daddr type { broadcast, multicast, anycast } counter drop
-   tests/shell/testcases/optimizations/ruleset
Previously failed due to using rule:
fib daddr type broadcast  drop

Signed-off-by: William Lyu 
---
 features/nf_tables/nft_test.cfg | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/features/nf_tables/nft_test.cfg b/features/nf_tables/nft_test.cfg
index fbebbaba..45ca8e5d 100644
--- a/features/nf_tables/nft_test.cfg
+++ b/features/nf_tables/nft_test.cfg
@@ -1,10 +1,12 @@
 CONFIG_NF_CONNTRACK_TIMEOUT=y
 CONFIG_NF_FLOW_TABLE_INET=m
 CONFIG_NF_FLOW_TABLE=m
+CONFIG_NFT_FIB_INET=y
+CONFIG_NFT_FIB_IPV4=y
+CONFIG_NFT_FIB_IPV6=y
 CONFIG_NFT_FLOW_OFFLOAD=m
 CONFIG_NFT_NUMGEN=m
 CONFIG_NFT_OSF=m
 CONFIG_NFT_QUOTA=m
 CONFIG_NFT_SYNPROXY=m
 CONFIG_NFT_XFRM=m
-
-- 
2.43.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13742): 
https://lists.yoctoproject.org/g/linux-yocto/message/13742
Mute This Topic: https://lists.yoctoproject.org/mt/105179815/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto] [yocto-kernel-cache yocto-6.6][PATCH 1/2] features/nf_tables: nft_objref is now builtin

2024-03-27 Thread Lyu, William via lists.yoctoproject.org
From: William Lyu 

Starting from kernel v6.2 (including all rc versions),
CONFIG_NFT_OBJREF has become builtin and cannot be disabled [1]. So,
this configure option is removed from nf_tables.cfg.

References
[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d037abc2414b4539401e0e6aa278bedc4628ad69

Signed-off-by: William Lyu 
---
 features/nf_tables/nf_tables.cfg | 1 -
 1 file changed, 1 deletion(-)

diff --git a/features/nf_tables/nf_tables.cfg b/features/nf_tables/nf_tables.cfg
index 4debc628..5b0f28df 100644
--- a/features/nf_tables/nf_tables.cfg
+++ b/features/nf_tables/nf_tables.cfg
@@ -11,7 +11,6 @@ CONFIG_NFT_LIMIT=m
 CONFIG_NFT_CONNLIMIT=m
 CONFIG_NFT_TUNNEL=m
 CONFIG_NFT_NAT=m
-CONFIG_NFT_OBJREF=m
 CONFIG_NFT_QUEUE=m
 CONFIG_NFT_REJECT=m
 CONFIG_NFT_REJECT_INET=m
-- 
2.43.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13741): 
https://lists.yoctoproject.org/g/linux-yocto/message/13741
Mute This Topic: https://lists.yoctoproject.org/mt/105179813/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[v2][linux-yocto][yocto-kernel-cache][yocto-6.1][PATCH] ti-am62: add TSN feature related kernel configs

2024-03-27 Thread Xulin Sun via lists.yoctoproject.org
Add TSN feature related kernel configs, and drop the duplicated
kernel config CONFIG_NET_SCH_TAPRIO with tsn.cfg.

Signed-off-by: Xulin Sun 
---
 bsp/ti-am62/ti-am62.cfg | 1 -
 bsp/ti-am62/ti-am62.scc | 1 +
 2 files changed, 1 insertion(+), 1 deletion(-)

diff --git a/bsp/ti-am62/ti-am62.cfg b/bsp/ti-am62/ti-am62.cfg
index fdef5c2b..2dab2c45 100755
--- a/bsp/ti-am62/ti-am62.cfg
+++ b/bsp/ti-am62/ti-am62.cfg
@@ -251,7 +251,6 @@ CONFIG_TI_K3_AM65_CPSW_SWITCHDEV=y
 CONFIG_NET_SWITCHDEV=y
 CONFIG_TI_K3_AM65_CPTS=y
 CONFIG_TI_AM65_CPSW_TAS=y
-CONFIG_NET_SCH_TAPRIO=y
 CONFIG_BRIDGE_VLAN_FILTERING=y
 
 #
diff --git a/bsp/ti-am62/ti-am62.scc b/bsp/ti-am62/ti-am62.scc
index 9a0dda7f..d8d41953 100644
--- a/bsp/ti-am62/ti-am62.scc
+++ b/bsp/ti-am62/ti-am62.scc
@@ -4,5 +4,6 @@ include cfg/fs/flash_fs.cfg
 include features/hugetlb/hugetlb.scc
 # Enable the ability to run 32 bit apps
 include arch/arm/32bit-compat.scc
+include features/tsn/tsn.scc
 
 kconf hardware ti-am62.cfg
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13736): 
https://lists.yoctoproject.org/g/linux-yocto/message/13736
Mute This Topic: https://lists.yoctoproject.org/mt/105173754/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto][yocto-kernel-cache][yocto-6.1][PATCH] ti-am62: add kernel configs NET_SCH_CBS & NET_SCH_MQPRIO & NET_SCH_ETF

2024-03-27 Thread Kevin Hao
On Wed, Mar 27, 2024 at 03:30:35PM +0800, Xulin Sun via lists.yoctoproject.org 
wrote:
> Add kernel configs NET_SCH_CBS & NET_SCH_MQPRIO & NET_SCH_ETF to support
> AM62AX TSN feature.
> 
> Signed-off-by: Xulin Sun 
> ---
>  bsp/ti-am62/ti-am62.cfg | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/bsp/ti-am62/ti-am62.cfg b/bsp/ti-am62/ti-am62.cfg
> index fdef5c2b..537f4120 100755
> --- a/bsp/ti-am62/ti-am62.cfg
> +++ b/bsp/ti-am62/ti-am62.cfg
> @@ -252,6 +252,9 @@ CONFIG_NET_SWITCHDEV=y
>  CONFIG_TI_K3_AM65_CPTS=y
>  CONFIG_TI_AM65_CPSW_TAS=y
>  CONFIG_NET_SCH_TAPRIO=y
> +CONFIG_NET_SCH_ETF=y
> +CONFIG_NET_SCH_CBS=y
> +CONFIG_NET_SCH_MQPRIO=y

We can use the feature/tsn.

Thanks,
Kevin


signature.asc
Description: PGP signature

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13735): 
https://lists.yoctoproject.org/g/linux-yocto/message/13735
Mute This Topic: https://lists.yoctoproject.org/mt/105173259/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][yocto-kernel-cache][yocto-6.1][PATCH] ti-am62: add kernel configs NET_SCH_CBS & NET_SCH_MQPRIO & NET_SCH_ETF

2024-03-27 Thread Xulin Sun via lists.yoctoproject.org
Add kernel configs NET_SCH_CBS & NET_SCH_MQPRIO & NET_SCH_ETF to support
AM62AX TSN feature.

Signed-off-by: Xulin Sun 
---
 bsp/ti-am62/ti-am62.cfg | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/bsp/ti-am62/ti-am62.cfg b/bsp/ti-am62/ti-am62.cfg
index fdef5c2b..537f4120 100755
--- a/bsp/ti-am62/ti-am62.cfg
+++ b/bsp/ti-am62/ti-am62.cfg
@@ -252,6 +252,9 @@ CONFIG_NET_SWITCHDEV=y
 CONFIG_TI_K3_AM65_CPTS=y
 CONFIG_TI_AM65_CPSW_TAS=y
 CONFIG_NET_SCH_TAPRIO=y
+CONFIG_NET_SCH_ETF=y
+CONFIG_NET_SCH_CBS=y
+CONFIG_NET_SCH_MQPRIO=y
 CONFIG_BRIDGE_VLAN_FILTERING=y
 
 #
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13734): 
https://lists.yoctoproject.org/g/linux-yocto/message/13734
Mute This Topic: https://lists.yoctoproject.org/mt/105173259/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 2/3] nxp-imx9: Enable NET_DSA for nxp-imx9

2024-03-26 Thread Xiaolei Wang via lists.yoctoproject.org
Enable NET_DSA for nxp-imx9.

Signed-off-by: Xiaolei Wang 
---
 bsp/nxp-imx9/nxp-imx9.cfg | 1 +
 1 file changed, 1 insertion(+)

diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg
index 29c3b8e3..c034cb5c 100644
--- a/bsp/nxp-imx9/nxp-imx9.cfg
+++ b/bsp/nxp-imx9/nxp-imx9.cfg
@@ -113,6 +113,7 @@ CONFIG_AT803X_PHY=y
 CONFIG_REALTEK_PHY=y
 CONFIG_STMMAC_ETH=y
 CONFIG_FEC_ECAT=y
+CONFIG_NET_DSA=m
 CONFIG_NET_DSA_NETC=m
 CONFIG_NET_DSA_SJA1105=m
 CONFIG_NET_DSA_SJA1105_PTP=y
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13732): 
https://lists.yoctoproject.org/g/linux-yocto/message/13732
Mute This Topic: https://lists.yoctoproject.org/mt/105158063/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 3/3] nxp-imx9: Delete MXC_CLK_SCU since imx93 does not need this driver

2024-03-26 Thread Xiaolei Wang via lists.yoctoproject.org
MXC_CLK_SCU is specific on imx8, so remove it to avoid warnings

[NOTE]: 'CONFIG_MXC_CLK_SCU' last val (y) and .config val (n) do not match
[INFO]: CONFIG_MXC_CLK_SCU : n
[INFO]: raw config text:

config MXC_CLK_SCU
tristate
depends on COMMON_CLK

Config 'MXC_CLK_SCU' has the following Direct dependencies 
(MXC_CLK_SCU=y):
COMMON_CLK(=y)
Parent dependencies are:
 COMMON_CLK [y]
[INFO]: config 'CONFIG_MXC_CLK_SCU' was set, but it wasn't assignable, 
check (parent) dependencies

[INFO]: selection details for 'CONFIG_MXC_CLK_SCU':
Symbols currently n-selecting this symbol (no effect):
  - CLK_IMX8QXP

Signed-off-by: Xiaolei Wang 
---
 bsp/nxp-imx9/nxp-imx9.cfg | 1 -
 1 file changed, 1 deletion(-)

diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg
index c034cb5c..8ad37abb 100644
--- a/bsp/nxp-imx9/nxp-imx9.cfg
+++ b/bsp/nxp-imx9/nxp-imx9.cfg
@@ -511,7 +511,6 @@ CONFIG_DMABUF_HEAPS_DSP=y
 # Clock driver for ARM Reference designs
 #
 CONFIG_MXC_CLK=y
-CONFIG_MXC_CLK_SCU=y
 CONFIG_CLK_IMX93=y
 
 #
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13733): 
https://lists.yoctoproject.org/g/linux-yocto/message/13733
Mute This Topic: https://lists.yoctoproject.org/mt/105158064/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 1/3] nxp-imx9: Delete IMX_SCU since imx93 does not need this driver

2024-03-26 Thread Xiaolei Wang via lists.yoctoproject.org
IMX_SCU is specific on imx8, so remove it to avoid warnings

[NOTE]: 'CONFIG_PINCTRL_IMX_SCU' last val (y) and .config val (n) do not match
[INFO]: CONFIG_PINCTRL_IMX_SCU : n
[INFO]: raw config text:

config PINCTRL_IMX_SCU
tristate
select PINCTRL_IMX
depends on IMX_SCU && PINCTRL

Config 'PINCTRL_IMX_SCU' has the following Direct dependencies 
(PINCTRL_IMX_SCU=y):
IMX_SCU(=y) && PINCTRL(=y)
Parent dependencies are:
 PINCTRL [y] IMX_SCU [y]
[INFO]: config 'CONFIG_PINCTRL_IMX_SCU' was set, but it wasn't assignable, 
check (parent) dependencies

[INFO]: selection details for 'CONFIG_PINCTRL_IMX_SCU':
Symbols currently n-selecting this symbol (no effect):
  - PINCTRL_IMX8QM
  - PINCTRL_IMX8QXP
  - PINCTRL_IMX8DXL

Signed-off-by: Xiaolei Wang 
---
 bsp/nxp-imx9/nxp-imx9.cfg | 1 -
 1 file changed, 1 deletion(-)

diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg
index 41964ea5..29c3b8e3 100644
--- a/bsp/nxp-imx9/nxp-imx9.cfg
+++ b/bsp/nxp-imx9/nxp-imx9.cfg
@@ -164,7 +164,6 @@ CONFIG_SPI_SLAVE=y
 CONFIG_PINCTRL=y
 CONFIG_GPIOLIB=y
 CONFIG_PINCTRL_IMX=y
-CONFIG_PINCTRL_IMX_SCU=y
 CONFIG_PINCTRL_IMX93=y
 CONFIG_GPIO_MAX732X=y
 CONFIG_GPIO_PCA953X=y
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13731): 
https://lists.yoctoproject.org/g/linux-yocto/message/13731
Mute This Topic: https://lists.yoctoproject.org/mt/105158062/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 1/3] features/net: Add xdp feature config

2024-03-21 Thread Bruce Ashfield
All three are merged to yocto-6.1, the net features are
also on 6.6 and master.

Bruce

In message: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 1/3] 
features/net: Add xdp feature config
on 21/03/2024 Xiaolei Wang wrote:

> Add xdp feature config.
> 
> Signed-off-by: Xiaolei Wang 
> ---
>  features/net/xdp/xdp.cfg | 1 +
>  features/net/xdp/xdp.scc | 1 +
>  2 files changed, 2 insertions(+)
>  create mode 100644 features/net/xdp/xdp.cfg
>  create mode 100644 features/net/xdp/xdp.scc
> 
> diff --git a/features/net/xdp/xdp.cfg b/features/net/xdp/xdp.cfg
> new file mode 100644
> index ..061b65a4
> --- /dev/null
> +++ b/features/net/xdp/xdp.cfg
> @@ -0,0 +1 @@
> +CONFIG_XDP_SOCKETS=y
> diff --git a/features/net/xdp/xdp.scc b/features/net/xdp/xdp.scc
> new file mode 100644
> index ..e4df6d09
> --- /dev/null
> +++ b/features/net/xdp/xdp.scc
> @@ -0,0 +1 @@
> +kconf hardware xdp.cfg
> -- 
> 2.25.1
> 

In message: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 2/3] 
features/net_sched: Add MULTIQ and NET_EMATCH config
on 21/03/2024 Xiaolei Wang wrote:

> Add MULTIQ and NET_EMATCH config.
> 
> Signed-off-by: Xiaolei Wang 
> ---
>  features/net_sched/net_sched.cfg | 5 +
>  1 file changed, 5 insertions(+)
> 
> diff --git a/features/net_sched/net_sched.cfg 
> b/features/net_sched/net_sched.cfg
> index d0473170..137ca752 100644
> --- a/features/net_sched/net_sched.cfg
> +++ b/features/net_sched/net_sched.cfg
> @@ -20,6 +20,8 @@ CONFIG_NET_SCH_INGRESS=m
>  CONFIG_NET_SCH_CODEL=m
>  CONFIG_NET_SCH_FQ_CODEL=m
>  
> +CONFIG_NET_SCH_MULTIQ=m
> +
>  #
>  # Classification
>  #
> @@ -31,3 +33,6 @@ CONFIG_NET_CLS_U32=y
>  CONFIG_NET_ACT_MIRRED=m
>  CONFIG_NET_ACT_SKBEDIT=m
>  CONFIG_NET_EMATCH=y
> +
> +CONFIG_NET_EMATCH_U32=y
> +CONFIG_NET_EMATCH_META=y
> -- 
> 2.25.1
> 

In message: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 3/3] nxp-imx9: 
Add some related net config required by tsn
on 21/03/2024 Xiaolei Wang wrote:

> Add some related net config required by tsn.
> 
> Signed-off-by: Xiaolei Wang 
> ---
>  bsp/nxp-imx9/nxp-imx9-preempt-rt.scc | 2 ++
>  bsp/nxp-imx9/nxp-imx9-standard.scc   | 2 ++
>  bsp/nxp-imx9/nxp-imx9.cfg| 6 ++
>  3 files changed, 10 insertions(+)
> 
> diff --git a/bsp/nxp-imx9/nxp-imx9-preempt-rt.scc 
> b/bsp/nxp-imx9/nxp-imx9-preempt-rt.scc
> index 57ce73f9..737fdeab 100644
> --- a/bsp/nxp-imx9/nxp-imx9-preempt-rt.scc
> +++ b/bsp/nxp-imx9/nxp-imx9-preempt-rt.scc
> @@ -3,6 +3,8 @@ define KTYPE preempt-rt
>  define KARCH arm64
>  
>  include ktypes/preempt-rt
> +include features/tsn/tsn.scc
> +include features/net/xdp/xdp.scc
>  
>  include nxp-imx9.scc
>  
> diff --git a/bsp/nxp-imx9/nxp-imx9-standard.scc 
> b/bsp/nxp-imx9/nxp-imx9-standard.scc
> index 4483215c..1e6e9eea 100644
> --- a/bsp/nxp-imx9/nxp-imx9-standard.scc
> +++ b/bsp/nxp-imx9/nxp-imx9-standard.scc
> @@ -3,5 +3,7 @@ define KTYPE standard
>  define KARCH arm64
>  
>  include ktypes/standard
> +include features/tsn/tsn.scc
> +include features/net/xdp/xdp.scc
>  
>  include nxp-imx9.scc
> diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg
> index 499b0750..41964ea5 100644
> --- a/bsp/nxp-imx9/nxp-imx9.cfg
> +++ b/bsp/nxp-imx9/nxp-imx9.cfg
> @@ -112,6 +112,12 @@ CONFIG_FEC=y
>  CONFIG_AT803X_PHY=y
>  CONFIG_REALTEK_PHY=y
>  CONFIG_STMMAC_ETH=y
> +CONFIG_FEC_ECAT=y
> +CONFIG_NET_DSA_NETC=m
> +CONFIG_NET_DSA_SJA1105=m
> +CONFIG_NET_DSA_SJA1105_PTP=y
> +CONFIG_NET_DSA_SJA1105_TAS=y
> +CONFIG_NET_DSA_SJA1105_VL=y
>  
>  #
>  # Input device support
> -- 
> 2.25.1
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13719): 
https://lists.yoctoproject.org/g/linux-yocto/message/13719
Mute This Topic: https://lists.yoctoproject.org/mt/105076207/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 2/3] features/net_sched: Add MULTIQ and NET_EMATCH config

2024-03-21 Thread Xiaolei Wang via lists.yoctoproject.org
Add MULTIQ and NET_EMATCH config.

Signed-off-by: Xiaolei Wang 
---
 features/net_sched/net_sched.cfg | 5 +
 1 file changed, 5 insertions(+)

diff --git a/features/net_sched/net_sched.cfg b/features/net_sched/net_sched.cfg
index d0473170..137ca752 100644
--- a/features/net_sched/net_sched.cfg
+++ b/features/net_sched/net_sched.cfg
@@ -20,6 +20,8 @@ CONFIG_NET_SCH_INGRESS=m
 CONFIG_NET_SCH_CODEL=m
 CONFIG_NET_SCH_FQ_CODEL=m
 
+CONFIG_NET_SCH_MULTIQ=m
+
 #
 # Classification
 #
@@ -31,3 +33,6 @@ CONFIG_NET_CLS_U32=y
 CONFIG_NET_ACT_MIRRED=m
 CONFIG_NET_ACT_SKBEDIT=m
 CONFIG_NET_EMATCH=y
+
+CONFIG_NET_EMATCH_U32=y
+CONFIG_NET_EMATCH_META=y
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13716): 
https://lists.yoctoproject.org/g/linux-yocto/message/13716
Mute This Topic: https://lists.yoctoproject.org/mt/105060995/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 1/3] features/net: Add xdp feature config

2024-03-21 Thread Xiaolei Wang via lists.yoctoproject.org
Add xdp feature config.

Signed-off-by: Xiaolei Wang 
---
 features/net/xdp/xdp.cfg | 1 +
 features/net/xdp/xdp.scc | 1 +
 2 files changed, 2 insertions(+)
 create mode 100644 features/net/xdp/xdp.cfg
 create mode 100644 features/net/xdp/xdp.scc

diff --git a/features/net/xdp/xdp.cfg b/features/net/xdp/xdp.cfg
new file mode 100644
index ..061b65a4
--- /dev/null
+++ b/features/net/xdp/xdp.cfg
@@ -0,0 +1 @@
+CONFIG_XDP_SOCKETS=y
diff --git a/features/net/xdp/xdp.scc b/features/net/xdp/xdp.scc
new file mode 100644
index ..e4df6d09
--- /dev/null
+++ b/features/net/xdp/xdp.scc
@@ -0,0 +1 @@
+kconf hardware xdp.cfg
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13717): 
https://lists.yoctoproject.org/g/linux-yocto/message/13717
Mute This Topic: https://lists.yoctoproject.org/mt/105060996/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 3/3] nxp-imx9: Add some related net config required by tsn

2024-03-21 Thread Xiaolei Wang via lists.yoctoproject.org
Add some related net config required by tsn.

Signed-off-by: Xiaolei Wang 
---
 bsp/nxp-imx9/nxp-imx9-preempt-rt.scc | 2 ++
 bsp/nxp-imx9/nxp-imx9-standard.scc   | 2 ++
 bsp/nxp-imx9/nxp-imx9.cfg| 6 ++
 3 files changed, 10 insertions(+)

diff --git a/bsp/nxp-imx9/nxp-imx9-preempt-rt.scc 
b/bsp/nxp-imx9/nxp-imx9-preempt-rt.scc
index 57ce73f9..737fdeab 100644
--- a/bsp/nxp-imx9/nxp-imx9-preempt-rt.scc
+++ b/bsp/nxp-imx9/nxp-imx9-preempt-rt.scc
@@ -3,6 +3,8 @@ define KTYPE preempt-rt
 define KARCH arm64
 
 include ktypes/preempt-rt
+include features/tsn/tsn.scc
+include features/net/xdp/xdp.scc
 
 include nxp-imx9.scc
 
diff --git a/bsp/nxp-imx9/nxp-imx9-standard.scc 
b/bsp/nxp-imx9/nxp-imx9-standard.scc
index 4483215c..1e6e9eea 100644
--- a/bsp/nxp-imx9/nxp-imx9-standard.scc
+++ b/bsp/nxp-imx9/nxp-imx9-standard.scc
@@ -3,5 +3,7 @@ define KTYPE standard
 define KARCH arm64
 
 include ktypes/standard
+include features/tsn/tsn.scc
+include features/net/xdp/xdp.scc
 
 include nxp-imx9.scc
diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg
index 499b0750..41964ea5 100644
--- a/bsp/nxp-imx9/nxp-imx9.cfg
+++ b/bsp/nxp-imx9/nxp-imx9.cfg
@@ -112,6 +112,12 @@ CONFIG_FEC=y
 CONFIG_AT803X_PHY=y
 CONFIG_REALTEK_PHY=y
 CONFIG_STMMAC_ETH=y
+CONFIG_FEC_ECAT=y
+CONFIG_NET_DSA_NETC=m
+CONFIG_NET_DSA_SJA1105=m
+CONFIG_NET_DSA_SJA1105_PTP=y
+CONFIG_NET_DSA_SJA1105_TAS=y
+CONFIG_NET_DSA_SJA1105_VL=y
 
 #
 # Input device support
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13718): 
https://lists.yoctoproject.org/g/linux-yocto/message/13718
Mute This Topic: https://lists.yoctoproject.org/mt/105060997/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto][yocto-kernel-cache][master/yocto-6.6][PATCH 1/3] features/vfio: remove CONFIG_VFIO_VIRQFD

2024-03-19 Thread Bruce Ashfield
All three are applied.

Bruce

In message: [linux-yocto][yocto-kernel-cache][master/yocto-6.6][PATCH 1/3] 
features/vfio: remove CONFIG_VFIO_VIRQFD
on 18/03/2024 Yongxin Liu wrote:

> CONFIG_VFIO_VIRQFD was changed to bool in kernel commit
> e2d55709398e ("vfio: Fold vfio_virqfd.ko into vfio.ko") and
> it is not user selectable.
> 
> Signed-off-by: Yongxin Liu 
> ---
>  features/vfio/vfio.cfg | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/features/vfio/vfio.cfg b/features/vfio/vfio.cfg
> index 96c9208e..2a38f6d9 100644
> --- a/features/vfio/vfio.cfg
> +++ b/features/vfio/vfio.cfg
> @@ -1,6 +1,5 @@
>  # SPDX-License-Identifier: MIT
>  CONFIG_VFIO_IOMMU_TYPE1=m
> -CONFIG_VFIO_VIRQFD=m
>  CONFIG_VFIO=m
>  CONFIG_VFIO_PCI=m
>  CONFIG_VFIO_PCI_VGA=y
> -- 
> 2.43.2
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13700): 
https://lists.yoctoproject.org/g/linux-yocto/message/13700
Mute This Topic: https://lists.yoctoproject.org/mt/105000432/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto][yocto-kernel-cache][master/yocto-6.6][PATCH] bsp/intel-x86: remove intel-x86-64-preempt-rt.cfg in scc file

2024-03-19 Thread Bruce Ashfield
merged.

Bruce

In message: [linux-yocto][yocto-kernel-cache][master/yocto-6.6][PATCH] 
bsp/intel-x86: remove intel-x86-64-preempt-rt.cfg in scc file
on 18/03/2024 Yongxin Liu wrote:

> intel-x86-64-preempt-rt.cfg was removed in commit bd20a636b044
> ("config: remove mis-located configuration fragment").
> 
> Signed-off-by: Yongxin Liu 
> ---
>  bsp/intel-x86/intel-x86-64-preempt-rt.scc | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/bsp/intel-x86/intel-x86-64-preempt-rt.scc 
> b/bsp/intel-x86/intel-x86-64-preempt-rt.scc
> index 63d517ec..e776cfa9 100644
> --- a/bsp/intel-x86/intel-x86-64-preempt-rt.scc
> +++ b/bsp/intel-x86/intel-x86-64-preempt-rt.scc
> @@ -8,4 +8,3 @@ include ktypes/preempt-rt
>  include intel-x86-64.scc
>  include features/tsn/tsn.scc
>  kconf hardware cfs-bandwidth.cfg
> -kconf hardware intel-x86-64-preempt-rt.cfg
> -- 
> 2.43.2
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13699): 
https://lists.yoctoproject.org/g/linux-yocto/message/13699
Mute This Topic: https://lists.yoctoproject.org/mt/104997867/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][yocto-kernel-cache][master/yocto-6.6][PATCH 1/3] features/vfio: remove CONFIG_VFIO_VIRQFD

2024-03-18 Thread Yongxin Liu via lists.yoctoproject.org
CONFIG_VFIO_VIRQFD was changed to bool in kernel commit
e2d55709398e ("vfio: Fold vfio_virqfd.ko into vfio.ko") and
it is not user selectable.

Signed-off-by: Yongxin Liu 
---
 features/vfio/vfio.cfg | 1 -
 1 file changed, 1 deletion(-)

diff --git a/features/vfio/vfio.cfg b/features/vfio/vfio.cfg
index 96c9208e..2a38f6d9 100644
--- a/features/vfio/vfio.cfg
+++ b/features/vfio/vfio.cfg
@@ -1,6 +1,5 @@
 # SPDX-License-Identifier: MIT
 CONFIG_VFIO_IOMMU_TYPE1=m
-CONFIG_VFIO_VIRQFD=m
 CONFIG_VFIO=m
 CONFIG_VFIO_PCI=m
 CONFIG_VFIO_PCI_VGA=y
-- 
2.43.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13692): 
https://lists.yoctoproject.org/g/linux-yocto/message/13692
Mute This Topic: https://lists.yoctoproject.org/mt/105000432/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][yocto-kernel-cache][master/yocto-6.6][PATCH 2/3] features/vfio: remove CONFIG_VFIO_MDEV

2024-03-18 Thread Yongxin Liu via lists.yoctoproject.org
CONFIG_VFIO_MDEV wasn't a user choice after kerne commit
8bf8c5ee1f38 ("vfio-mdev: turn VFIO_MDEV into a selectable symbol").

Signed-off-by: Yongxin Liu 
---
 features/vfio/vfio.cfg | 1 -
 1 file changed, 1 deletion(-)

diff --git a/features/vfio/vfio.cfg b/features/vfio/vfio.cfg
index 2a38f6d9..94991365 100644
--- a/features/vfio/vfio.cfg
+++ b/features/vfio/vfio.cfg
@@ -6,4 +6,3 @@ CONFIG_VFIO_PCI_VGA=y
 CONFIG_VFIO_PCI_MMAP=y
 CONFIG_VFIO_PCI_INTX=y
 CONFIG_VIRT_DRIVERS=y
-CONFIG_VFIO_MDEV=m
-- 
2.43.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13693): 
https://lists.yoctoproject.org/g/linux-yocto/message/13693
Mute This Topic: https://lists.yoctoproject.org/mt/105000433/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][yocto-kernel-cache][master/yocto-6.6][PATCH 3/3] bsp/intel-x86: remove CONFIG_IXGB

2024-03-18 Thread Yongxin Liu via lists.yoctoproject.org
ixgb driver was removed in kernel commit e485f3a6eae0
("ixgb: Remove ixgb driver").

Signed-off-by: Yongxin Liu 
---
 bsp/intel-x86/intel-x86.cfg | 5 -
 1 file changed, 5 deletions(-)

diff --git a/bsp/intel-x86/intel-x86.cfg b/bsp/intel-x86/intel-x86.cfg
index ee01e61e..8266bf8f 100644
--- a/bsp/intel-x86/intel-x86.cfg
+++ b/bsp/intel-x86/intel-x86.cfg
@@ -153,11 +153,6 @@ CONFIG_HOSTAP=y
 #
 CONFIG_RTL8723BE=m
 
-#
-# Intel devices
-#
-CONFIG_IXGB=y
-
 #
 # nvram support
 #
-- 
2.43.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13694): 
https://lists.yoctoproject.org/g/linux-yocto/message/13694
Mute This Topic: https://lists.yoctoproject.org/mt/105000434/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][yocto-kernel-cache][master/yocto-6.6][PATCH] bsp/intel-x86: remove intel-x86-64-preempt-rt.cfg in scc file

2024-03-17 Thread Yongxin Liu via lists.yoctoproject.org
intel-x86-64-preempt-rt.cfg was removed in commit bd20a636b044
("config: remove mis-located configuration fragment").

Signed-off-by: Yongxin Liu 
---
 bsp/intel-x86/intel-x86-64-preempt-rt.scc | 1 -
 1 file changed, 1 deletion(-)

diff --git a/bsp/intel-x86/intel-x86-64-preempt-rt.scc 
b/bsp/intel-x86/intel-x86-64-preempt-rt.scc
index 63d517ec..e776cfa9 100644
--- a/bsp/intel-x86/intel-x86-64-preempt-rt.scc
+++ b/bsp/intel-x86/intel-x86-64-preempt-rt.scc
@@ -8,4 +8,3 @@ include ktypes/preempt-rt
 include intel-x86-64.scc
 include features/tsn/tsn.scc
 kconf hardware cfs-bandwidth.cfg
-kconf hardware intel-x86-64-preempt-rt.cfg
-- 
2.43.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13691): 
https://lists.yoctoproject.org/g/linux-yocto/message/13691
Mute This Topic: https://lists.yoctoproject.org/mt/104997867/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] [yocto-autobuilder2][PATCH] schedulers: metrics: Start again with master for the daily full download

2024-03-16 Thread Yoann Congal
(Replying to myself to keep conclusion of an IRC discussion)

Le sam. 16 mars 2024 à 00:29, Yoann Congal  a écrit :

> Change the order of metrics branches:
> * First, master at 5am which may do the full CVE download (might take
>   1 hour to finish).
> * Then, the other branches starting at 6am to allow them to use the
>   fresh download.
> * And, finally, generate global charts data from individual branch
>   metrics (at 8am)
>

That would not work since the master metrics can go well above 1h (e.g.
https://autobuilder.yoctoproject.org/typhoon/#/builders/138/builds/1343)

What we want is:
* A triggering builder (see
https://docs.buildbot.net/3.8.0/manual/configuration/steps/trigger.html)
that
  * for each branch,
* trigger a builder that do the run-cvecheck (starting with master for
the NVD database download)
  * Finish with the chart generation (run-cvechart)

That way, we will have proper ordering/dependencies between metrics
computing and chart generation.

NB: Trying to order builders on the AB based on estimated build duration
does not work because workers are quite loaded and the pressure regulation
can extend the build time quite a bit.


> Compared with commit 839c3cedbf6f ("schedulers: metrics: Start with master
> for the daily full download"),
> the last part is new.
>
> Signed-off-by: Yoann Congal 
> ---
>



>  schedulers.py | 9 +++--
>  1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/schedulers.py b/schedulers.py
> index a30383f..67cc739 100644
> --- a/schedulers.py
> +++ b/schedulers.py
> @@ -497,12 +497,17 @@
> schedulers.append(sched.Nightly(name='nightly-meta-oe-mirror',
> branch='master',
>  schedulers.append(sched.Nightly(name='nightly-reproducible-meta-oe',
> branch='master', properties=parent_default_props('reproducible-meta-oe'),
>builderNames=['reproducible-meta-oe'], hour=2,
> minute=0, dayOfWeek=5))
>
> -# Run metrics at 3-7am each day
> +# Run metrics at 5-8am each day
> +# Starts with master which may do a full CVE database download and start
> other
> +# branches 1 hour later to allow them to re-use the fresh download.
> +schedulers.append(sched.Nightly(name='nightly-metrics', branch='master',
> properties=parent_default_props('metrics'), builderNames=['metrics'],
> hour=5, minute=0))
>  schedulers.append(sched.Nightly(name='nightly-metrics-dunfell',
> branch='dunfell', properties=parent_default_props('metrics', 'dunfell'),
> builderNames=['metrics'], hour=6, minute=0, codebases = {'' : {'branch' :
> 'dunfell'}}))
>  schedulers.append(sched.Nightly(name='nightly-metrics-kirkstone',
> branch='kirkstone', properties=parent_default_props('metrics',
> 'kirkstone'), builderNames=['metrics'], hour=6, minute=15, codebases = {''
> : {'branch' : 'kirkstone'}}))
>  schedulers.append(sched.Nightly(name='nightly-metrics-mickledore',
> branch='mickledore', properties=parent_default_props('metrics',
> 'mickledore'), builderNames=['metrics'], hour=6, minute=30, codebases = {''
> : {'branch' : 'mickledore'}}))
>  schedulers.append(sched.Nightly(name='nightly-metrics-nanbield',
> branch='nanbield', properties=parent_default_props('metrics', 'nanbield'),
> builderNames=['metrics'], hour=6, minute=45, codebases = {'' : {'branch' :
> 'nanbield'}}))
> -schedulers.append(sched.Nightly(name='nightly-metrics', branch='master',
> properties=parent_default_props('metrics'), builderNames=['metrics'],
> hour=7, minute=0))
> +# Generate charts after every branch had its metrics computed
> +schedulers.append(sched.Nightly(name='nightly-metrics-charts',
> branch='master', properties=parent_default_props('metrics'),
> builderNames=['metrics-charts'], hour=8, minute=0))
> +
>
>  # Run check-layer-nightly twice a week for nanbield
>  schedulers.append(sched.Nightly(name='nightly-check-layer-nanbield',
> properties=parent_default_props('check-layer-nightly', 'nanbield'),
> --
> 2.39.2
>
>

-- 
Yoann Congal
Smile ECS - Tech expert

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62772): https://lists.yoctoproject.org/g/yocto/message/62772
Mute This Topic: https://lists.yoctoproject.org/mt/104959134/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] [yocto-autobuilder2][PATCH] schedulers: metrics: Start again with master for the daily full download

2024-03-15 Thread Yoann Congal
Change the order of metrics branches:
* First, master at 5am which may do the full CVE download (might take
  1 hour to finish).
* Then, the other branches starting at 6am to allow them to use the
  fresh download.
* And, finally, generate global charts data from individual branch
  metrics (at 8am)

Compared with commit 839c3cedbf6f ("schedulers: metrics: Start with master for 
the daily full download"),
the last part is new.

Signed-off-by: Yoann Congal 
---
 schedulers.py | 9 +++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/schedulers.py b/schedulers.py
index a30383f..67cc739 100644
--- a/schedulers.py
+++ b/schedulers.py
@@ -497,12 +497,17 @@ 
schedulers.append(sched.Nightly(name='nightly-meta-oe-mirror', branch='master',
 schedulers.append(sched.Nightly(name='nightly-reproducible-meta-oe', 
branch='master', properties=parent_default_props('reproducible-meta-oe'),
   builderNames=['reproducible-meta-oe'], hour=2, minute=0, 
dayOfWeek=5))
 
-# Run metrics at 3-7am each day
+# Run metrics at 5-8am each day
+# Starts with master which may do a full CVE database download and start other
+# branches 1 hour later to allow them to re-use the fresh download.
+schedulers.append(sched.Nightly(name='nightly-metrics', branch='master', 
properties=parent_default_props('metrics'), builderNames=['metrics'], hour=5, 
minute=0))
 schedulers.append(sched.Nightly(name='nightly-metrics-dunfell', 
branch='dunfell', properties=parent_default_props('metrics', 'dunfell'), 
builderNames=['metrics'], hour=6, minute=0, codebases = {'' : {'branch' : 
'dunfell'}}))
 schedulers.append(sched.Nightly(name='nightly-metrics-kirkstone', 
branch='kirkstone', properties=parent_default_props('metrics', 'kirkstone'), 
builderNames=['metrics'], hour=6, minute=15, codebases = {'' : {'branch' : 
'kirkstone'}}))
 schedulers.append(sched.Nightly(name='nightly-metrics-mickledore', 
branch='mickledore', properties=parent_default_props('metrics', 'mickledore'), 
builderNames=['metrics'], hour=6, minute=30, codebases = {'' : {'branch' : 
'mickledore'}}))
 schedulers.append(sched.Nightly(name='nightly-metrics-nanbield', 
branch='nanbield', properties=parent_default_props('metrics', 'nanbield'), 
builderNames=['metrics'], hour=6, minute=45, codebases = {'' : {'branch' : 
'nanbield'}}))
-schedulers.append(sched.Nightly(name='nightly-metrics', branch='master', 
properties=parent_default_props('metrics'), builderNames=['metrics'], hour=7, 
minute=0))
+# Generate charts after every branch had its metrics computed
+schedulers.append(sched.Nightly(name='nightly-metrics-charts', 
branch='master', properties=parent_default_props('metrics'), 
builderNames=['metrics-charts'], hour=8, minute=0))
+
 
 # Run check-layer-nightly twice a week for nanbield
 schedulers.append(sched.Nightly(name='nightly-check-layer-nanbield', 
properties=parent_default_props('check-layer-nightly', 'nanbield'),
-- 
2.39.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62771): https://lists.yoctoproject.org/g/yocto/message/62771
Mute This Topic: https://lists.yoctoproject.org/mt/104959134/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] [yocto-autobuilder-helper][PATCH 1/2] run-cvecheck: Split out the chart generation code

2024-03-15 Thread Yoann Congal
run-cvecheck had a special case for master were it would generate chart
data after computing CVE metrics. This had to happen last in the list
branches calling run-cvecheck.

By spliting run-cvecheck into 2:
* run-cvecheck (only does the cve-check),
* run-cvecharts (only does the chart generation),
... we can run-cvecheck on master first while keeping run-cvecharts
last.

Signed-off-by: Yoann Congal 
---
 scripts/run-cvecharts | 79 +++
 scripts/run-cvecheck  | 13 ---
 2 files changed, 79 insertions(+), 13 deletions(-)
 create mode 100755 scripts/run-cvecharts

diff --git a/scripts/run-cvecharts b/scripts/run-cvecharts
new file mode 100755
index 000..d55
--- /dev/null
+++ b/scripts/run-cvecharts
@@ -0,0 +1,79 @@
+#!/bin/bash
+#
+# SPDX-License-Identifier: GPL-2.0-only
+#
+
+set -eu
+
+ARGS=$(getopt -o '' --long 'metrics:,results:,push' -n 'run-cvecharts' -- "$@")
+if [ $? -ne 0 ]; then
+echo 'Cannot parse arguments...' >&2
+exit 1
+fi
+eval set -- "$ARGS"
+unset ARGS
+
+# Location of the yocto-autobuilder-helper scripts
+OURDIR=$(dirname $0)
+# The metrics repository to use
+METRICSDIR=""
+# Where to copy results to
+RESULTSDIR=""
+# Whether to push the metrics
+PUSH=0
+
+while true; do
+case "$1" in
+'--metrics')
+METRICSDIR=$(realpath $2)
+shift 2
+continue
+;;
+'--results')
+RESULTSDIR=$(realpath -m $2)
+shift 2
+continue
+;;
+'--push')
+PUSH=1
+shift
+continue
+;;
+'--')
+shift
+break
+;;
+*)
+echo "Unexpected value $1" >&2
+exit 1
+;;
+esac
+done
+
+if ! test "$METRICSDIR" -a "$RESULTSDIR"; then
+echo "Not all required options specified"
+exit 1
+fi
+
+#
+# CVE Chart data generation
+#
+if [ ! -d $RESULTSDIR ]; then
+mkdir $RESULTSDIR
+fi
+
+# Do another pull to make sure we're as up to date as possible.  This is
+# preferable to committing and rebasing before pushing as it would be better to
+# waste some time repeating work than commit potentially corrupted files from a
+# git merge gone wrong.
+git -C $METRICSDIR pull
+
+$OURDIR/cve-generate-chartdata --json $METRICSDIR/cve-count-byday.json 
--resultsdir $METRICSDIR/cve-check/
+git -C $METRICSDIR add cve-count-byday.json
+git -C $METRICSDIR commit -asm "Autobuilder updating CVE counts" || true
+if [ "$PUSH" = "1" ]; then
+   git -C $METRICSDIR push
+fi
+
+cp $METRICSDIR/cve-count-byday.json $RESULTSDIR
+cp $METRICSDIR/cve-count-byday-lastyear.json $RESULTSDIR
diff --git a/scripts/run-cvecheck b/scripts/run-cvecheck
index 373f57c..13ba6e3 100755
--- a/scripts/run-cvecheck
+++ b/scripts/run-cvecheck
@@ -94,16 +94,3 @@ if [ -e tmp/log/cve/cve-summary.json ]; then
 fi
 $OURDIR/cve-report.py tmp/log/cve/cve-summary.json > 
$RESULTSDIR/cve-status-$BRANCH.txt
 fi
-
-if [ "$BRANCH" = "master" ]; then
-mkdir -p $METRICSDIR/cve-check/$BRANCH/
-$OURDIR/cve-generate-chartdata --json $METRICSDIR/cve-count-byday.json 
--resultsdir $METRICSDIR/cve-check/
-git -C $METRICSDIR add cve-count-byday.json
-git -C $METRICSDIR commit -asm "Autobuilder updating CVE counts" || true
-if [ "$PUSH" = "1" ]; then
-git -C $METRICSDIR push
-fi
-
-cp $METRICSDIR/cve-count-byday.json $RESULTSDIR
-cp $METRICSDIR/cve-count-byday-lastyear.json $RESULTSDIR
-fi
-- 
2.39.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62769): https://lists.yoctoproject.org/g/yocto/message/62769
Mute This Topic: https://lists.yoctoproject.org/mt/104959075/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] [yocto-autobuilder-helper][PATCH 2/2] config.json: metrics: Add new metrics-charts builder

2024-03-15 Thread Yoann Congal
This builder generates global chart data from individual branch metrics.
By splitting it out of metrics we can simplify metrics and schedule it
more freely.

This builder should be scheduled after metrics has been run for every
branch.

Signed-off-by: Yoann Congal 
---
 config.json | 17 +
 1 file changed, 17 insertions(+)

diff --git a/config.json b/config.json
index 763121a..5b63313 100644
--- a/config.json
+++ b/config.json
@@ -1332,6 +1332,23 @@
 "EXTRACMDS": [ "${SCRIPTSDIR}/run-abint 
${HELPERRESULTSDIR}/../../abint/"]
 }
 },
+"metrics-charts" : {
+"NEEDREPOS" : ["poky", "meta-openembedded"],
+"step1" : {
+"shortname" : "Fetching metrics repositories",
+"EXTRAPLAINCMDS" : [
+"git clone ssh://g...@push.yoctoproject.org/yocto-metrics 
&& git clone ssh://g...@push.yoctoproject.org/yocto-metrics-meta-oe"
+]
+},
+"step2" : {
+"shortname" : "CVE charts for meta",
+"EXTRACMDS" : ["${SCRIPTSDIR}/run-cvecharts --metrics 
../yocto-metrics --results ${HELPERRESULTSDIR}/../../patchmetrics --push"]
+},
+"step3" : {
+"shortname" : "CVE charts for meta-oe",
+"EXTRACMDS" : ["${SCRIPTSDIR}/run-cvecharts --metrics 
../yocto-metrics-meta-oe --results 
${HELPERRESULTSDIR}/../../patchmetrics-meta-oe --push"]
+}
+},
 "meta-mingw" : {
 "NEEDREPOS" : ["poky", "meta-mingw"],
 "MACHINE" : "qemux86-64",
-- 
2.39.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62770): https://lists.yoctoproject.org/g/yocto/message/62770
Mute This Topic: https://lists.yoctoproject.org/mt/104959076/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] [yocto-autobuilder2][PATCH] schedulers: metrics: Start with master for the daily full download

2024-03-13 Thread Yoann Congal
Change the order of metrics branches:
* First, master at 5am which may do the full CVE download (might take
  1 hour to finish).
* Then, the other branches starting at 6am to allow them to use the
  fresh download.

Signed-off-by: Yoann Congal 
---
 schedulers.py | 6 --
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/schedulers.py b/schedulers.py
index a30383f..34e2b70 100644
--- a/schedulers.py
+++ b/schedulers.py
@@ -497,12 +497,14 @@ 
schedulers.append(sched.Nightly(name='nightly-meta-oe-mirror', branch='master',
 schedulers.append(sched.Nightly(name='nightly-reproducible-meta-oe', 
branch='master', properties=parent_default_props('reproducible-meta-oe'),
   builderNames=['reproducible-meta-oe'], hour=2, minute=0, 
dayOfWeek=5))
 
-# Run metrics at 3-7am each day
+# Run metrics at 5-7am each day
+# Starts with master which may do a full CVE database download and start other
+# branches 1 hour later to allow them to re-use the fresh download.
+schedulers.append(sched.Nightly(name='nightly-metrics', branch='master', 
properties=parent_default_props('metrics'), builderNames=['metrics'], hour=5, 
minute=0))
 schedulers.append(sched.Nightly(name='nightly-metrics-dunfell', 
branch='dunfell', properties=parent_default_props('metrics', 'dunfell'), 
builderNames=['metrics'], hour=6, minute=0, codebases = {'' : {'branch' : 
'dunfell'}}))
 schedulers.append(sched.Nightly(name='nightly-metrics-kirkstone', 
branch='kirkstone', properties=parent_default_props('metrics', 'kirkstone'), 
builderNames=['metrics'], hour=6, minute=15, codebases = {'' : {'branch' : 
'kirkstone'}}))
 schedulers.append(sched.Nightly(name='nightly-metrics-mickledore', 
branch='mickledore', properties=parent_default_props('metrics', 'mickledore'), 
builderNames=['metrics'], hour=6, minute=30, codebases = {'' : {'branch' : 
'mickledore'}}))
 schedulers.append(sched.Nightly(name='nightly-metrics-nanbield', 
branch='nanbield', properties=parent_default_props('metrics', 'nanbield'), 
builderNames=['metrics'], hour=6, minute=45, codebases = {'' : {'branch' : 
'nanbield'}}))
-schedulers.append(sched.Nightly(name='nightly-metrics', branch='master', 
properties=parent_default_props('metrics'), builderNames=['metrics'], hour=7, 
minute=0))
 
 # Run check-layer-nightly twice a week for nanbield
 schedulers.append(sched.Nightly(name='nightly-check-layer-nanbield', 
properties=parent_default_props('check-layer-nightly', 'nanbield'),
-- 
2.39.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62754): https://lists.yoctoproject.org/g/yocto/message/62754
Mute This Topic: https://lists.yoctoproject.org/mt/104913450/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] [yocto-autobuilder-helper][PATCH] config.json: metrics: Switch to daily CVE DB full-download

2024-03-13 Thread Yoann Congal
By using CVE_DB_INCR_UPDATE_AGE_THRES = CVE_DB_INCR_UPDATE_AGE_THRES = 6h,
cve-check will do a NVD database full download if the database is older
than 6h or reuse it un-updated if its younger than 6h. Since the metrics
builder is scheduled every day, that will result in a daily
full-download.

That will workaround NVD API limitations were some updates may be missed
and the incrementaly updated database is not equivalent to a freshly
downloaded database.

Signed-off-by: Yoann Congal 

---
This patch depends on [PATCH 2/2] cve-update-nvd2-native: Add an age threshold 
for incremental update
https://lists.openembedded.org/g/openembedded-core/message/197046
---
 config.json | 1 +
 1 file changed, 1 insertion(+)

diff --git a/config.json b/config.json
index fdf4052..763121a 100644
--- a/config.json
+++ b/config.json
@@ -1290,6 +1290,7 @@
 "CVE_CHECK_FORMAT_JSON = '1'",
 "CVE_CHECK_SHOW_WARNINGS = '0'",
 "CVE_DB_UPDATE_INTERVAL = '21600'",
+"CVE_DB_INCR_UPDATE_AGE_THRES = '21600'",
 "BB_SERVER_TIMEOUT = '0'"
 ],
 "step1" : {
-- 
2.39.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62753): https://lists.yoctoproject.org/g/yocto/message/62753
Mute This Topic: https://lists.yoctoproject.org/mt/104913380/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 1/3] nxp-imx9: Enable imx93 MIPI phy

2024-03-10 Thread Bruce Ashfield
All three patches are now merged.

Bruce

In message: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 1/3] nxp-imx9: 
Enable imx93 MIPI phy
on 06/03/2024 Xiaolei Wang via lists.yoctoproject.org wrote:

> Enable imx93 MIPI phy.
> 
> Signed-off-by: Xiaolei Wang 
> ---
>  bsp/nxp-imx9/nxp-imx9.cfg | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg
> index 1bee68aa..1fd96acd 100644
> --- a/bsp/nxp-imx9/nxp-imx9.cfg
> +++ b/bsp/nxp-imx9/nxp-imx9.cfg
> @@ -341,6 +341,7 @@ CONFIG_DRM_MXS=y
>  CONFIG_DRM_MXSFB=y
>  CONFIG_MUX_MMIO=y
>  CONFIG_RESET_IMX7=y
> +CONFIG_PHY_FSL_IMX93_MIPI_DPHY=y
>  
>  #
>  ## Therminal Driver
> -- 
> 2.25.1
> 

> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13661): 
https://lists.yoctoproject.org/g/linux-yocto/message/13661
Mute This Topic: https://lists.yoctoproject.org/mt/104762935/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Yocto Project Quick Build - MACHINE

2024-03-07 Thread Worik Stanton
>
>
> Is there a part of the manual I can read that explains what this is?
>
>
The intel-meta README

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62707): https://lists.yoctoproject.org/g/yocto/message/62707
Mute This Topic: https://lists.yoctoproject.org/mt/104799797/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Yocto Project Quick Build - MACHINE

2024-03-07 Thread Worik Stanton
Thanks for the help.

The system is telling me it succeeded,  I used intel-corei7-64

I have a directory: build/tmp/deploy/images/intel-corei7-64 that has a lot
of artifacts in it, and  I am unsure of how to test it.

The yocto system I was working with created a single image file.  I am
looking at a lot of parts here.

Is there a part of the manual I can read that explains what this is?



On Fri, 8 Mar 2024 at 13:57, Worik Stanton via lists.yoctoproject.org
 wrote:

>
>> Hi,
>> did you add meta-altera here?
>>
>> build/conf/bblayers.conf
>>
>>
> Thank you, no.  It was right there in the documentation: "bitbake-layers
> add-layer ../meta-altera"
>
>
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62706): https://lists.yoctoproject.org/g/yocto/message/62706
Mute This Topic: https://lists.yoctoproject.org/mt/104799797/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Yocto Project Quick Build - MACHINE

2024-03-07 Thread Worik Stanton
>
>
> Hi,
> did you add meta-altera here?
>
> build/conf/bblayers.conf
>
>
Thank you, no.  It was right there in the documentation: "bitbake-layers
add-layer ../meta-altera"

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62705): https://lists.yoctoproject.org/g/yocto/message/62705
Mute This Topic: https://lists.yoctoproject.org/mt/104799797/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Yocto Project Quick Build - MACHINE

2024-03-07 Thread Markus Volk
On Thu, Mar 7 2024 at 03:46:30 PM -08:00:00, Worik Stanton 
 wrote:

What have I done wrong?


Hi,
did you add meta-altera here?

build/conf/bblayers.conf


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62704): https://lists.yoctoproject.org/g/yocto/message/62704
Mute This Topic: https://lists.yoctoproject.org/mt/104799797/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Yocto Project Quick Build - qemu

2024-03-07 Thread Worik Stanton
>
> > What I see in my terminal is:
> >
> > runqemu - INFO - Running MACHINE=qemux86-64 bitbake -e  ...
> > runqemu - INFO - Continuing with the following parameters:
> > KERNEL: [/home/yocto/poky/build/tmp/deploy/images/qemux86-64/bzImage]
> > MACHINE: [qemux86-64]
> > FSTYPE: [ext4]
> > ROOTFS:
> [/home/yocto/poky/build/tmp/deploy/images/qemux86-64/core-image-sato-qemux86-64.rootfs-20240307220730.ext4]
> > CONFFILE:
> [/home/yocto/poky/build/tmp/deploy/images/qemux86-64/core-image-sato-qemux86-64.rootfs-20240307220730.qemuboot.conf]
> >
> > runqemu - INFO - Using preconfigured tap device tap0
> > runqemu - INFO - If this is not intended, touch
> /tmp/qemu-tap-locks/tap0.skip to make runqemu skip tap0.
> > runqemu - INFO - Network configuration: ip=192.168.7.2::192.168.7.1
> :255.255.255.0::eth0:off:8.8.8.8 net.ifnames=0
> > runqemu - INFO - Running
> /home/yocto/poky/build/tmp/work/x86_64-linux/qemu-helper-native/1.0/recipe-sysroot-native/usr/bin/qemu-system-x86_64
> -device virtio-net-pci,netdev=net0,mac=52:54:00:12:34:02 -netdev
> tap,id=net0,ifname=tap0,script=no,downscript=no -object
> rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0
> -drive
> file=/home/yocto/poky/build/tmp/deploy/images/qemux86-64/core-image-sato-qemux86-64.rootfs-20240307220730.ext4,if=virtio,format=raw
> -usb -device usb-tablet -usb -device usb-kbd   -cpu IvyBridge -machine
> q35,i8042=off -smp 4 -m 512 -serial mon:vc -serial null -device virtio-vga
>  -display sdl,show-cursor=on  -kernel
> /home/yocto/poky/build/tmp/deploy/images/qemux86-64/bzImage -append
> 'root=/dev/vda rw  ip=192.168.7.2::192.168.7.1:255.255.255.0::eth0:off:8.8.8.8
> net.ifnames=0 oprofile.timer=1 tsc=reliable no_timer_check
> rcupdate.rcu_expedited=1 swiotlb=0 '
> >
> > runqemu - INFO - Host uptime: 3820.75
>
> You should be able to ssh to root@192.168.7.2
>
>
I see!  I have built the wrong build?  "sato" is a mobile build, does it
include a SSH server?

Worik

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62703): https://lists.yoctoproject.org/g/yocto/message/62703
Mute This Topic: https://lists.yoctoproject.org/mt/104799142/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Yocto Project Quick Build - MACHINE

2024-03-07 Thread Worik Stanton
Progressing I am at the stage:

Customizing Your Build for Specific Hardware

I have unpacked the `meta-altera` repository as instructed

I edited my build/conf/local.conf

MACHINE ??= "cyclone5"

I get the error:

MACHINE=cyclone5 is invalid. Please set a valid MACHINE in your local.conf,
environment or other configuration file.

Thrashing around a little I re-ran "source oe-init-build-env" but that did
not help

What have I done wrong?
W

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62702): https://lists.yoctoproject.org/g/yocto/message/62702
Mute This Topic: https://lists.yoctoproject.org/mt/104799797/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Yocto Project Quick Build - qemu

2024-03-07 Thread Richard Purdie
On Thu, 2024-03-07 at 15:06 -0800, Worik Stanton wrote:
> Friends
> 
> I am starting from first principles and following Yocto Project Quick Build.
> 
> I am at the step: Simulate Your Image Using QEMU:
> 
> I am unfamiliar with qemu.  But it has started up (I watched it spin its 
> wheels in top) but there is nothing to show for it. 
> 
> I am running in a Debian Bullseye LXC container as I have had trouble 
> building Yocto builds in Bookworm.  Was that a bad decision?  
> 
> I am unsure if I have failed or succeeded!
> 
> What I see in my terminal is:
> 
> runqemu - INFO - Running MACHINE=qemux86-64 bitbake -e  ...
> runqemu - INFO - Continuing with the following parameters:
> KERNEL: [/home/yocto/poky/build/tmp/deploy/images/qemux86-64/bzImage]
> MACHINE: [qemux86-64]
> FSTYPE: [ext4]
> ROOTFS: 
> [/home/yocto/poky/build/tmp/deploy/images/qemux86-64/core-image-sato-qemux86-64.rootfs-20240307220730.ext4]
> CONFFILE: 
> [/home/yocto/poky/build/tmp/deploy/images/qemux86-64/core-image-sato-qemux86-64.rootfs-20240307220730.qemuboot.conf]
> 
> runqemu - INFO - Using preconfigured tap device tap0
> runqemu - INFO - If this is not intended, touch /tmp/qemu-tap-locks/tap0.skip 
> to make runqemu skip tap0.
> runqemu - INFO - Network configuration: 
> ip=192.168.7.2::192.168.7.1:255.255.255.0::eth0:off:8.8.8.8 net.ifnames=0
> runqemu - INFO - Running 
> /home/yocto/poky/build/tmp/work/x86_64-linux/qemu-helper-native/1.0/recipe-sysroot-native/usr/bin/qemu-system-x86_64
>  -device virtio-net-pci,netdev=net0,mac=52:54:00:12:34:02 -netdev 
> tap,id=net0,ifname=tap0,script=no,downscript=no -object 
> rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0 
> -drive 
> file=/home/yocto/poky/build/tmp/deploy/images/qemux86-64/core-image-sato-qemux86-64.rootfs-20240307220730.ext4,if=virtio,format=raw
>  -usb -device usb-tablet -usb -device usb-kbd   -cpu IvyBridge -machine 
> q35,i8042=off -smp 4 -m 512 -serial mon:vc -serial null -device virtio-vga  
> -display sdl,show-cursor=on  -kernel 
> /home/yocto/poky/build/tmp/deploy/images/qemux86-64/bzImage -append 
> 'root=/dev/vda rw  
> ip=192.168.7.2::192.168.7.1:255.255.255.0::eth0:off:8.8.8.8 net.ifnames=0 
> oprofile.timer=1 tsc=reliable no_timer_check rcupdate.rcu_expedited=1 
> swiotlb=0 '
> 
> runqemu - INFO - Host uptime: 3820.75

You should be able to ssh to root@192.168.7.2

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62701): https://lists.yoctoproject.org/g/yocto/message/62701
Mute This Topic: https://lists.yoctoproject.org/mt/104799142/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Yocto Project Quick Build - qemu

2024-03-07 Thread Worik Stanton
Friends

I am starting from first principles and following Yocto Project Quick Build.

I am at the step: Simulate Your Image Using QEMU:

I am unfamiliar with qemu.  But it has started up (I watched it spin its
wheels in top) but there is nothing to show for it.

I am running in a Debian Bullseye LXC container as I have had trouble
building Yocto builds in Bookworm.  Was that a bad decision?

I am unsure if I have failed or succeeded!

What I see in my terminal is:

runqemu - INFO - Running MACHINE=qemux86-64 bitbake -e  ...
runqemu - INFO - Continuing with the following parameters:
KERNEL: [/home/yocto/poky/build/tmp/deploy/images/qemux86-64/bzImage]
MACHINE: [qemux86-64]
FSTYPE: [ext4]
ROOTFS:
[/home/yocto/poky/build/tmp/deploy/images/qemux86-64/core-image-sato-qemux86-64.rootfs-20240307220730.ext4]
CONFFILE:
[/home/yocto/poky/build/tmp/deploy/images/qemux86-64/core-image-sato-qemux86-64.rootfs-20240307220730.qemuboot.conf]

runqemu - INFO - Using preconfigured tap device tap0
runqemu - INFO - If this is not intended, touch
/tmp/qemu-tap-locks/tap0.skip to make runqemu skip tap0.
runqemu - INFO - Network configuration:
ip=192.168.7.2::192.168.7.1:255.255.255.0::eth0:off:8.8.8.8
net.ifnames=0
runqemu - INFO - Running
/home/yocto/poky/build/tmp/work/x86_64-linux/qemu-helper-native/1.0/recipe-sysroot-native/usr/bin/qemu-system-x86_64
-device virtio-net-pci,netdev=net0,mac=52:54:00:12:34:02 -netdev
tap,id=net0,ifname=tap0,script=no,downscript=no -object
rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0
-drive
file=/home/yocto/poky/build/tmp/deploy/images/qemux86-64/core-image-sato-qemux86-64.rootfs-20240307220730.ext4,if=virtio,format=raw
-usb -device usb-tablet -usb -device usb-kbd   -cpu IvyBridge -machine
q35,i8042=off -smp 4 -m 512 -serial mon:vc -serial null -device virtio-vga
 -display sdl,show-cursor=on  -kernel
/home/yocto/poky/build/tmp/deploy/images/qemux86-64/bzImage -append
'root=/dev/vda rw  ip=192.168.7.2::192.168.7.1:255.255.255.0::eth0:off:8.8.8.8
net.ifnames=0 oprofile.timer=1 tsc=reliable no_timer_check
rcupdate.rcu_expedited=1 swiotlb=0 '

runqemu - INFO - Host uptime: 3820.75

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62700): https://lists.yoctoproject.org/g/yocto/message/62700
Mute This Topic: https://lists.yoctoproject.org/mt/104799142/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 3/3] nxp-imx9: Enable PWM_ADP5585 for imx9 ADP5585

2024-03-06 Thread Xiaolei Wang via lists.yoctoproject.org
Enable PWM_ADP5585 for imx9 ADP5585.

Signed-off-by: Xiaolei Wang 
---
 bsp/nxp-imx9/nxp-imx9.cfg | 1 +
 1 file changed, 1 insertion(+)

diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg
index c4c2b91c..499b0750 100644
--- a/bsp/nxp-imx9/nxp-imx9.cfg
+++ b/bsp/nxp-imx9/nxp-imx9.cfg
@@ -85,6 +85,7 @@ CONFIG_REGULATOR_MAX8973=y
 CONFIG_REGULATOR_PCA9450=y
 CONFIG_REGULATOR_PFUZE100=y
 CONFIG_REGULATOR_PWM=y
+CONFIG_PWM_ADP5585=y
 
 #
 # MMC Driver
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13646): 
https://lists.yoctoproject.org/g/linux-yocto/message/13646
Mute This Topic: https://lists.yoctoproject.org/mt/104762937/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 2/3] nxp-imx9: Enable NOP_USB_XCEIV for nxp-imx9

2024-03-06 Thread Xiaolei Wang via lists.yoctoproject.org
Enable NOP_USB_XCEIV for nxp-imx9.

Signed-off-by: Xiaolei Wang 
---
 bsp/nxp-imx9/nxp-imx9.cfg | 1 +
 1 file changed, 1 insertion(+)

diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg
index 1fd96acd..c4c2b91c 100644
--- a/bsp/nxp-imx9/nxp-imx9.cfg
+++ b/bsp/nxp-imx9/nxp-imx9.cfg
@@ -432,6 +432,7 @@ CONFIG_USB_G_NCM=m
 CONFIG_USB_G_ACM_MS=m
 CONFIG_USB_MASS_STORAGE=m
 CONFIG_USB_DWC3=y
+CONFIG_NOP_USB_XCEIV=y
 
 #
 # Typec driver
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13645): 
https://lists.yoctoproject.org/g/linux-yocto/message/13645
Mute This Topic: https://lists.yoctoproject.org/mt/104762936/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 1/3] nxp-imx9: Enable imx93 MIPI phy

2024-03-06 Thread Xiaolei Wang via lists.yoctoproject.org
Enable imx93 MIPI phy.

Signed-off-by: Xiaolei Wang 
---
 bsp/nxp-imx9/nxp-imx9.cfg | 1 +
 1 file changed, 1 insertion(+)

diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg
index 1bee68aa..1fd96acd 100644
--- a/bsp/nxp-imx9/nxp-imx9.cfg
+++ b/bsp/nxp-imx9/nxp-imx9.cfg
@@ -341,6 +341,7 @@ CONFIG_DRM_MXS=y
 CONFIG_DRM_MXSFB=y
 CONFIG_MUX_MMIO=y
 CONFIG_RESET_IMX7=y
+CONFIG_PHY_FSL_IMX93_MIPI_DPHY=y
 
 #
 ## Therminal Driver
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13644): 
https://lists.yoctoproject.org/g/linux-yocto/message/13644
Mute This Topic: https://lists.yoctoproject.org/mt/104762935/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 1/2] nxp-imx9: Add nxp-imx9 BSP kernel cache

2024-03-05 Thread Bruce Ashfield
merged.

Bruce

In message: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 1/2] nxp-imx9: 
Add nxp-imx9 BSP kernel cache
on 04/03/2024 Xiaolei Wang wrote:

> nxp-imx9 and nxp-imx8 use a set of kernel cache in the
> SDK, and some drivers are common, such as the media module,
> so here I deleted the imx8-related pinctrl, clk and other
> CPU-related configurations based on the imx8 kernel cache,
> no changes will be made to other peripherals.
> 
> Signed-off-by: Xiaolei Wang 
> ---
>  bsp/nxp-imx9/nxp-imx9-preempt-rt.cfg |  15 +
>  bsp/nxp-imx9/nxp-imx9-preempt-rt.scc |   9 +
>  bsp/nxp-imx9/nxp-imx9-standard.scc   |   7 +
>  bsp/nxp-imx9/nxp-imx9.cfg| 610 +++
>  bsp/nxp-imx9/nxp-imx9.scc|  11 +
>  5 files changed, 652 insertions(+)
>  create mode 100644 bsp/nxp-imx9/nxp-imx9-preempt-rt.cfg
>  create mode 100644 bsp/nxp-imx9/nxp-imx9-preempt-rt.scc
>  create mode 100644 bsp/nxp-imx9/nxp-imx9-standard.scc
>  create mode 100644 bsp/nxp-imx9/nxp-imx9.cfg
>  create mode 100644 bsp/nxp-imx9/nxp-imx9.scc
> 
> diff --git a/bsp/nxp-imx9/nxp-imx9-preempt-rt.cfg 
> b/bsp/nxp-imx9/nxp-imx9-preempt-rt.cfg
> new file mode 100644
> index ..780e974a
> --- /dev/null
> +++ b/bsp/nxp-imx9/nxp-imx9-preempt-rt.cfg
> @@ -0,0 +1,15 @@
> +..
> +.WARNING
> +.
> +. This file is a kernel configuration fragment, and not a full kernel
> +. configuration file.  The final kernel configuration is made up of
> +. an assembly of processed fragments, each of which is designed to
> +. capture a specific part of the final configuration (e.g. platform
> +. configuration, feature configuration, and board specific hardware
> +. configuration).  For more information on kernel configuration, please
> +. consult the product documentation.
> +.
> +..
> +
> +# CONFIG_TRANSPARENT_HUGEPAGE is not set
> +# CONFIG_LEDS_TRIGGER_CPU is not set
> diff --git a/bsp/nxp-imx9/nxp-imx9-preempt-rt.scc 
> b/bsp/nxp-imx9/nxp-imx9-preempt-rt.scc
> new file mode 100644
> index ..57ce73f9
> --- /dev/null
> +++ b/bsp/nxp-imx9/nxp-imx9-preempt-rt.scc
> @@ -0,0 +1,9 @@
> +define KMACHINE nxp-imx9
> +define KTYPE preempt-rt
> +define KARCH arm64
> +
> +include ktypes/preempt-rt
> +
> +include nxp-imx9.scc
> +
> +kconf hardware nxp-imx9-preempt-rt.cfg
> diff --git a/bsp/nxp-imx9/nxp-imx9-standard.scc 
> b/bsp/nxp-imx9/nxp-imx9-standard.scc
> new file mode 100644
> index ..4483215c
> --- /dev/null
> +++ b/bsp/nxp-imx9/nxp-imx9-standard.scc
> @@ -0,0 +1,7 @@
> +define KMACHINE nxp-imx9
> +define KTYPE standard
> +define KARCH arm64
> +
> +include ktypes/standard
> +
> +include nxp-imx9.scc
> diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg
> new file mode 100644
> index ..945541a1
> --- /dev/null
> +++ b/bsp/nxp-imx9/nxp-imx9.cfg
> @@ -0,0 +1,610 @@
> +CONFIG_ARM64=y
> +CONFIG_SMP=y
> +CONFIG_ARCH_NXP=y
> +CONFIG_ARCH_LAYERSCAPE=y
> +CONFIG_ARCH_MXC=y
> +CONFIG_HAVE_IMX_BUSFREQ=y
> +
> +CONFIG_PM=y
> +CONFIG_CPU_PM=y
> +
> +#
> +# CPU Idle
> +#
> +CONFIG_CPU_IDLE=y
> +CONFIG_ARM_PSCI_CPUIDLE=y
> +CONFIG_ARM_PSCI_CPUIDLE_DOMAIN=y
> +
> +#
> +# CPU Frequency scaling
> +#
> +CONFIG_CPU_FREQ=y
> +CONFIG_CPU_FREQ_GOV_ATTR_SET=y
> +CONFIG_CPU_FREQ_GOV_COMMON=y
> +CONFIG_CPU_FREQ_STAT=y
> +CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
> +CONFIG_CPU_FREQ_GOV_POWERSAVE=y
> +CONFIG_CPU_FREQ_GOV_USERSPACE=y
> +CONFIG_CPU_FREQ_GOV_ONDEMAND=y
> +CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
> +CONFIG_CPU_FREQ_GOV_SCHEDUTIL=y
> +
> +#
> +# CPU frequency scaling drivers
> +#
> +CONFIG_CPUFREQ_DT=y
> +CONFIG_ARM_IMX_CPUFREQ_DT=y
> +
> +#
> +# CAN
> +#
> +CONFIG_CAN=m
> +CONFIG_CAN_FLEXCAN=m
> +
> +CONFIG_PCI=y
> +CONFIG_PCI_MSI=y
> +CONFIG_PCI_IMX6=y
> +CONFIG_PCI_IMX6_HOST=y
> +CONFIG_PHY_FSL_IMX8Q_PCIE=y
> +
> +CONFIG_IMX_DSP=y
> +CONFIG_IMX_SCU=y
> +CONFIG_IMX_SCU_PD=y
> +CONFIG_IMX_SECO_MU=y
> +CONFIG_IMX_EL_ENCLAVE=m
> +CONFIG_IMX_ELE_TRNG=y
> +
> +#
> +## MTD
> +#
> +CONFIG_MTD=y
> +CONFIG_MTD_CMDLINE_PARTS=y
> +CONFIG_MTD_BLOCK=y
> +CONFIG_MTD_CFI=y
> +CONFIG_MTD_CFI_ADV_OPTIONS=y
> +CONFIG_MTD_CFI_INTELEXT=y
> +CONFIG_MTD_CFI_AMDSTD=y
> +CONFIG_MTD_CFI_STAA=y
> +CONFIG_MTD_PHYSMAP=y
> +CONFIG_MTD_PHYSMAP_OF=y
> +CONFIG_MTD_DATAFLASH=y
> +CONFIG_MTD_RAW_NAND=y
> +CONFIG_MTD_NAND_DENALI_DT=y
> +CONFIG_MTD_SPI_NOR=y
> +CONFIG_MTD_SST25L=y
> +
> +#
> +## Regulator 

Re: [linux-yocto][yocto-kernel-cache][yocto-5.15 and yocto-6.1][PATCH] features/net_sched: remove retired config NET_SCH_CBQ and NET_SCH_DSMARK

2024-03-05 Thread Bruce Ashfield
I've already had these removed in 6.6 and master for a bit now,
so I've done cherry-picks instead of taking this patch.

Bruce

In message: [linux-yocto][yocto-kernel-cache][yocto-5.15 and yocto-6.1][PATCH] 
features/net_sched: remove retired config NET_SCH_CBQ and NET_SCH_DSMARK
on 04/03/2024 Yongxin Liu wrote:

> CONFIG_NET_SCH_CBQ was retired in kernel upstream commit 051d442098421
> ("net/sched: Retire CBQ qdisc").
> 
> CONFIG_NET_SCH_DSMARK was retired in kernel upstream commit bbe77c14ee61
> ("net/sched: Retire dsmark qdisc").
> 
> Signed-off-by: Yongxin Liu 
> ---
>  features/net_sched/net_sched.cfg | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/features/net_sched/net_sched.cfg 
> b/features/net_sched/net_sched.cfg
> index 4d72a9f9..d0473170 100644
> --- a/features/net_sched/net_sched.cfg
> +++ b/features/net_sched/net_sched.cfg
> @@ -7,7 +7,6 @@ CONFIG_NET_SCHED=y
>  #
>  # Queueing/Scheduling
>  #
> -CONFIG_NET_SCH_CBQ=m
>  CONFIG_NET_SCH_HTB=m
>  CONFIG_NET_SCH_HFSC=m
>  CONFIG_NET_SCH_PRIO=m
> @@ -16,7 +15,6 @@ CONFIG_NET_SCH_SFQ=m
>  CONFIG_NET_SCH_TEQL=m
>  CONFIG_NET_SCH_TBF=m
>  CONFIG_NET_SCH_GRED=m
> -CONFIG_NET_SCH_DSMARK=m
>  CONFIG_NET_SCH_NETEM=m
>  CONFIG_NET_SCH_INGRESS=m
>  CONFIG_NET_SCH_CODEL=m
> -- 
> 2.43.2
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13636): 
https://lists.yoctoproject.org/g/linux-yocto/message/13636
Mute This Topic: https://lists.yoctoproject.org/mt/104714319/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] [yocto-autobuilder-helper] [PATCH] config.json: Switch poky-altcfg to use ipk as the package backend

2024-03-04 Thread Michael Opdenacker via lists.yoctoproject.org

Hi Richard,

On 3/4/24 at 16:48, Richard Purdie wrote:

On Mon, 2024-03-04 at 16:34 +0100, Michael Opdenacker wrote:

Hi Richard

Many thanks for the patch!

On 3/4/24 at 16:14, Richard Purdie wrote:

Since we plan to have better "binary distro" testing on the autobuilder
and we plan to primarily use ipk for this, having ipk based images available
as part of our builds is desireable.

Since we want systemd based images with ipk, it makes sense to leave standard
poky using rpm images but switch poky-altcfg to use ipk.

Whilst late in the release cycle, doing this now for scarthgap gives us a good
platform to build off in the long term too.

Signed-off-by: Richard Purdie 
---
   config.json | 5 +
   1 file changed, 5 insertions(+)

diff --git a/config.json b/config.json
index fd8335f..4d0f258 100644
--- a/config.json
+++ b/config.json
@@ -127,6 +127,7 @@
   "BUILDINFO" : true,
   "BUILDHISTORY" : true,
   "extravars" : [
+    "PACKAGE_CLASSES = 'package_ipk package_rpm package_deb'",
   "IMAGE_INSTALL:append = ' ssh-pregen-hostkeys'"
   ],
   "extratools" : "${EXTRATOOLS_URL}",
@@ -140,6 +141,7 @@
   "BUILDINFO" : true,
   "BUILDHISTORY" : true,
   "extravars" : [
+    "PACKAGE_CLASSES = 'package_ipk package_rpm package_deb'",
   "IMAGE_INSTALL:append = ' ssh-pregen-hostkeys'"
   ],
   "extratools" : "${EXTRATOOLS_URL}",
@@ -198,6 +200,9 @@
   "altcfg-hw" : {
   "DISTRO" : "poky-altcfg",
   "BUILDINFO" : true,
+    "extravars" : [
+    "PACKAGE_CLASSES = 'package_ipk package_rpm package_deb'"
+    ],
   "step1" : {
   "BBTARGETS" : "core-image-full-cmdline core-image-sato 
core-image-sato-sdk"
   }


Actually, to use these images for testing package upgrades through
feeds, we also need enough free space in the images.
Could we also add something like IMAGE_ROOTFS_EXTRA_SPACE = "262144"?

Setting that "globally" for those templates will potentially break other
images the usual way to do it would be:

IMAGE_ROOTFS_EXTRA_SPACE:append = "+ 102400"

but I still worry about side effects, e.g. for minimal or initramfs images.
Which images do we plan to test? core-image-full-cmdline and what else?

We probably need a set of definitions like:

IMAGE_ROOTFS_EXTRA_SPACE:append:pn-core-image-full-cmdline = " + 262144"

but something like:

IMAGE_ROOTFS_EXTRA_SPACE:append = "${@bb.utils.contains("IMAGE_FEATURES, "package-management", " + 
262144", "", d)}"

might work.



Ouch, good catch.
I'd vote for the second option. When we have package management, it 
makes sense to keep enough space for downloading and applying updates.

Cheers
Michael.

--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62673): https://lists.yoctoproject.org/g/yocto/message/62673
Mute This Topic: https://lists.yoctoproject.org/mt/104723845/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] [yocto-autobuilder-helper] [PATCH] config.json: Switch poky-altcfg to use ipk as the package backend

2024-03-04 Thread Richard Purdie
On Mon, 2024-03-04 at 16:34 +0100, Michael Opdenacker wrote:
> Hi Richard
> 
> Many thanks for the patch!
> 
> On 3/4/24 at 16:14, Richard Purdie wrote:
> > Since we plan to have better "binary distro" testing on the autobuilder
> > and we plan to primarily use ipk for this, having ipk based images available
> > as part of our builds is desireable.
> > 
> > Since we want systemd based images with ipk, it makes sense to leave 
> > standard
> > poky using rpm images but switch poky-altcfg to use ipk.
> > 
> > Whilst late in the release cycle, doing this now for scarthgap gives us a 
> > good
> > platform to build off in the long term too.
> > 
> > Signed-off-by: Richard Purdie 
> > ---
> >   config.json | 5 +
> >   1 file changed, 5 insertions(+)
> > 
> > diff --git a/config.json b/config.json
> > index fd8335f..4d0f258 100644
> > --- a/config.json
> > +++ b/config.json
> > @@ -127,6 +127,7 @@
> >   "BUILDINFO" : true,
> >   "BUILDHISTORY" : true,
> >   "extravars" : [
> > +    "PACKAGE_CLASSES = 'package_ipk package_rpm package_deb'",
> >   "IMAGE_INSTALL:append = ' ssh-pregen-hostkeys'"
> >   ],
> >   "extratools" : "${EXTRATOOLS_URL}",
> > @@ -140,6 +141,7 @@
> >   "BUILDINFO" : true,
> >   "BUILDHISTORY" : true,
> >   "extravars" : [
> > +    "PACKAGE_CLASSES = 'package_ipk package_rpm package_deb'",
> >   "IMAGE_INSTALL:append = ' ssh-pregen-hostkeys'"
> >   ],
> >   "extratools" : "${EXTRATOOLS_URL}",
> > @@ -198,6 +200,9 @@
> >   "altcfg-hw" : {
> >   "DISTRO" : "poky-altcfg",
> >   "BUILDINFO" : true,
> > +    "extravars" : [
> > +    "PACKAGE_CLASSES = 'package_ipk package_rpm package_deb'"
> > +    ],
> >   "step1" : {
> >   "BBTARGETS" : "core-image-full-cmdline core-image-sato 
> > core-image-sato-sdk"
> >   }
> > 
> Actually, to use these images for testing package upgrades through 
> feeds, we also need enough free space in the images.
> Could we also add something like IMAGE_ROOTFS_EXTRA_SPACE = "262144"?

Setting that "globally" for those templates will potentially break other
images the usual way to do it would be:

IMAGE_ROOTFS_EXTRA_SPACE:append = "+ 102400"

but I still worry about side effects, e.g. for minimal or initramfs images.
Which images do we plan to test? core-image-full-cmdline and what else?

We probably need a set of definitions like:

IMAGE_ROOTFS_EXTRA_SPACE:append:pn-core-image-full-cmdline = " + 262144"

but something like:

IMAGE_ROOTFS_EXTRA_SPACE:append = "${@bb.utils.contains("IMAGE_FEATURES, 
"package-management", " + 262144", "", d)}"

might work.

Cheers,

Richard


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62672): https://lists.yoctoproject.org/g/yocto/message/62672
Mute This Topic: https://lists.yoctoproject.org/mt/104723845/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] [yocto-autobuilder-helper] [PATCH] config.json: Switch poky-altcfg to use ipk as the package backend

2024-03-04 Thread Michael Opdenacker via lists.yoctoproject.org

Hi Richard

Many thanks for the patch!

On 3/4/24 at 16:14, Richard Purdie wrote:

Since we plan to have better "binary distro" testing on the autobuilder
and we plan to primarily use ipk for this, having ipk based images available
as part of our builds is desireable.

Since we want systemd based images with ipk, it makes sense to leave standard
poky using rpm images but switch poky-altcfg to use ipk.

Whilst late in the release cycle, doing this now for scarthgap gives us a good
platform to build off in the long term too.

Signed-off-by: Richard Purdie 
---
  config.json | 5 +
  1 file changed, 5 insertions(+)

diff --git a/config.json b/config.json
index fd8335f..4d0f258 100644
--- a/config.json
+++ b/config.json
@@ -127,6 +127,7 @@
  "BUILDINFO" : true,
  "BUILDHISTORY" : true,
  "extravars" : [
+"PACKAGE_CLASSES = 'package_ipk package_rpm package_deb'",
  "IMAGE_INSTALL:append = ' ssh-pregen-hostkeys'"
  ],
  "extratools" : "${EXTRATOOLS_URL}",
@@ -140,6 +141,7 @@
  "BUILDINFO" : true,
  "BUILDHISTORY" : true,
  "extravars" : [
+"PACKAGE_CLASSES = 'package_ipk package_rpm package_deb'",
  "IMAGE_INSTALL:append = ' ssh-pregen-hostkeys'"
  ],
  "extratools" : "${EXTRATOOLS_URL}",
@@ -198,6 +200,9 @@
  "altcfg-hw" : {
  "DISTRO" : "poky-altcfg",
  "BUILDINFO" : true,
+"extravars" : [
+"PACKAGE_CLASSES = 'package_ipk package_rpm package_deb'"
+],
  "step1" : {
  "BBTARGETS" : "core-image-full-cmdline core-image-sato 
core-image-sato-sdk"
  }

Actually, to use these images for testing package upgrades through 
feeds, we also need enough free space in the images.
Could we also add something like IMAGE_ROOTFS_EXTRA_SPACE = "262144"? 
Thanks again Cheers Michael. --


Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62670): https://lists.yoctoproject.org/g/yocto/message/62670
Mute This Topic: https://lists.yoctoproject.org/mt/104723845/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] [yocto-autobuilder-helper] [PATCH] config.json: Switch poky-altcfg to use ipk as the package backend

2024-03-04 Thread Tim Orling
On Mon, Mar 4, 2024 at 7:14 AM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:

> Since we plan to have better "binary distro" testing on the autobuilder
> and we plan to primarily use ipk for this, having ipk based images
> available
> as part of our builds is desireable.
>

Definitely agree.

>
> Since we want systemd based images with ipk, it makes sense to leave
> standard
> poky using rpm images but switch poky-altcfg to use ipk.
>

Good idea!

>
> Whilst late in the release cycle, doing this now for scarthgap gives us a
> good
> platform to build off in the long term too.
>

Seems like a good idea to me!

>
> Signed-off-by: Richard Purdie 
> ---
>  config.json | 5 +
>  1 file changed, 5 insertions(+)
>
> diff --git a/config.json b/config.json
> index fd8335f..4d0f258 100644
> --- a/config.json
> +++ b/config.json
> @@ -127,6 +127,7 @@
>  "BUILDINFO" : true,
>  "BUILDHISTORY" : true,
>  "extravars" : [
> +"PACKAGE_CLASSES = 'package_ipk package_rpm package_deb'",
>  "IMAGE_INSTALL:append = ' ssh-pregen-hostkeys'"
>  ],
>  "extratools" : "${EXTRATOOLS_URL}",
> @@ -140,6 +141,7 @@
>  "BUILDINFO" : true,
>  "BUILDHISTORY" : true,
>  "extravars" : [
> +"PACKAGE_CLASSES = 'package_ipk package_rpm package_deb'",
>  "IMAGE_INSTALL:append = ' ssh-pregen-hostkeys'"
>  ],
>  "extratools" : "${EXTRATOOLS_URL}",
> @@ -198,6 +200,9 @@
>  "altcfg-hw" : {
>  "DISTRO" : "poky-altcfg",
>  "BUILDINFO" : true,
> +"extravars" : [
> +"PACKAGE_CLASSES = 'package_ipk package_rpm package_deb'"
> +],
>  "step1" : {
>  "BBTARGETS" : "core-image-full-cmdline core-image-sato
> core-image-sato-sdk"
>  }
> --
> 2.40.1
>
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62669): https://lists.yoctoproject.org/g/yocto/message/62669
Mute This Topic: https://lists.yoctoproject.org/mt/104723845/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] [yocto-autobuilder-helper][kirkstone 2/2] config.json: use buildtools for Ubuntu 18.04 (both x86 and arm)

2024-03-04 Thread Steve Sakoman
Signed-off-by: Steve Sakoman 
---
 config.json | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/config.json b/config.json
index 4b7ee34..60fe6a4 100644
--- a/config.json
+++ b/config.json
@@ -11,6 +11,7 @@
 "BUILDTOOLS_URL_TEMPLOCAL" : 
"/srv/autobuilder/autobuilder.yocto.io/pub/non-release/20210214-8/buildtools/x86_64-buildtools-extended-nativesdk-standalone-3.2+snapshot-7d38cc8e749aedb8435ee71847e04b353cca541d.sh",
 "BUILDTOOLS_URL_TEMPLOCAL2" : 
"https://downloads.yoctoproject.org/releases/yocto/milestones/yocto-3.1_M3/buildtools/x86_64-buildtools-extended-nativesdk-standalone-3.0+snapshot-20200315.sh;,
 "BUILDTOOLS_URL" : 
"https://downloads.yoctoproject.org/releases/yocto/yocto-4.3/buildtools/x86_64-buildtools-extended-nativesdk-standalone-4.3.sh;,
+"BUILDTOOLS_ARM_URL" : 
"https://downloads.yoctoproject.org/releases/yocto/yocto-4.3/buildtools/aarch64-buildtools-extended-nativesdk-standalone-4.3.sh;,
 
 "REPO_STASH_DIR" : "${BASE_HOMEDIR}/git/mirror",
 "TRASH_DIR" : "${BASE_HOMEDIR}/git/trash",
@@ -1311,6 +1312,8 @@
 "debian9*" : "${BUILDTOOLS_URL}",
 "centos7*" : "${BUILDTOOLS_URL}",
 "ubuntu1604*" : "${BUILDTOOLS_URL}",
+"ubuntu1804-ty-*" : "${BUILDTOOLS_URL}",
+"ubuntu1804-arm-*" : "${BUILDTOOLS_ARM_URL}",
 "alma8*"   : "${BUILDTOOLS_URL}",
 "stream8*" : "${BUILDTOOLS_URL}",
 "opensuse153*" : "${BUILDTOOLS_URL}",
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62668): https://lists.yoctoproject.org/g/yocto/message/62668
Mute This Topic: https://lists.yoctoproject.org/mt/104724006/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] [yocto-autobuilder-helper][kirkstone 1/2] config.json: update to latest buildtools tarball

2024-03-04 Thread Steve Sakoman
Signed-off-by: Steve Sakoman 
---
 config.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/config.json b/config.json
index 7c53c46..4b7ee34 100644
--- a/config.json
+++ b/config.json
@@ -10,7 +10,7 @@
 
 "BUILDTOOLS_URL_TEMPLOCAL" : 
"/srv/autobuilder/autobuilder.yocto.io/pub/non-release/20210214-8/buildtools/x86_64-buildtools-extended-nativesdk-standalone-3.2+snapshot-7d38cc8e749aedb8435ee71847e04b353cca541d.sh",
 "BUILDTOOLS_URL_TEMPLOCAL2" : 
"https://downloads.yoctoproject.org/releases/yocto/milestones/yocto-3.1_M3/buildtools/x86_64-buildtools-extended-nativesdk-standalone-3.0+snapshot-20200315.sh;,
-"BUILDTOOLS_URL" : 
"/srv/autobuilder/autobuilder.yocto.io/pub/non-release/20230223-18/buildtools/x86_64-buildtools-extended-nativesdk-standalone-4.1+snapshot-9c07de0f20042c81496185293857284048d7912c.sh",
+"BUILDTOOLS_URL" : 
"https://downloads.yoctoproject.org/releases/yocto/yocto-4.3/buildtools/x86_64-buildtools-extended-nativesdk-standalone-4.3.sh;,
 
 "REPO_STASH_DIR" : "${BASE_HOMEDIR}/git/mirror",
 "TRASH_DIR" : "${BASE_HOMEDIR}/git/trash",
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62667): https://lists.yoctoproject.org/g/yocto/message/62667
Mute This Topic: https://lists.yoctoproject.org/mt/104724004/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] [yocto-autobuilder-helper][kirkstone 0/2] Patch review

2024-03-04 Thread Steve Sakoman
This series updates kirkstone to use the latest buildtools for selected
x86 and arm workers.

Passed a-full on autobuilder:

https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6640

The following changes since commit 9131fbeab58f0cad50c99dc9ba9003f04155999e:

  cve-report: Add summary counts of CVEs by recipe (2024-01-24 10:24:15 +)

are available in the Git repository at:

  https://git.yoctoproject.org/yocto-autobuilder-helper contrib/kirkstone-next
  
https://git.yoctoproject.org/yocto-autobuilder-helper/log/?h=contrib/kirkstone-next

Steve Sakoman (2):
  config.json: update to latest buildtools tarball
  config.json: use buildtools for Ubuntu 18.04 (both x86 and arm)

 config.json | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62666): https://lists.yoctoproject.org/g/yocto/message/62666
Mute This Topic: https://lists.yoctoproject.org/mt/104724001/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] [yocto-autobuilder-helper] [PATCH] config.json: Switch poky-altcfg to use ipk as the package backend

2024-03-04 Thread Richard Purdie
Since we plan to have better "binary distro" testing on the autobuilder
and we plan to primarily use ipk for this, having ipk based images available
as part of our builds is desireable.

Since we want systemd based images with ipk, it makes sense to leave standard
poky using rpm images but switch poky-altcfg to use ipk.

Whilst late in the release cycle, doing this now for scarthgap gives us a good
platform to build off in the long term too.

Signed-off-by: Richard Purdie 
---
 config.json | 5 +
 1 file changed, 5 insertions(+)

diff --git a/config.json b/config.json
index fd8335f..4d0f258 100644
--- a/config.json
+++ b/config.json
@@ -127,6 +127,7 @@
 "BUILDINFO" : true,
 "BUILDHISTORY" : true,
 "extravars" : [
+"PACKAGE_CLASSES = 'package_ipk package_rpm package_deb'",
 "IMAGE_INSTALL:append = ' ssh-pregen-hostkeys'"
 ],
 "extratools" : "${EXTRATOOLS_URL}",
@@ -140,6 +141,7 @@
 "BUILDINFO" : true,
 "BUILDHISTORY" : true,
 "extravars" : [
+"PACKAGE_CLASSES = 'package_ipk package_rpm package_deb'",
 "IMAGE_INSTALL:append = ' ssh-pregen-hostkeys'"
 ],
 "extratools" : "${EXTRATOOLS_URL}",
@@ -198,6 +200,9 @@
 "altcfg-hw" : {
 "DISTRO" : "poky-altcfg",
 "BUILDINFO" : true,
+"extravars" : [
+"PACKAGE_CLASSES = 'package_ipk package_rpm package_deb'"
+],
 "step1" : {
 "BBTARGETS" : "core-image-full-cmdline core-image-sato 
core-image-sato-sdk"
 }
-- 
2.40.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62665): https://lists.yoctoproject.org/g/yocto/message/62665
Mute This Topic: https://lists.yoctoproject.org/mt/104723845/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



  1   2   3   4   5   6   7   8   9   10   >