<rburton>
yes, the SDK variation needs documenting, but it's the same idea just for the sdk not the target
zpfvo has quit [Ping timeout: 240 seconds]
<RobertBerger>
@rburton It does not make much sense to be different values for both in most cases, but the migration-guides seem to kind of explain it. Like by default bitbake with >5.15 but build with your SDK whatever version down to 3.2.
<rburton>
RobertBerger: sure it makes sense: you might want to have a sdk that runs on old rhel but know your target kernels are 6.x
<RobertBerger>
Ah the SDK value has to do with the host Linux kernel?
<rburton>
we bump the target minimum regularly as it means glibc can optimise itself for newer kernels
<rburton>
JaMa: looks like your image name thing broke bundled initramfs
goliath has joined #yocto
adrianf has joined #yocto
<yudjinn[m]>
I have TEST_VERSION ?= "1.2" in my bblayers.conf; is there any way to manually override that at build time? I know with machine you can just MACHINE=machine bitbake core-image... but TEST_VERSION="1.3" bitbake.. doesnt seem to work
<rburton>
bitbake cleans the environment and only allows a few environment variables through
<rburton>
see BB_ENV_PASSTHROUGH
aak-rookie has joined #yocto
<yudjinn[m]>
ahh, so you have to set BB_ENV_PASSTHROUGH_ADDITIONS
florian_kc has joined #yocto
adrianf has quit [Ping timeout: 246 seconds]
<aak-rookie>
i have an engine project in yocto. there are 3 different projects coming out of this engine. project1, project2, project3. i only have machine configuration for project1 that engine generates. i plan to create machinename-project1.conf, machinename-project2.conf, machinename-project3.conf. also, thinking of defining the common things in
<aak-rookie>
"default-common-settings.inc" file. i will include this file on machine configs. would such a structure have a problem? does it make sense? do you have any suggestions? meanwhile, the machine will be the same. for example, let's say cm4.
<aak-rookie>
specific distro, machine features or kernel configurations can be made for projects.
<khem>
aak-rookie: what other differences are there in project ?
<khem>
are they distro level policy changes
<khem>
or just something you can manage at image level
<aak-rookie>
i can say image level.
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
<khem>
in that case perhaps you can just have 3 different images for same distro and machine
<khem>
hmm if you have project based patches that might be a problem
nemik has joined #yocto
Guest33 has joined #yocto
Guest33 has quit [Client Quit]
<aak-rookie>
for example, maybe need to setgpio pins for project2 like this:
<aak-rookie>
gpio=17=op,dl \n\
<aak-rookie>
gpio=22=op,dl \n\
<aak-rookie>
gpio=5=op,dl,pd \n\
<aak-rookie>
gpio=6=op,dl,pd \n\
<aak-rookie>
that's why i thought it would make more sense to create machine confs.
<aak-rookie>
or no need touchscreen,bluetooth etc.
<khem>
how will you set this up ? via runtime conf or rootfs time tweak ?
<aak-rookie>
i'm using meta-raspberrypi. it is sufficient to add it to the RPI_EXTRA_CONFIG variable in the machine configuration. does it "rootfs time tweak" concept? i'm a rookie, i may not know all the concepts exactly. :D
gsalazar has quit [Ping timeout: 246 seconds]
adrianf has joined #yocto
florian_kc has joined #yocto
<khem>
that affects rpi-config package particularly and is build time value
adrianf has quit [Ping timeout: 245 seconds]
<khem>
rburton: SVE and SVE2 should perhaps be added to aarch64 tunable options
<khem>
similar to crypto and crc
adrianf has joined #yocto
florian_kc is now known as florian
mixfix41 has joined #yocto
florian has quit [Ping timeout: 252 seconds]
midicase has joined #yocto
sakoman has quit [Quit: Leaving.]
sakoman has joined #yocto
paulbarker has quit [Quit: Connection closed for inactivity]
goliath has quit [Quit: SIGSEGV]
aak-rookie has quit [Quit: Client closed]
aak-rookie has joined #yocto
<aak-rookie>
lets say i have mymachine.conf and includes:
<aak-rookie>
i want to check like this: "${@bb.utils.contains("MACHINE", "myallmachines", "raspicam", "", d)}" but it doesnt work, checked with "bitbake -e".
adrianf63 has joined #yocto
<cambrian_invader>
shouldn't you check MACHINEOVERRIDES?
adrianf63 has quit [Client Quit]
<aak-rookie>
i need some sleep... u are right, im fool.
nemik has quit [Ping timeout: 245 seconds]
nemik has joined #yocto
<aak-rookie>
i thought it would work but it still didn't. bitbake -e returns MACHINEOVERRIDES="rpi:armv7ve:myallmachines:raspberrypi4:mymachine". i guess it can't find it because there isn't a single value.
florian has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
frieder has quit [Remote host closed the connection]
amitk__ has quit [Ping timeout: 264 seconds]
<rburton>
khem: tell jon he keeps on threatening to rewrite the tunes :)
<khem>
yeah, I am not sure whats minimum arch for sve and sve2
<khem>
I guess v8.2 for sve and v9 for sve2 ?
<rburton>
sounds about right
<khem>
can it exist without crypto ?
<rburton>
no idea technically, but realistically i doubt you'll get sve but no crypto