Chaser has quit [Quit: My Unrecognized Mac has gone to sleep. ZZZzzz…]
Danct12 has joined #yocto
aduskett has joined #yocto
aduskett has quit [Client Quit]
xmn has quit [Ping timeout: 252 seconds]
ray-san has joined #yocto
mckoan|away is now known as mckoan
<mckoan>
good morning
zpfvo has joined #yocto
rber|res has joined #yocto
leon-anavi has joined #yocto
alimon has quit [Ping timeout: 265 seconds]
sgw has quit [Ping timeout: 252 seconds]
sgw has joined #yocto
Kubu_work has joined #yocto
frieder has joined #yocto
angeloc__ has joined #yocto
albeu has joined #yocto
Guest68 has joined #yocto
gioyik has joined #yocto
wojci has quit [Ping timeout: 252 seconds]
wojci has joined #yocto
<Guest68>
Hello everyone! I have conceptual question! Is it possible to take NXP's repository where yocto classes, settings and recipes are in built, I take my meta-layer customize some recipes from NXP along with some own machine configs, and having all the packages I define in my meta-layer to be included and not from NXP?
dmoseley has joined #yocto
dmoseley_ has quit [Ping timeout: 255 seconds]
gioyik has quit [Remote host closed the connection]
gioyik has joined #yocto
bhstalel has joined #yocto
<bhstalel>
Hello everyone,
<bhstalel>
Someone asked me "why SRCREV is not enough ?, Why branch parameter is needed ?"
Jones42_ has joined #yocto
Jones42 has joined #yocto
<mckoan>
guest68: theoretically it is doable, however this way you are breaking the Yocto operating paradigm and duplicating code. You should also consider NXP's EULA. theoretically it is doable, however this way you are breaking the Yocto operating paradigm and duplicating the code. Also you should consider the NXP EULA.
<mckoan>
guest68: I don't see the reason to do this and I advise against it
Jones42_ has quit [Ping timeout: 252 seconds]
Chaser has joined #yocto
<Guest68>
mcfrisk I want to separate my layer from NXPs so I can update to latest NXP with git pull every now and then without disturbing or corrupting my changes and settings
<mcfrisk>
I would review vendor layers very closely and use BBMASK to disable changes that I don't want or need, and then use as much from maintained open source layers, and update them on demand. And I would develop on master branch instead of a stable/LTS branch. I would switch to stable/LTS branch only once product ships. If at all.
<AdrianF>
guest68: The official answer is probably what mckoan wrote. But as a second opinion I can say that I never successfully used a BSP from a vendor. I always ended up with copying a few files from the vendor BSP into my layer and maintain them independently. It depends on the vendor and the exact BSP and also on the life cycle of your products if you
<AdrianF>
can use official BSPs or not.
<mckoan>
AdrianF: that's exacly how NOT tu use Yocto :-(
<mcfrisk>
a lot of the vendor BSP recipes needs to be modified at least with bbappends for product. same for machine, SoC etc configs. Some issues are clear bugs and it makes sense to try to upstream them to vendor. But vendors do a lot of questionable things, like fork/take over high level SW components and thus end up locking to certain, usually old, yocto release branch. To break this lock-in, product configs
<mcfrisk>
need to limit what they take from the BSP layer, e.g. disable changes to openssl but allow building u-boot and kernel.
<Guest68>
mcfrisk mckoan I have used your AdrianF approach. However it becomes very cumbersome if one wants to upstream ones system. That's why I wanted to separate them to make it more easily manageable especially for upstreams
<mcfrisk>
review the full SW stack, disable full BSP layer with BBMASK, then enable only what is absolutely needed. compare against upstream SW components and yocto community layers. What did vendor change and why? The initial POC with full vendor layers is easy but then reviewing and polishing everything for full product and long term maintenance is a lot harder
mbulut has joined #yocto
debbiemartin has joined #yocto
mbulut_ has joined #yocto
mbulut has quit [Read error: Connection reset by peer]
<debbiemartin>
rburton, it needs extra config (beyond just setting TOOLCHAIN) to build the kernel with clang as detailed here: https://github.com/kraj/meta-clang?tab=readme-ov-file#kernel-build-with-clang. It uses linux-rockchip as an example. However, I'm facing errors when I add that config with linux-yocto-rt as my preferred provider.
florian has joined #yocto
<Guest68>
mckoan mcfrisk AdrianF thank you very much for your insightful inputs
<mckoan>
guest68: good luck
wojci has quit [Remote host closed the connection]
wojci has joined #yocto
rfuentess has quit [Ping timeout: 260 seconds]
rfuentess has joined #yocto
wojci has quit [Remote host closed the connection]
Guest68 has quit [Quit: Client closed]
florian_kc has joined #yocto
frieder has quit [Ping timeout: 260 seconds]
<kanavin>
bhstalel, because it helps to see which branch the SRCREV is on, so that you don't accidentally update SRCREV to some dangling commit which is not on a branch, or on the wrong branch (e.g. someone's private hacks). It's a kind of supply chain security.
* RP
is happy to have that bitbake toaster patch series posted
frieder has joined #yocto
gioyik has quit [Ping timeout: 260 seconds]
ehussain has quit [Ping timeout: 252 seconds]
<kanavin>
seems like a large scale refactor?
<kanavin>
I was wondering about those fixup fixup fixup commits in master-next
<kanavin>
they're actually a good sign, it happens when someone is on a roll and in the zone :)
ehussain has joined #yocto
gioyik has joined #yocto
ptatrai has joined #yocto
<RP>
kanavin: the testsuite was poor in places, it needed a lot of help
<RP>
kanavin: my local testing exposed totally different timing issues to what the autobuilder did.
<RP>
kanavin: by removing the sleep() calls, the testsuite execution time is now about 12 mins down from 45 mins
<kanavin>
sleep() in tests is almost always a red flag
<kanavin>
I've been fighting with people in mbition over this, they just wouldn't get why is that.
<RP>
kanavin: agreed, I should have spotted some of this during review previously. Some I let through as it was good to at least have some code to start from
<RP>
kanavin: I've mostly got rid of them now. There are some isolated cases which are probably ok
<RP>
(in a retry loop waiting for the browser to do something)
<kanavin>
maybe it's not a red flag when one is cutting things with a laser, or engaging car brakes in a realtime baremetal context, but that's not what we do :)
<RP>
kanavin: you'd be truly appalled at what some of the code in there was doing. I think it is safe to say I've improved it from that perspective
<RP>
sadly more work remains
<kanavin>
RP being polite in that british way :D
<RP>
kanavin: it was great to have a test suite running on the autobuilder at all
<kanavin>
I think I've actually picked up some of those turns of phrase from you and rburton, it's a good thing when I need to be gently negative.
<RP>
kanavin: agreed, it can be quite a powerful tool in some ways
<kanavin>
we're not native speakers, most of us, so those nuances of meaning aren't so easy
amitk has quit [Ping timeout: 252 seconds]
<kanavin>
meaning and tone
<RP>
kanavin: definitely. It isn't helped that there are different ways people use the language too. Brits do tend to use it a little differently to Americans for example :)
<RP>
kanavin: I'm also from an area with a strong local dialect too which is fairly distinct even within England
DixitP has joined #yocto
<kanavin>
RP: can you do 'posh' southern english? :D
<kanavin>
my way of speaking is a mix of russian english (a cringe-fest from my POV, I can't stand hearing myself talk) and finnish english, as that's where I've actually started to talk every day.
<RP>
kanavin: locals think I'm not local, my accent filters out a lot of northern elements much of the time. Apparently when I get suitably worked up about something the northern elements creep in :)
<RP>
kanavin: I guess what I do switch is the dialect as there are a lot of expressions/words that only really work locally
<RP>
kanavin: "Howay man!" :) (which is gender neutral)
amitk has joined #yocto
ehussain has quit [Remote host closed the connection]
<rburton>
i have two builds which _should_ be identical but the spdx files are all different
<JPEW>
rburton: It's the taskhash. Is this SPDX 2.2 or 3.0?
<rburton>
3
<rburton>
hm ok the taskhash most likely did change, the final binary output didn't
<rburton>
i'll nuke the spdx and compare again
rfuentess has quit [Remote host closed the connection]
<JPEW>
Ya. It's tricky to make them unique enough that the won't conflict while keeping them binary identical. With SPDX 3, I was able to fix one major problem though in that the documents aren't linked by spdxId, but rather by a special "OE Alias" (which doesn't use the task hash and is removed in the final document). This fixes a lot of linking errors we had in SPDX 2.2 where the wrong ID's were being referenced
tgamblin_ is now known as tgamblin
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Xagen has joined #yocto
ray-san has quit [Ping timeout: 252 seconds]
rob_w has joined #yocto
gioyik has quit [Ping timeout: 260 seconds]
gioyik has joined #yocto
rber|res has quit [Remote host closed the connection]
gioyik has quit [Remote host closed the connection]
gioyik has joined #yocto
rob_w has quit [Read error: Connection reset by peer]
Tyaku has quit [Quit: Lost terminal]
florian_kc has quit [Ping timeout: 252 seconds]
druppy has joined #yocto
frieder has quit [Remote host closed the connection]
Chaser has quit [Quit: My Unrecognized Mac has gone to sleep. ZZZzzz…]
florian has quit [Quit: Ex-Chat]
angeloc__ has quit [Ping timeout: 252 seconds]
Guest44 has joined #yocto
Guest44 has quit [Client Quit]
xmn has joined #yocto
Kubu_work has quit [Quit: Leaving.]
rob_w has joined #yocto
zpfvo has quit [Remote host closed the connection]
gioyik has quit [Ping timeout: 260 seconds]
gioyik has joined #yocto
gioyik has quit [Ping timeout: 260 seconds]
Jones42 has quit [Read error: Connection reset by peer]
druppy has quit [Ping timeout: 252 seconds]
gioyik has joined #yocto
mischief has quit [Ping timeout: 246 seconds]
mischief has joined #yocto
gioyik has quit [Remote host closed the connection]
gioyik has joined #yocto
leon-anavi has quit [Quit: Leaving]
<AdrianF>
We are trying to reproduce the ppc related bug https://bugzilla.yoctoproject.org/show_bug.cgi?id=15625. But it passes successfully on all the machines we tried. We are not yet familiar with the details of the AB. Could it be a timeout which terminates the test too early on the AB?
florian_kc has joined #yocto
mischief has quit [Ping timeout: 245 seconds]
debbiemartin has quit [Quit: Connection closed for inactivity]
gioyik has quit [Ping timeout: 260 seconds]
florian_kc has quit [Quit: Ex-Chat]
mischief has joined #yocto
florian has joined #yocto
PhoenixMage has quit [Ping timeout: 265 seconds]
gspbirel56 has quit [Ping timeout: 252 seconds]
gioyik has joined #yocto
albeu has quit [Quit: albeu]
gioyik has quit [Remote host closed the connection]
gioyik has joined #yocto
pidge has quit [Ping timeout: 246 seconds]
mischief has quit [Ping timeout: 248 seconds]
ptsneves has joined #yocto
mischief has joined #yocto
druppy has joined #yocto
ptsneves has quit [Read error: Connection reset by peer]
ptsneves has joined #yocto
gspbirel56 has joined #yocto
pidge has joined #yocto
ptsneves has quit [Ping timeout: 252 seconds]
gspbirel56 has quit [Ping timeout: 252 seconds]
pidge has quit [Ping timeout: 252 seconds]
jmiehe has quit [Quit: jmiehe]
<RP>
AdrianF: no, the timeout would show very differently. It is more likely load from other jobs on the system affects the test timings
pidge has joined #yocto
gioyik has quit [Ping timeout: 260 seconds]
<AdrianF>
RP: Thank you. We will investigate further.
gioyik has joined #yocto
ehussain has joined #yocto
gioyik has quit [Ping timeout: 260 seconds]
Chaser has joined #yocto
Saur_Home has joined #yocto
gioyik has joined #yocto
gioyik has quit [Ping timeout: 260 seconds]
<rburton>
AdrianF: if you're running stuff in containers, you can limit the cpu time the guest is allowed
gspbirel56 has joined #yocto
gspbirel56 has quit [Ping timeout: 252 seconds]
druppy has quit [Ping timeout: 252 seconds]
olani- has joined #yocto
olani_ has joined #yocto
Saur_Home46 has joined #yocto
gioyik has joined #yocto
Saur_Home has quit [Ping timeout: 256 seconds]
jmd has quit [Remote host closed the connection]
sakman has quit [Quit: Leaving]
gioyik has quit [Remote host closed the connection]
gioyik has joined #yocto
albeu has joined #yocto
Chaser has quit [Quit: My Unrecognized Mac has gone to sleep. ZZZzzz…]