Hello,
I'm trying to build a Yocto image for NXP i.MX8M (4 core 64-bit A53s). I am
getting some error when I execute the bitmake command.
I'd appreciate if you could guide me with next steps. Any Guide or url will
be helpful.
Thanks
Ajith
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages
Hello All,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.0.1.rc3.
We are planning to execute following tests for this cycle:
OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw
3. BSP-Qemu
Runtime auto test for following platforms:
1. MinnowTurbot 32-bit
2.
Hi Bruce,
These commits will update marvell_cn96xx to kernel v5.4 on linux-yocto-dev.
Target branch: standard/cn96xx.
Patches based on:standard/base.
Thanks~
Br.
The following changes since commit 7169ab2c05a45377ad22ba50f0b1a7a02e0c88ef:
arm64: dts: ti: k3-am65-main: Enable support for
From: Yanfei Xu
When some layer include this edac feature and bitbake kernel ARCH
=mips, that will cause some warning masseges.
CONFIG_EDAC and CONFIG_EDAC_DEBUG depend on CONFIG_EDAC_SUPPORT,
but CONFIG_EDAC_SUPPORT isn't enabled in most of mips bsps(except
CAVIUM_OCTEON_SOC, however
On Thu, Nov 21, 2019 at 4:12 PM Jon Mason wrote:
>
> We are proud to announce the inaugural OpenEmbedded Workshop. It is
> being held on 03 February 2020 in Brussels, Belgium. The day after
> FOSDEM.
>
> The Call for Participation is open now. For more information, go to
>
On Tue, Nov 26, 2019 at 5:51 AM Kevin Hao wrote:
>
> Hi Bruce,
>
> Here is another patch series for the Marvell cn96xx SoC support. The main
> changes are two CPU erratas and misc Ethernet bug fix. Please help me merge
> these to the following two branches:
> v5.2/standard/cn96xx
>
Hello,
I need to use a TPM2 software stack for my project (tpm2-tools, tpm2-abrmd,
tpm2-tss, etc.), where I am already using Yocto, meta-intel, meta-oe,
meta-networking, etc.
I see there are at least the following three layers that carry the necessary
TPM2 bits, with varying recipe versions.
On Wed, Nov 27, 2019 at 3:55 AM Yongxin Liu wrote:
>
> Hi Bruce,
>
> This patch was sent to mainline kernel for review.
> But it costs much more time than I thought.
> Could help to review whether it can be merged to linux-yocto v5.2?
Thanks for the link to the discussion! We can fix the issue
On Tue, Nov 26, 2019 at 7:53 AM Jun Miao wrote:
>
> Hi Bruce,
>
> About BSP ti-am65x platform, there are conflict in k3-am65-main.dtsi between
> v5.4.
> Below 2 patches are used to SD card.
>
> Could you please help to merge the 2 patches into branch v5.2/standard/base,
> linux-ycoto kernel.
On Tue, Nov 26, 2019 at 3:28 AM Xiaotao Yin wrote:
>
> Hi Bruce,
>
> This is Xiaotao, is working on marvell-cn96xx platform, and I want to enable
> CONFIG_JUMP_LABEL for marvell-cn96xx ethernet.
>
> Could you please help to merge this patch into yocto-kernel-cache, branche:
> master.
merged
Looks good to me. This is merged
Bruce
On Mon, Nov 25, 2019 at 11:52 PM wrote:
> From: Limeng
>
> Hi Bruce,
>
> Jason Wessel is working on Raspbeerypi 4 platform, and he wants to enable
> CONFIG_FB_SIMPLE for display feature.
>
> Could you please help to merge this patch into
Hi JH,
The image root file system size is based on the actual content of the
root file system. Besides ROOTFS_SIZE there are other variables that
control how the root file system is sized:
IMAGE_ROOTFS_SIZE: Defines the size in kilobytes of the created root
filesystem image. The
build system
Mauro wrote...
Actually I'm using:
EXTRA_USERS_PARAMS = " usermod -p '$(openssl passwd -6 myrootpassword)' root;"
...
But at this point I'm not sure if ${ROOT_PASSWORD} works (I'm using the
password wrote on the command, not passed by variable).
Switching to the ‘$(openssl …)’ form has
Hi
If you want to reduce the size of your root filesystem, you have to
remove software you don't need. IMAGE_ROOTFS_SIZE has no effect on the
size of your image-rootfs.tar.gz. Putting a smaller size will just lead
to a rootfs that don't fit in the expected IMAGE_ROOTFS_SIZE.
Fabien
Le mercredi
On 27/11/19 12:06, Andy Pont wrote:
I tried this out on a build that I am working on for which I needed to
add a root password and to create a non-root user with a password.
If I use:
EXTRA_USERS_PARAMS += "usermod -p `openssl passwd -6 ${ROOT_PASSWORD}`
root;”
When I try to login to the
On Wed, Nov 27, 2019 at 10:12:13PM +1100, JH wrote:
> Hi,
>
> Does the Yocto rootfs image size is based on real contents included in
> the image-rootfs.tar.gz?
>
> When I build the image with very large size of applications and
> libraries such as boost, I have my image-rootfs.tr.gz about 44 MB,
Hi,
Does the Yocto rootfs image size is based on real contents included in
the image-rootfs.tar.gz?
When I build the image with very large size of applications and
libraries such as boost, I have my image-rootfs.tr.gz about 44 MB,
then I removed all large size of applications and libraries, I
Mauro wrote...
pay attention that "openssl passwd ${ROOT_PASSWORD}" command handles only
passwords up to 8 characters (the extra characters will be truncated and the generated
hash is for the first eight).
If you want to use more than 8 characters in the password, use another password
This reverts commit 7b11e8989618581bc0226ad313264cdc05d48d86.
Consider the following hardware setting.
|-PNP0C14:00
| |-- device #1
|-PNP0C14:01
| |-- device #2
When unloading wmi driver module, device #2 will be first unregistered.
But device_destroy() using MKDEV(0, 0) will locate
Hi Bruce,
This patch was sent to mainline kernel for review.
But it costs much more time than I thought.
Could help to review whether it can be merged to linux-yocto v5.2?
For more details, please refer to https://patchwork.kernel.org/patch/11244821/
Yongxin Liu (1):
Revert "platform/x86:
20 matches
Mail list logo
