Greetings !
I am trying to add "etckeeper" to yocto . I have written a recipe and added it
in my Rootfs . But when I try to commit , I am getting the below error log:
-
root@imx6ulevk:~# etckeeper
From: Nitin Yadav
commit 527095165281cbc60a1b42995c1e55e6756cbe93 from
git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
ti,otap-del-sel-legacy/ti,itap-del-sel-legacy passed
from DT are currently ignored for all SD/MMC and eMMC
modes.
Fix this by making start loop index to MMC_TIMING_LEGACY.
From: Udit Kumar
commit fa3fc9dd2eae576a047cefa1bed9b8568143a0a8 from
git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
Commit 8be3ac2d8bd77bb9cb9ddbb7a545decf9f5e4181 Upstream.
After splitting wkup_pmx pin mux for J784S4 into four regions.
Pin mux offset for ADC nodes were not updated to
From: Udit Kumar
commit ca6a775097f0c879eaa7a2ddfe79c09fd08dffb6 from
git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
The eMMC fails to enumerate intermittently on HS400 mode. Also
observing multiple CQE recovery warnings.
Update the sdhci0 node to disable HS400.
Cc: Vignesh Raghavendra
From: Udit Kumar
commit 696d9e2d712fb42014a420942f9c787339f4a568 from
git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
After splitting the wkup_pmx into four region.
I2C and PMIC pin muxes was falling outside the assigned region.
Also removed unused pin from OSPI pin mux.
Fixes:
From: Udit Kumar
commit 7e7d44cc4b3b9694558f7e81bb1fdebb63007090 from
git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
After splitting the wkup_pmx into four region.
CSI pin mux was falling outside the assigned region.
Fixes: c33b294d75dd ("arm64: dts: ti: k3-j721s2: Fix wkup pinmux
From: Bryan Brattlof
commit c3bb4011ec46d9ac09ad127c749df13d2e7fb806 from
git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
commit c4026d3e2578291016703cd75f3a6f786f60cd80 upstream
Only some of TI's J721E SoCs will need a eFuse register range mapped to
determine if they're affected by TI's
From: Bryan Brattlof
commit a7119d957b2a8a7df21dc4f5ca87759728531a53 from
git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
commit 366444ebe7e2e1c987c6a07551f06db4b5b7c0ad upstream
Some of TI's J721E SoCs require a software trimming procedure for the
temperature monitors to function
From: Bryan Brattlof
commit 0d9ecfae1ec9e1556b8a943dbd9deea94e8d4870 from
git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
commit effe8db0a421480fc4dad0c7bf380b8e245cbb8c upstream
Elaborate on the function of this device node as well as some of the
properties this node uses.
From: Bryan Brattlof
commit d1bd8644407db9b730391bd39315ad9fb0916faf from
git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
commit 156f0e2fda420c4a4a7b244a909df04086039bd6 upstream
'fuse_base' is only needed during the initial probe function to provide
data for a software trimming method
Hi Bruce,
This patch series is to pick several patches from the TI SDK 9.0.1.2 to make
the Thermal feature work.
Please help me merge these into the following two branches:
v6.1/standard/ti-sdk-6.1/ti-j7xxx
v6.1/standard/preempt-rt/ti-sdk-6.1/ti-j7xxx
From: Bryan Brattlof
commit 83b6b872cda56104a2050124b95b91500810d782 from
git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
commit 311f328ffc7572219bee65db77645e5fedd4e8e6 upstream
Some of TI's J721E SoCs require a software trimming method to report
temperatures accurately. Currently we are
On 10/18/23 10:06, Changqing Li wrote:
From: Changqing Li
Since oe-core commit 26d97acc713 [image-artifact-names: include
${IMAGE_NAME_SUFFIX} directly in both ${IMAGE_NAME} and
${IMAGE_LINK_NAME}], image name has changed to
core-image-minimal-qemux86.rootfs.ext4, change accordingly to fix
The default value of CORES_TS_OFFSET will cause the following known issue:
# cat /sys/kernel/debug/llce_core/core1_ts
Unable to handle kernel paging request at virtual address ffc00ced0870
Mem abort info:
ESR = 0x9607
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV =
Hi Bruce,
There is one patch to correct the value of CORES_TS_OFFSET.
Would you please help to merge it into
v5.15/standard/nxp-sdk-5.15/nxp-s32g
v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g
branches?
Thanks,
Zhantao
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages
Hi Bruce,
This is a trial merge of the stable kernel v5.15.136 v6.1.58 v6.1.59 for the
following branches in the linux-yocto.
876d7300fe9e v5.15/standard/sdkv5.10/axxia
13fe5a251783 v5.15/standard/preempt-rt/sdkv5.10/axxia
2a9cd206a46f v5.15/standard/base
b3bbc5cb8dad
Fixes dropdown menus so they are functional again.
Signed-off-by: Tim Orling
---
.../static/js/{boostrap-3.4.1.min.js => bootstrap-3.4.1.min.js} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename layerindex/static/js/{boostrap-3.4.1.min.js => bootstrap-3.4.1.min.js}
(100%)
diff
On Thu, 2023-10-19 at 14:06 +, Jing Hui Tham wrote:
> Hi all,
>
> Intel and WR YP QA is planning for QA execution for YP build yocto-4.3.rc1.
> We are planning to execute following tests for this cycle:
>
> OEQA-manual tests for following module:
> 1. OE-Core
> 2. BSP-hw
>
> Runtime
Hi Darek
Making the recipe compiling for cross and native and adding a DEPENDS from
cross to native seems to be the cleanest and most Yocto-ish way to me.
Alternatively this patch would allow to run cross compiled executables with
Qemu in the cmake project
On Wed, 2023-10-18 at 07:43 +0200, Marta Rybczynska wrote:
> Hello all,
> There' a discussion pending on the usage of SRTool and CVE management
> for the Yocto project in general. It is related to the need of having
> a list of CVEs the project is affected by, those fixed and those that
> we know
Hello all,
So I have a cmake project that uses an executable generated from a cmake
subproject.
My architecture is as such
├── ProjectA
├── projecta_1.0.bb ( http://projecta_1.0.bb/ )
├── files
├── ProjectA
├── CMakeLists.txt
├── ProjectB
├── CMakeLists.txt
My recipe is a standard recipe that
This is now done with a dedicated switch, where previously the file was always
written
out, creating often unneeded clutter.
Signed-off-by: Alexander Kanavin
---
config.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/config.json b/config.json
index 94c86e1..ea6885d
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-4.3.rc1. We
are planning to execute following tests for this cycle:
OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw
Runtime auto test for following platforms:
1. MinnowBoard Turbot - 32bit
On Thu, 2023-10-19 at 12:52 +0100, Richard Purdie via
lists.yoctoproject.org wrote:
> On Thu, 2023-10-19 at 11:58 +0100, Richard Purdie via
> lists.yoctoproject.org wrote:
> > On Wed, 2023-10-18 at 15:46 +0200, David Pierret wrote:
> > > Inspired from trigger-build and trigger-build-post-trigger
>
On Thu, 2023-10-19 at 14:28 +0200, Alexis Lothoré wrote:
> Hi Ross,
> On 10/19/23 13:04, Ross Burton wrote:
> > > On 19 Oct 2023, at 09:36, Alexis Lothoré via lists.yoctoproject.org
> > > wrote:
> > I just skimmed your report and have some feedback to hopefully make it
> > easier to read in the
Hi Ross,
On 10/19/23 13:04, Ross Burton wrote:
>> On 19 Oct 2023, at 09:36, Alexis Lothoré via lists.yoctoproject.org
>> wrote:
> I just skimmed your report and have some feedback to hopefully make it easier
> to read in the future.
>
> I’d suggest sorting the output in order of importance.
On Thu, 2023-10-19 at 10:36 +0200, Alexis Lothoré wrote:
> Hello,
>
> On 10/18/23 08:16, Pokybuild User wrote:
> >
> > A build flagged for QA (yocto-4.3.rc1) was completed on the autobuilder
> > and is available at:
> >
> >
> >
On Thu, 2023-10-19 at 11:58 +0100, Richard Purdie via
lists.yoctoproject.org wrote:
> On Wed, 2023-10-18 at 15:46 +0200, David Pierret wrote:
> > Inspired from trigger-build and trigger-build-post-trigger
> > The branch must be selected on build configuration.
> >
> > Signed-off-by: David Pierret
Hi Alexis,
> On 19 Oct 2023, at 09:36, Alexis Lothoré via lists.yoctoproject.org
> wrote:
> The regression report looks worryingly empty. It has been generated with
> yocto-4.2 as comparison base. When taking a look at yocto-testresults content
> for it, I only find a few test results (11,
On Wed, 2023-10-18 at 15:46 +0200, David Pierret wrote:
> Inspired from trigger-build and trigger-build-post-trigger
> The branch must be selected on build configuration.
>
> Signed-off-by: David Pierret
> Reviewed-by: Yoann Congal
> ---
> config.json | 30 ++
> 1
This way explicitly listing the test can be avoided, especially when more tests
of the same kind will be added (such as te CDN sstate cache mirror test).
Signed-off-by: Alexander Kanavin
---
config.json | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/config.json
Hello,
On 10/18/23 08:16, Pokybuild User wrote:
>
> A build flagged for QA (yocto-4.3.rc1) was completed on the autobuilder
> and is available at:
>
>
> https://autobuilder.yocto.io/pub/releases/yocto-4.3.rc1
The regression report looks worryingly empty. It has been generated
Le jeu. 19 oct. 2023 à 01:22, Jose Quaresma a écrit :
> Hi Yoann,
Hi!
> I have found the same for BBLAYERS that was fixed [1] expanding any relative
> path that could exist.
> Maybe it would be better to also expand BB_LOGCONFIG when the newbuilddir
> argument is present.
>
> [1]
>
33 matches
Mail list logo
