On Sat, May 2, 2020, 1:22 PM Rudolf J Streif
wrote:
> eMMC devices commonly have three hardware partitions: two boot
> partitions and a user partition. I was looking for a convenient way to
> have wic build an image for the boot partition and one for the user
> partition. However, that does not
eMMC devices commonly have three hardware partitions: two boot
partitions and a user partition. I was looking for a convenient way to
have wic build an image for the boot partition and one for the user
partition. However, that does not seem to be possible right out of the
box. The variable
On Sat, 2 May 2020, Denys Dmytriyenko wrote:
> https://lists.yoctoproject.org/g/yocto/topic/73258946
ah, i remember that exchange, but i was focused on the patching
aspect of it, not the simpler copying aspect.
rday
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
https://lists.yoctoproject.org/g/yocto/topic/73258946
On Sat, May 02, 2020 at 11:55:59AM -0400, Robert P. J. Day wrote:
>
> was playing with shadow and PAM stuff, and noticed this in
> shadow.inc:
>
> # Additional Policy files for PAM
> PAM_SRC_URI = "file://pam.d/chfn \
>
was playing with shadow and PAM stuff, and noticed this in
shadow.inc:
# Additional Policy files for PAM
PAM_SRC_URI = "file://pam.d/chfn \
file://pam.d/chpasswd \
file://pam.d/chsh \
file://pam.d/login \
file://pam.d/newusers \
merged to the newly created v5.6/* branches, and I'll put it in the
kernel-cache so my 5.7 work should pick it up as well.
Bruce
In message: [PATCH yocto-dev] yaffs: fix misplaced variable declaration
on 30/04/2020 Paul Gortmaker wrote:
> A variable declaration landed one function higher than
merged.
I'm ok with this being enabled by the features that need it, but am still
heistant to enable it by default on the kernel types themselves.
Cheers,
Bruce
In message: [linux-yocto][master yocto-5.4][PATCH] bpf: Add CONFIG_IKHEADERS
on 27/04/2020 zhe...@windriver.com wrote:
> From: He
Did I miss applying this to the kernel-cache previously ? or did
I miss a patch against the linux-yocto repo itself ?
The reason I ask, is that it is awkward to apply patches like this
to the tree.
If you send the patch against linux-yocto, I'll apply it and then
commit the change to the
merged to master.
Bruce
In message: [linux-yocto][kernel-cache master][PATCH] feathures/stm: Add
support for System Trace Module
on 27/04/2020 Jun Miao wrote:
> A System Trace Module (STM) is a device exporting data in System Trace
> Protocol
> (STP) format as defined by MIPI STP
What are the impacted kernel versions for this one ?
Bruce
On Wed, Apr 29, 2020 at 9:36 PM Jiping Ma wrote:
>
> Record PC value from regs[15], it should be regs[32], which cause perf
> parser the backtrace failed.
>
> Signed-off-by: Jiping Ma
> ---
> arch/arm64/kernel/perf_regs.c | 4
>
Oh, one more thing, most of those 3rd party BSP layers can be found in the
layer index:
http://layers.openembedded.org/layerindex/branch/master/layers/
Alex
On Sat, 2 May 2020 at 13:23, Alexander Kanavin
wrote:
> There is a difference between supported target architectures, and
> supported
There is a difference between supported target architectures, and supported
target machines; it's easier to talk about the latter.
Oe-core layer directly supports QEMU targets (which are *not* suitable for
any physical HW):
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/conf/machine
first, i realize PPC is still supported, despite the official
dropping of reference target MPC8315-RDB. also aware of meta-riscv
layer:
https://github.com/riscv
despite not having a reference board.
is there somewhere to point people when they ask about the state of
the world WRT
OK, finally built the u-boot-fw-utils and run it on iMX6ULL:
# fw_printenv -v
Compiled with U-Boot 2019.07-dirty
But it could not run:
# fw_printenv
Cannot read bad block mark: Invalid argument
Here is the configure file:
# cat /etc/fw_env.config
# NAND
/dev/mtd1 0x40
14 matches
Mail list logo
