Hi, Wolfram, On 05.12.2024 10:39, Claudiu Beznea wrote: > Hi, Wolfram, > > On 04.12.2024 23:38, Wolfram Sang wrote: >> Hi Claudiu, >> >>> in the following scenarios: >>> >>> 1/ "earlycon keep_bootcon" were present in bootargs >>> 2/ only "earlycon" was present in bootargs >>> 3/ none of the "earlycon" or "earlycon keep_bootcon" were present in >>> bootargs >> ... >>> Please give it a try on your devices as well. >> >> Will happily do so. Is there something to look for? Except for "it >> works"? Sorry, I noticed I missed to provide a clear answer your question: if boot works for this scenarios we should be OK. > > As this code touches the earlycon functionality, of interest are the 3 > cases highlighted above: > > 1/ "earlycon keep_bootcon" are both present in bootargs > 2/ only "earlycon" is present in bootargs > 3/ none of the "earlycon" or "earlycon keep_bootcon" are present in > bootargs > > One other thing, that I was currently able to test only on RZ/G3S, is to > see how it behaves when the debug serial is described in DT with an alias > other than zero. E.g., on [1] the debug serial alias on RZ/G3S was changed > from 0 to 3. With the new alias (3) there were issues that I've tried to > fix with this series. If you can also check: - it boots in this case and - the serial device with alias zero and the debug serial are both working (tx, rx are working) after boot then we can declare it OK as well. Thank you, Claudiu > > Thank you for checking it, > Claudiu > > [1] > https://lore.kernel.org/all/20241115134401.3893008-6-claudiu.beznea.uj@xxxxxxxxxxxxxx/ > >> >> Happy hacking, >> >> Wolfram >>
