We have many recipes appended to IMAGE_INSTALL in our image recipes and it
works just fine.
>From your description, it sounds like you could go either way. I personally
prefer to keep my image recipes as clean as possible, so I push as much as
I can to individual recipes. This helps with
sorry about that, right now the config files are placed in the files directory
of the recipe which builds the module.
Sample snippets of the recipe concerning this config file, I removed the rest
of lines.
SRC_URI = " \
file://config.json \
"
do_install_append() {
install -m 0644
From: Limeng
Hi Bruce,
CONFIG_SENSORS_ALTERA_A10S config is not for stratix10 platform,
So remove it.
Could you please help to merge this patch into yocto-kernel-cache, branch is
yocto-5.10?
diffstat info ad below:
intel-socfpga-64.cfg |1 -
1 file changed, 1 deletion(-)
thanks,
From: Meng Li
CONFIG_SENSORS_ALTERA_A10S config is not for stratix10 platform,
So remove it.
Signed-off-by: Meng Li
---
bsp/intel-socfpga/intel-socfpga-64.cfg | 1 -
1 file changed, 1 deletion(-)
diff --git a/bsp/intel-socfpga/intel-socfpga-64.cfg
b/bsp/intel-socfpga/intel-socfpga-64.cfg
You left a few details out about how the configuration files are managed.
Ideally you could just make bitbake recipes for the config files
themselves. This way you can create an image recipe for each project and
use the IMAGE_INSTALL variable to append whatever configs and modules you
want on a
Hi everyone,
I'm curious on a good approach when dealing with multiple projects
I've just started out yocto and have already created our own meta-layer which
contains our modules. Now these modules would sometimes have config files and
this could vary when each project that we have would use
add Paul Eggleton
On 7/13/21 10:44 AM, Changqing Li wrote:
From: Changqing Li
Now, YPCompatibleVersions's name is only designed for using version like
2.0 3.0, the max_length is 25. but we mostly use Codename for layer
compatibility, eg: LAYERSERIES_COMPAT_dpdk = "dunfell gatesgarth
From: Changqing Li
Now, YPCompatibleVersions's name is only designed for using version like
2.0 3.0, the max_length is 25. but we mostly use Codename for layer
compatibility, eg: LAYERSERIES_COMPAT_dpdk = "dunfell gatesgarth
hardknott", in this case, it's not enough to save the compatible
Hi Bruce,
Please help to merge this patch into our linux-yocto repo.
patch:
0001-pci-octeontx2-Workaround-for-PEM-config-space-writes.patch
repo:
linux-yocto
branch:
v5.10/standard/cn-sdkv5.4/octeon
From: Sunil Goutham
commit cff5676836acd0f92cc7b72b8965f1201ff42278 from
g...@git.assembla.com:cavium/WindRiver.linux.git
This patch adds workaround for config space write's
byte enables issue in the PEM generated TLPs.
Issue: In the TLPs generated by PEM for config space
writes to offsets >
I'm using Zeus. I'm trying to create and mount a data partition using wic. My
wks file is
part u-boot --source rawcopy --sourceparams="file=u-boot.imx" --ondisk mmc
--no-table --align 1
part /boot --source bootimg-partition --ondisk mmc --fstype=vfat --label bootA
--active --align 4096
On 2021-07-12 12:04 p.m., Alexander Kanavin wrote:
**[Please note: This e-mail is from an EXTERNAL e-mail address]
I seem to vaguely remember that -l is not actually taking a
percentage, but an absolute value that is specific to the amount of
CPU cores a system has. Have you verified your
merged.
Bruce
In message: [linux-yocto][v5.10/standard/base][PATCH] timers: Fix
get_next_timer_interrupt() with no timers pending
on 12/07/2021 He Zhe wrote:
> From: Frederic Weisbecker
>
> 31cd0e119d50 ("timers: Recalculate next timer interrupt only when
> necessary") subtly altered
In message: [linux-yocto][linux-yocto v5.10] kernel code for marvell cn96xx
on 08/07/2021 Ruiqiang Hao wrote:
> Hi Bruce,
>
> Please help to merge this patch into our linux-yocto repo.
merged.
Bruce
>
> repo:
> linux-yocto
> branch:
>
Thanks paul,
This is now merged.
Bruce
In message: [PATCH v5.10-rt] xfrm: fix up warning introduced by pseudo revert
on 07/07/2021 Paul Gortmaker wrote:
> To fix:
> net/xfrm/xfrm_state.c:47:42: warning: 'xfrm_state_hash_generation' defined
> but not used
>
> The line was removed in the
On Wed, Jul 7, 2021 at 10:24 PM Li, Meng wrote:
>
>
>
> > -Original Message-
> > From: Bruce Ashfield
> > Sent: Thursday, July 8, 2021 3:37 AM
> > To: Li, Meng
> > Cc: linux-yocto@lists.yoctoproject.org
> > Subject: Re: [linux-yocto]: [kernel v5.10/standard/cn-sdkv5.4/octeon]:
> >
In message: Re: [linux-yocto] [kernel-cache][master yocto-5.13
yocto-5.10][PATCH] amt: enable watchdog sysfs
on 08/07/2021 Mittal, Anuj wrote:
> Thanks Bruce. Can you please merge this in yocto-5.10 as well?
Indeed! I managed to miss that branch. This is now cherry-picked
to 5.10 as well.
All,
Just a reminder we will hold the monthly Yocto Project Technical Meeting at
8am PST tomorrow. (7/13)
Yocto Project Technical Team Meeting: We encourage people attending the
meeting to logon and announce themselves on the Yocto Project IRC chancel
during the meeting (optional):
I seem to vaguely remember that -l is not actually taking a percentage, but
an absolute value that is specific to the amount of CPU cores a system has.
Have you verified your assumption?
Alex
On Mon, 12 Jul 2021 at 14:11, Trevor Gamblin
wrote:
> This adds the "-l" option to PARALLEL_MAKE in
On 2021-07-08 9:53 a.m., Randy MacLeod wrote:
YP AB Intermittent failures meeting
===
July 1, 2021, 9 AM ET
https://windriver.zoom.us/j/3696693975
Attendees: Tony, Richard, Trevor, Randy
Summary:
The autobuilder RCU hang is still fixed ;-),
Hello,
I see that meta-spdxscanner has been moved to
http://git.yoctoproject.org, and doesn't maintained on github
anymore.https://github.com/dl9pf/meta-spdxscanner/issues/21
Therefore the only way to get in contact to developers is writing to this ML
I am trying to understand how
This adds the "-l" option to PARALLEL_MAKE in config.json with an
initial testing value of 100 (100% system load). This option is supported
by both Make and Ninja. However, we also require the "--debug=j" option
to be passed to Make in order for the latter to report perceived system
load in the
From: Quanyang Wang
64-bit division "(u64 A) / (u32 B)" will break linking on ARCH arm:
arm-linux-gnueabihf-ld: drivers/spi/spi-cadence-quadspi.o: in function
`cqspi_setdlldelay':
spi-cadence-quadspi.c:(.text+0x1400): undefined reference to `__aeabi_uldivmod'
Fix this by using do_div.
From: Quanyang Wang
64-bit division "(u64 A) / (u32 B)" will break linking on ARCH arm:
arm-linux-gnueabihf-ld: drivers/clk/si5324drv.o: in function `si5324_find_n2ls':
si5324drv.c:(.text+0xb94): undefined reference to `__aeabi_uldivmod'
Fix this by using do_div.
Signed-off-by: Quanyang Wang
From: Quanyang Wang
64-bit division "(u64 A) / (u32 B)" will break linking on ARCH arm:
rm-linux-gnueabihf-ld: drivers/rtc/rtc-zynqmp.o: in function
`xlnx_rtc_read_offset':
rtc-zynqmp.c:(.text+0x48): undefined reference to `__aeabi_ldivmod'
Fix this by using do_div.
Signed-off-by: Quanyang
From: Quanyang Wang
The driver zynqmp-sha.c calls the function "__flush_cache_user_range"
which is arm64 specific, and it will break compilation in other ARCHs.
So drop COMPILE_TEST from Kconfig.
Signed-off-by: Quanyang Wang
---
drivers/crypto/Kconfig | 2 +-
1 file changed, 1 insertion(+),
From: Quanyang Wang
This patch fixes compile error as below:
drivers/media/platform/xilinx/xilinx-hdmirxss.c:500:9: error: implicit
declaration of function ‘FIELD_PREP’ [-Werror=implicit-function-declaration]
500 | val |= FIELD_PREP(HDMIRX_VTD_CTRL_TIMERBASE_MASK, count);
|
From: Quanyang Wang
The args type and number of some functions are different between
CONFIG_ZYNQMP_FIRMWARE is enabled and disabled. Let's unify them
to avoid compile error.
Signed-off-by: Quanyang Wang
---
include/linux/firmware/xlnx-zynqmp.h | 8
1 file changed, 4 insertions(+), 4
From: Quanyang Wang
This patch fixes compile error as below:
drivers/media/i2c/adv7511-v4l2.c:416:9: error: ‘return’ with a value, in
function returning void [-Werror=return-type]
416 | return 0;
| ^
Signed-off-by: Quanyang Wang
---
drivers/media/i2c/adv7511-v4l2.c | 2 +-
From: Quanyang Wang
Because of commit 43f33b6e59c2 ("hwmon: (pmbus) Add 'phase' parameter
where needed for multi-phase support"), the function "pmbus_read_word_data"
needs one more argument "phase". Since tps544 doesn't support
multi-phase, this "phase" argument will be ignored. Let's pass
From: Quanyang Wang
The argument "attr" to sysfs_attr_init is "struct attribute *" type
not "struct device_attribute *" type. This patch fixes the compile
error as below:
drivers/misc/xilinx-ai-engine/ai-engine-sysfs.c: In function
‘aie_sysfs_create_dev_attr’:
From: Quanyang Wang
When enabling CONFIG_UAPI_HEADER_TEST, there will be compile error as
below:
In file included from :32:
./usr/include/linux/xlnxsync.h:37:2: error: unknown type name ‘u8’
37 | u8 prod_sync : 1;
| ^~
There is no u8/u16/u32/u64/bool definition in uapi headers. So
From: Quanyang Wang
When enabling CONFIG_UAPI_HEADER_TEST, there will be compile error as
below:
In file included from :32:
./usr/include/linux/xlnx_mpg2tsmux_interface.h:59:2: error: unknown type name
‘u8’
59 | u8 stream_id;
| ^~
There is no u8/u16/u32/u64/bool definition in uapi
From: Quanyang Wang
When enabling CONFIG_UAPI_HEADER_TEST, there will be compile error as
below:
In file included from ./usr/include/linux/xilinx-sdirxss.h:7,
from :32:
./usr/include/linux/videodev2.h:2418:20: error: field ‘timestamp’ has
incomplete type
2418 | struct
From: Quanyang Wang
There are two global variables with the same name "lp". This will result
the link error as below:
aarch64-linux-gnu-ld: drivers/staging/xroeframer/xroe_framer.o:(.bss+0x0):
multiple definition of `lp';
drivers/net/ethernet/xilinx/xilinx_tsn_switch.o:(.bss+0x80): first
From: Quanyang Wang
Hi Bruce & Michal,
Would you please help review these patches?
These patches fix the build error when enabling allyesconfig for arm and arm64.
And the build errors can be reproduced by:
For arm32:
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- allyesconfig
make ARCH=arm
From: Frederic Weisbecker
31cd0e119d50 ("timers: Recalculate next timer interrupt only when
necessary") subtly altered get_next_timer_interrupt()'s behaviour. The
function no longer consistently returns KTIME_MAX with no timers
pending.
In order to decide if there are any timers pending we
37 matches
Mail list logo
