mansandersson86 has quit [Remote host closed the connection]
mansandersson86 has joined #yocto
Clayton has joined #yocto
Clayton has quit [Client Quit]
tlwoerner has quit [Ping timeout: 252 seconds]
tlwoerner has joined #yocto
davidinux has quit [Ping timeout: 265 seconds]
davidinux has joined #yocto
starblue has quit [Ping timeout: 252 seconds]
starblue has joined #yocto
jclsn has quit [Ping timeout: 272 seconds]
jclsn has joined #yocto
LainExperiments has joined #yocto
LainExperiments has quit [Quit: Client closed]
LainExperiments has joined #yocto
LainExperiments3 has joined #yocto
LainExperiments has quit [Ping timeout: 240 seconds]
Vonter has quit [Ping timeout: 260 seconds]
LainExperiments3 has quit [Quit: Client closed]
ericksonu has quit [Ping timeout: 252 seconds]
ericksonu has joined #yocto
LainExperiments has joined #yocto
LainExperiments4 has joined #yocto
LainExperiments has quit [Ping timeout: 240 seconds]
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #yocto
LainExperiments4 has quit [Ping timeout: 240 seconds]
LainExperiments has joined #yocto
ericksonu has quit [Ping timeout: 252 seconds]
LainExperiments has quit [Ping timeout: 240 seconds]
LainExperiments has joined #yocto
rob_w has joined #yocto
geoffhp has joined #yocto
eduter55 has joined #yocto
alessio has joined #yocto
eduter73 has joined #yocto
eduter73 has quit [Client Quit]
eduter55 has quit [Ping timeout: 240 seconds]
dmoseley_ has joined #yocto
dmoseley has quit [Ping timeout: 248 seconds]
savolla has joined #yocto
nzingile has joined #yocto
leon-anavi has joined #yocto
olani has quit [Remote host closed the connection]
<nzingile>
Hi.. all just to check if people is "alive" here :)
eduter has joined #yocto
olani has joined #yocto
LainExperiments has quit [Quit: Client closed]
olani has quit [Remote host closed the connection]
olani has joined #yocto
mckoan|away is now known as mckoan
<mckoan>
good morning
frgo has joined #yocto
<eduter>
Morning everyone here.
<eduter>
I am about to start the interesting task of updating my Yocto project from "kirkstone" to "scarthgap". I am using a manifest where I specify in there the 10/11 repositories I am fetching "kirkstone" compatible, using the "google repo" tool.
<eduter>
I have already read through all the "migration notes" for all the releases in between (including scarthgap 5.0 of course).
<eduter>
Does anyone here has a good tip on how to approach this process? it could be a link to a website, a youtube tutorial, or any comment would be appreciate since I consider myself a newbie in Yocto (just start using it 3 weeks ago), and even "basic" stuff for you might be "gold knowledge" for me to try to approach this task in an efficient manner.
<eduter>
Thanks in advance for any tip :-)
<mckoan>
eduter: the main issue will be adapting the BSP part that is not Yocto related
<mckoan>
eduter: what's your MACHINE?
<mcfrisk>
eduter: in the end you need to fix the update to compile, then to pass all tests that you have. So updating in smaller steps, from release to next, may work, or a big bang of updating everything. In the end all SW components and overall product need to be reviewed and tested so that they work as you want.
<eduter>
mckoan Thanks for you answer. I am using hardware from vendor PHYTEC, one of the repos I am fetching is maintained by them. The machine is aarch64.
<eduter>
mcfrisk Thanks for your answer and time mcfrisk. I was considering doing an upgrade from LTS to LTS. I do not have a lot of recipes, in my custom layer.
<mcfrisk>
with BSPs, it may be needed to reduce their scope on your platform. For example not updating BSP and keeping any SW there as is with only updates to make them compile.
<eduter>
mcfrisk of course, running tests and smoke tests that have to succeed is part of the plan:-)
<mcfrisk>
or if BSP vendors supports, also updating their delivery from old LTS to new. Doing both may bring too many changes to test
<mcfrisk>
with new BSP delivery it could be possible to 'redo' the whole product config until end result is good enough.
<mcfrisk>
every update and every product config is different, it's just a lot of hard work with lots of interesting problems to solve
<eduter>
mcfrisk Ok. Need to leave now for 1 hour, but I will come back and reply. But how long this process could take?
<eduter>
mcfrisk just an approximation from your experience... I am asking just out of curiosity nothing else
<mcfrisk>
from days to weeks to months, depending on product complexity
<eduter>
mcfrisk got you. Thanks a lot for your time and answers. I may post more quesitons later. Do you recommend any tutorial or reading besides the official migration notes?
<mcfrisk>
the updates get easier once you've done a few. I've learned to limit impact of layers, e.g. BSP, with BBMASK if necessary, to only take what is really needed which helps with distro side updates then
<mcfrisk>
migration notes, and just start doing it, either release at a time or the full big bang. end result will be the same
<eduter>
mcfrisk I will investigate this BBMASK... this is the kind of thing I have never heard of that could be gold info for a newbie like me. Thanks. Will be back in a minute