On Wed, Mar 17, 2021 at 6:16 PM Khem Raj wrote:
> On Wed, Mar 17, 2021 at 9:43 AM keydi
> wrote:
> >
> > Two projects are given. They use different YP release each.
> > Projects use also different target platform each.
> >
> > I wonder if differences in structuring metadata- and recipes-
On Wed, Mar 17, 2021 at 9:43 AM keydi wrote:
>
> Two projects are given. They use different YP release each.
> Projects use also different target platform each.
>
> I wonder if differences in structuring metadata- and recipes- directory tree
> between
> these two projects result solely from
On Tue, Mar 16, 2021 at 8:53 AM keydi wrote:
>
> Hello,
>
> This is about two projects Projects A and B. Both use Yocto to build
> embedded-Linux distribution. However different Yocto release each. Also
> different target platform each. One puts Linux software packages to RPM,
> another one to
On 2021-03-16 3:20 a.m., lavkhush2...@gmail.com wrote:
I am getting issue in Avahi
*Issue- trying to remove PID file.(/run/avahi-daemon/ /pid)
*Due to this issue, i am not able to get "Service name" on host machine.
please help me.
Hello,
It's a bit hard to know where to start without more
One more question: plain-text files named 'Packages' and placed during
distribution build in subtrees tmp/deploy/rpm, .../ipk, ... are these artifacts
supported YP releases can still build?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52753):
Hi,
Anyone else encounter this?
WARNING: cve-update-db-native-1.0-r0 do_populate_cve_db: Failed to fetch CVE
data ([SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get
local issuer certificate (_ssl.c:1108))
I am not sure how to resolve this. After googling on the
In the YOCTO/Linux source tree there's _drivers/spi/_ which has all the
source for SPI drivers. There's only 1 file, _spidev.c_, which has:
static int __init spidev_init(void)
{
int status;
/* Claim our 256 reserved device numbers. Then register a class
* that will key
Two projects are given. They use different YP release each.
Projects use also different target platform each.
I wonder if differences in structuring metadata- and recipes- directory tree
between
these two projects result solely from different YP releases in use.
Or if these can be a result also
On Wed, 17 Mar 2021, keydi wrote:
> Two projects are given. They use different YP release each.
> Projects use also different target platform each.
... snip ...
> project B (YP release 2.0, actually backport of some later release
you can't legitimately expect support for YP 2.0, which is six
How are the odds for this question to get more audience on stackoverflow?
In meantime I tried to search release notes of all YP releases starting the
oldest used here for related entries. Unsure if it is the right way and
direction but me used word "Packages" to search notes of releases for. No
Two projects are given. They use different YP release each.
Projects use also different target platform each.
I wonder if differences in structuring metadata- and recipes- directory tree
between
these two projects result solely from different YP releases in use.
Or if these can be a result also
There are 2 git repos: _openembedded-core_ and _meta-openembedded._
_openembedded-core_ has _oe-init-build-env_ to create the build
environment.
_meta-openembedded_ has the recipe for _spidev-test_
If I use _oe-init-build-env_ from _openembedded-core_ to create the env
vars then try:
$
Two projects are given. They use different YP release each.
Projects use also different target platform each.
I wonder if differences in structuring metadata- and recipes- directory tree
between
these two projects result solely from different YP releases in use.
Or if these can be a result also
Hello all,
I need two specific way to halt my embedded Linux system.
The first halt mode is used to halt the system while maintaining watchdog
trigger.
The second halt mode is used to halt the system without maintaining watchdog
trigger.
These two behavior are working fine, but actually, I
From: Limeng
Hi Bruce,
NXP had relesed sdk-bsp28 for nxp s32g2xx platform.
I got the latest BSP related patches from nxp-s32g sdk kernel repo
https://source.codeaurora.org/external/autobsps32/linux,
and want to merge them into linux-yocto-v5.10. There are 88 patches.
Could you please help to
From: Meng Li
at803x phy config depends on regulator config,
so enable CONFIG_REGULATOR.
Signed-off-by: Meng Li
---
bsp/nxp-s32g2xx/nxp-s32g2xx.cfg | 3 +++
1 file changed, 3 insertions(+)
diff --git a/bsp/nxp-s32g2xx/nxp-s32g2xx.cfg b/bsp/nxp-s32g2xx/nxp-s32g2xx.cfg
index bb65ca0c..27240a0a
From: Limeng
Hi Bruce,
at803x phy config depends on regulator config,
so enable CONFIG_REGULATOR.
Could you please help to merge this patch into yocto-kernel-cache, branch is
yocto-5.10?
diffstat info ad below:
nxp-s32g2xx.cfg |3 +++
1 file changed, 3 insertions(+)
thanks,
Limeng
17 matches
Mail list logo
