digetx has quit [Killed (NickServ (GHOST command used by digetx_))]
digetx has joined #tegra
marvin24_ has quit [Ping timeout: 252 seconds]
marvin24 has joined #tegra
crabbedhaloablut has quit [Ping timeout: 244 seconds]
crabbedhaloablut has joined #tegra
<pgwipeout[m]>
Heh, probably was fixed when I changed from pull_down to pull_none. Should have checked that again.
crabbedhaloablut has quit [Remote host closed the connection]
crabbedhaloablut has joined #tegra
digetx has quit [Killed (NickServ (GHOST command used by digetx_))]
digetx has joined #tegra
torez has joined #tegra
quarkyalice_ has quit [Remote host closed the connection]
quarkyalice has joined #tegra
quarkyalice has quit [Changing host]
quarkyalice has joined #tegra
JakeSays has joined #tegra
quarkyalice_ has joined #tegra
quarkyalice_ has quit [Remote host closed the connection]
quarkyalice_ has joined #tegra
gouchi has joined #tegra
torez has quit [Quit: torez]
quarkyalice_ has quit [Ping timeout: 252 seconds]
quarkyalice has quit [Ping timeout: 252 seconds]
quarkyalice has joined #tegra
quarkyalice has quit [Changing host]
quarkyalice has joined #tegra
quarkyalice_ has joined #tegra
quarkyalice_ has quit [Changing host]
quarkyalice_ has joined #tegra
quarkyalice_ has quit [Ping timeout: 252 seconds]
quarkyalice_ has joined #tegra
quarkyalice_ has quit [Remote host closed the connection]
quarkyalice_ has joined #tegra
quarkyalice_ has quit [Changing host]
quarkyalice_ has joined #tegra
gouchi has quit [Remote host closed the connection]
<digetx>
pgwipeout[m]: the lm90 interrupt was broken on all tegra boards anyways, they all were getting the non-stopping interrupt because it should be edge-triggered
<digetx>
that interrupt behaviour is documented in the sensor datasheet
<DavidHeidelberg>
digetx do you want it only against master branch or also setup another branch?
<digetx>
master only
quarkyalice_ has quit [Quit: Leaving]
quarkyalice_ has joined #tegra
quarkyalice_ has quit [Changing host]
quarkyalice_ has joined #tegra
<DavidHeidelberg>
digetx are u interested in building with multiple compilers matrix or just regular default gcc is enough?
<DavidHeidelberg>
btw. I just realized I'll love one feature of it. And it's always hard to spot, when did you updated git repo from Web UI, since you rebase, so now it'll be nicely visible by pushed release
<DavidHeidelberg>
it gets overwritten everytime it's build
quarkyalice_ has quit [Ping timeout: 246 seconds]
<DavidHeidelberg>
sent PR, just waiting for final CI test finishes on my okias/master
<digetx>
it could be good to have kernel compiled by older stable compiler and the most recent, for example thumb2 kernel build was broken using gcc10+ for a long time
<DavidHeidelberg>
digetx so first options, one standard build, then THUMB2 mode? CONFIG_THUMB2_KERNEL ?
<DavidHeidelberg>
or just give me a list of scenarions with CONFIG_ values and I'll make a build matrix
<DavidHeidelberg>
just thinking not sure about compilers, because the script uses some debian/buntu crosscompilation toolchain, so not sure how clear would be implement that
<digetx>
it also should be a special config focused on optimizing kernel image size, shouldn't it? will you use the pmOS config?
<DavidHeidelberg>
(dtbs will take longer I guess)
<DavidHeidelberg>
for Nexus 7 2012, for sure at some point
<DavidHeidelberg>
I could eventually create job for N7, curl config from pmOS pmaports and build it with it
<DavidHeidelberg>
(which is very good idea, because it will make pmaports update a piece of cake)
<DavidHeidelberg>
btw. tuxmake builds can be reproducible (if is used same command as saved in build done by CI)
<digetx>
DavidHeidelberg: why is it checking non-tegra dtbs? it should happen using tegra_defconfig
<DavidHeidelberg>
it's always check everything, which is kinda ... pain... but it's still searchable.. meh.. I know, not great
<DavidHeidelberg>
I think it takes whole architecture, the KBUILD_DEFCONFIG is set to "tegra_defconfig"
crabbedhaloablut has quit [Ping timeout: 244 seconds]
crabbedhaloablut has joined #tegra
<DavidHeidelberg>
well, still the kernel gets generated in 22 minutes, dts will take approx more than hour, but I didn't noticed that parallel jobs has any effect on speed of other jobs..
<DavidHeidelberg>
I think limit is 20 concurrent job, so we're at 3/20 :)
<digetx>
the non-tegra dtbs are not interesting, perhaps better to skip dtbs_check then?
<digetx>
it actually checks only tegra dtbs for me locally
<DavidHeidelberg>
digetx that's weird, what you doing differently?
<DavidHeidelberg>
status=0
<DavidHeidelberg>
make -j3 dtbs || status=1
<DavidHeidelberg>
make -j3 dtbs_check || status=1
<digetx>
make defconfig
<digetx>
looks suspicious, shouldn't it be make $KBUILD_DEFCONFIG?
<DavidHeidelberg>
nwm, oh I see "2021-07-09T22:38:15.1143268Z *** Default configuration is based on 'multi_v7_defconfig'"
<DavidHeidelberg>
digetx well, it should use exported KBUILD_DEFCONFIG
<DavidHeidelberg>
but it doesn't use it in this scenario...
<digetx>
it doesn't use KBUILD_DEFCONFIG
<DavidHeidelberg>
oh... btw. what about dt_bindings_check, I assume there it doesn't matter
<DavidHeidelberg>
or should it also get make $KBUILD_DEFCONFIG ?
<digetx>
dt_bindings_check shouldn't be needed
<DavidHeidelberg>
ok, seems to be fixed
<DavidHeidelberg>
pushed changes to ci for merge
quarkyalice_ has joined #tegra
quarkyalice_ has quit [Changing host]
quarkyalice_ has joined #tegra
<DavidHeidelberg>
I'm little bit playing in my head with idea like -> having one default tegra_defconfig and tegra_defconfig + all debug stuff + some initrd, which gets bundled, kernel gets uploaded to device and it'll do like "self testing" of everything which can be tested by automatization
<DavidHeidelberg>
digetx cool, dtbs done in 7 minutes, much better than 1h+
<digetx>
DavidHeidelberg: is PR ready now?
<DavidHeidelberg>
yup, kernel build is without change and DTS just compiled