alessioigor has quit [Remote host closed the connection]
alessioigor has joined #yocto
<khem>
RP: in some components this might be but for subset we need it has everything we need
<Xogium>
is there a wic recipe (not sure if one can call them this way), that allows boot on both legacy bios and modern uefi systems ? A bit like mkhybridiso, but not iso form
rfuentess has joined #yocto
Kubu_work has joined #yocto
MrFrank has quit [Remote host closed the connection]
grma has joined #yocto
frieder has joined #yocto
<LetoThe2nd>
yo dudX
<landgraf>
(^_^)/
<Xogium>
hiya LetoThe2nd :)
<mckoan>
Hello LetoThe2nd, landgraf, everyone
<Xogium>
well, I'm gonna ask this anyway because why not... But is there some way to get tutored in yocto ? Either one on one or in a very small group ? I do what I can with the manual, but I admit that it's still very difficult to learn all on my own
<Xogium>
mckoan: huh, those lesons do look cool :O but yeah costly not to mention pricy just for me ^^
<Xogium>
still, it's neat
mvlad has joined #yocto
prabhakar has joined #yocto
prabhakarlad has joined #yocto
sakman has joined #yocto
<LetoThe2nd>
Xogium: for free or low cost, its essentially the manual, the various YouTube resources (of varying quality including my own), and the Yocto Project Summit.
<Xogium>
hmm makes sense
<Xogium>
I wasn't trying to imply that the price was unreasonable btw it makes sense when taken in a company context
<LetoThe2nd>
Xogium: yeah we all understand. But the point is that almost nobody does Yocto "for fun", it is almost always a professional context.
<Xogium>
yeah
<Xogium>
I get that
<Xogium>
I mean, I want to learn it both for my own things and also because, well... It looks like not a lot of folks are interested in buildroot, so I'm kind of hoping that by learning yocto I'd have more luck at getting a job
sakman has quit [Ping timeout: 246 seconds]
florian has joined #yocto
<LetoThe2nd>
Xogium: oh there definitely are a lot of people working on and using buildroot too - it's just a different use case.
<LetoThe2nd>
Xogium: yocto talent is definitely sought after these days.
<Xogium>
damn, I must be unlucky as all hell in that case
<LetoThe2nd>
it of course depends a bit on the personal whereabout and flexibility, its definitely a skill in demand.
florian_kc has joined #yocto
<Xogium>
yeah that makes sense
schtobia has quit [Quit: Bye!]
schtobia has joined #yocto
alperak has joined #yocto
alperak has quit [Quit: Client closed]
alessioigor has quit [Quit: alessioigor]
alperak has joined #yocto
alessioigor has joined #yocto
leon-anavi has joined #yocto
Martin42 has joined #yocto
<Martin42>
Hello community, I have an out of tree kernel module, which also provides a header file that has to be included in the SDK. The module.bbclass only install the module file, but how do I install the header into the SDK? Thanks :)
<rburton>
Martin42: package the header as usual in the recipe, and then add the -dev package to the SDK using TOOLCHAIN_TARGET_TASK
<Martin42>
Thanks rburton :) I will give it a try. Do you recall if there were changes between honister and langdale regarding kernel modules and the SDK? Cause I am in the process of migrating and just packaging the -dev package was enugh on honister.
<rburton>
not afaik
<rburton>
i was about to say, packaging the header in the -dev should work
<rburton>
because if the module is in the rootfs then the dev will be in the sdk
otavio has joined #yocto
<Martin42>
Until now on honister I was not using any of MACHINE_ESSENTIAL_EXTRA_RDEPENDS - MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS - MACHINE_EXTRA_RDEPENDS - MACHINE_EXTRA_RRECOMMENDS, but rather using IMAGE_INSTALL to include my kernel modules. Maybe that also makes a difference here.
<rburton>
thats fine
<rburton>
you know langdale is EOL right
<rburton>
kirkstone is supported until 2026
<Xogium>
and there's gonna be a new shiny lts in may too
<Xogium>
^^
jmiehe has joined #yocto
<Martin42>
rburton thanks for the warning, however I am stuck on whatever latest version Xilinx packages with their FPGA chips ;(
<kanavin>
Martin42, all of xilinx layers are open source, you don't need to use what they package
<rburton>
weeelllll if you want support and the xilinx layers are famously complex you kind of do
<rburton>
i believe the next release will be actually on a LTS
<Xogium>
that's kinda what I like about st, their releases always use lts softwares
<Martin42>
rburton kanavin agreed, usually the x.1 release is LTS, the x.2 is intermediate, I am currently jumping onto 2023.2 and once available onto 2024.1 (which is hopefully LTS again).
frieder has quit [Remote host closed the connection]
<Xogium>
they follow along with stable releases, but they don't actively use them in a release of their own
<kanavin>
but then you should ask them to support you, not the 'community'
<kanavin>
otherwise, what's the point in using their outdated stuff
<Martin42>
kanavin the problem I had was with Yocto and not with Xilinx, probably just something small I as developer overlooked, so I appreciate the help of the community pointing me into the right direction
<rob_w>
can i ship a 2nd kernel in a image , would love to build a image for 2 different hardwares with 2 different kernels and decide on u-boot which one to boot
tnovotny has joined #yocto
<RP>
rburton: it is a beautiful place
<ablu>
rob_w: Hm... In general you should probably ship a single kernel and only provide 2 device-trees.
arisut has quit [Remote host closed the connection]
arisut has joined #yocto
Martin42 has quit [Quit: Client closed]
Guest44 has joined #yocto
Guest44 has left #yocto [#yocto]
OnkelUlla has joined #yocto
<rob_w>
ablu: having trouble porting a hardware to the same kernel as other hardware ... hence my question
<ablu>
rob_w: You can certainly hack u-boot or boot scripts to work with multiple kernels. But I am not sure if that will become particulary maintainable.
<rob_w>
not worried about u-boot .. that will be fine, but i need to add the 2nd kernel in theory
<mcfrisk>
rob_w: two kernels, two sets of modules in initramfs, rootfs etc it gets messy pretty soon
leon-anavi has quit [Remote host closed the connection]
<mcfrisk>
with multiconfig multiple machines can be compiled in one go and dependencies can be expressed between them, also multiple kernel versions then
leon-anavi has joined #yocto
<rob_w>
mcfrisk: agreed ... back to porting
jstephan has joined #yocto
<rob_w>
ahh i just tested copying the other kernel into my image, works .. damn it
* rob_w
curses TI
Guest18 has joined #yocto
<Guest18>
Hi all,
<Guest18>
I am using warrior based build and i have include CORE_IMAGE_EXTRA_INSTALL += "python3-fail2ban"
<Guest18>
which is using python3-fail2ban_0.10.4.0 but when i am running the fail2ban service getting error as
<Guest18>
Can someone help me how i can fix this issue in the warrior ? As if i checkout to other branches of meta-security(zeus,dunfell) i am getting conflict errors while building.
<Guest18>
Posting this again as due to some network issue i lost my connection
<jstephan>
Hi all, I am trying to fix bug #15162 (multiple sources in SRC_URI with devtool)
<rburton>
Guest18: were you here a week or so ago with sshd problems related to init.d/functions?
<rburton>
Guest18: whatever your distro is, it's shipping a custom /etc/init.d/functions that _needs_ bash. complain to whoever provided your distro.
<rburton>
also warrior was end-of-life in 2020 so please upgrade if you're using this in production
Guest20 has joined #yocto
Guest18 has quit [Ping timeout: 250 seconds]
linfax has quit [Ping timeout: 252 seconds]
rob_w has quit [Remote host closed the connection]
Dr_Who has joined #yocto
<RP>
Looks like groups.io has managed to make a blackhole list and all email is now going to spam for me :(
amitk_ has joined #yocto
<rburton>
whoops
<LetoThe2nd>
RP: yeah they are having some fun these days. first I needed to re-verify, and now they are spamming me with notifications about all oe/yp ml subscription changes (and I can't find a way to disable that)
<simonew>
Hi all, so I started looking into Bug 12388. When ckecking qemu and the include files for it, I wondered: Would it make sense in generall to add a tune-x86-64-v4.inc as well? the v3 was introduced when qemu added support for it. The same is now true for v4.
lefty has joined #yocto
tnovotny has quit [Quit: Leaving]
<rburton>
yes
lefty1 has joined #yocto
lefty has quit [Ping timeout: 250 seconds]
<simonew>
the yes is directed at me or to someone else?
prabhakarlad has quit [Quit: Client closed]
<rburton>
you :)
<rburton>
(sorry)
<simonew>
:) Ok I will look into it then. Normally would I create a Bugzilla issue for this?
<rburton>
filing a bug can be useful in case you don't finish, but isn't essential
<simonew>
Ok, thx
<rburton>
ah v4 is avx512, basically
prabhakar has quit [Ping timeout: 264 seconds]
prabhakarlad has joined #yocto
prabhakar has joined #yocto
amitk_ has quit [Ping timeout: 245 seconds]
lefty1 has left #yocto [#yocto]
vladest has quit [Ping timeout: 276 seconds]
jmd has joined #yocto
rfuentess has quit [Remote host closed the connection]
florian_kc has quit [Ping timeout: 252 seconds]
florian has quit [Quit: Ex-Chat]
alperak has quit [Quit: Client closed]
prabhakarlad has quit [Quit: Client closed]
vladest has joined #yocto
alessioigor has quit [Remote host closed the connection]
alessioigor has joined #yocto
alperak has joined #yocto
mckoan is now known as mckoan|away
<rburton>
FWIW i have most of a libunwind 1.8.0 upgrade _with a test suite_ done
Kubu_work has quit [Quit: Leaving.]
Guest20 has quit [Quit: Client closed]
<RP>
rburton: nice!
alperak has quit [Quit: Client closed]
kpo has joined #yocto
alperak has joined #yocto
sakman has quit [Ping timeout: 264 seconds]
leon-anavi has quit [Quit: Leaving]
prabhakar has quit [Ping timeout: 252 seconds]
jmd has quit [Remote host closed the connection]
jmd has joined #yocto
prabhakarlad has joined #yocto
prabhakar has joined #yocto
wicki has joined #yocto
prabhakarlad has quit [Ping timeout: 250 seconds]
prabhakar has quit [Ping timeout: 260 seconds]
ptsneves has joined #yocto
xmn has quit [Ping timeout: 245 seconds]
vladest1 has joined #yocto
florian_kc has joined #yocto
vladest has quit [Read error: Connection reset by peer]
vladest1 is now known as vladest
vladest1 has joined #yocto
vladest has quit [Ping timeout: 260 seconds]
vladest1 is now known as vladest
ray-san has joined #yocto
sakman has joined #yocto
vladest1 has joined #yocto
vladest has quit [Ping timeout: 255 seconds]
vladest1 is now known as vladest
vladest has quit [Read error: Connection reset by peer]
vladest has joined #yocto
smooge is now known as NephewFred
Haxxa has quit [Quit: Haxxa flies away.]
zwelch has quit [Ping timeout: 256 seconds]
Haxxa has joined #yocto
vladest has quit [Quit: vladest]
vladest has joined #yocto
vladest has quit [Ping timeout: 245 seconds]
zwelch has joined #yocto
vladest has joined #yocto
Shaun has quit [Quit: Lost terminal]
vladest1 has joined #yocto
florian_kc has quit [Ping timeout: 260 seconds]
vladest has quit [Ping timeout: 245 seconds]
vladest1 is now known as vladest
MrFrank has joined #yocto
alessioigor has quit [Quit: alessioigor]
alperak has quit [Quit: Client closed]
amitk has quit [Ping timeout: 252 seconds]
ptsneves has quit [Read error: Connection reset by peer]
ptsneves1 has joined #yocto
simonew has quit [Quit: Konversation terminated!]
ptsneves1 is now known as ptsneves
florian_kc has joined #yocto
Kubu_work has joined #yocto
Shaun has joined #yocto
jmd has quit [Remote host closed the connection]
prabhakarlad has joined #yocto
prabhakar has joined #yocto
ptsneves has quit [Ping timeout: 264 seconds]
vladest has quit [Remote host closed the connection]
vmeson has quit [Read error: Connection reset by peer]
arisut has quit [Quit: install gentoo]
arisut has joined #yocto
vmeson has joined #yocto
vladest has joined #yocto
prabhakar has quit [Ping timeout: 252 seconds]
Danct12 has quit [Remote host closed the connection]