<dryimpact>
ynezz unfortunately the u-boot on that router is too old and doesnt have the pinmux command yet.
<dryimpact>
Is it possible to read the pinmux config from a firmware dump? I already copied everything from the nand, but don't know how I would read the u-boot sections.
<\x>
ahemm
<\x>
so are apk packages gonna be built on the buildbot too?
<ynezz>
dryimpact: next option is md command using u-boot
<ynezz>
dryimpact: so you need to figure out the address of that pinmux register, read out the content and decode the configuration manually
owrt-images-builds has quit [Quit: buildmaster reconfigured: bot disconnecting]
owrt-images-builds has joined #openwrt-devel
<ynezz>
ccache: -- Downloading Xxhash from the internet since Xxhash>=0.8.0 was not found locally and DEPS=AUTO
<ynezz>
shouldn't we build xxhash instead?
<ynezz>
nice backdoor btw :P
mrkiko has joined #openwrt-devel
<mrkiko>
to transition to the new APK world - is enough to enable "use apk to built distribution", and have apk-mbedtls enabled and opkg disabled? Or are there otherthings I need to change?
<Habbie>
one small diff for man, one big step for openwrtkind
<mrkiko>
ynezz: thanks. But I was asking in the context of migration a pre-switch config via "make oldconfig2
<mrkiko>
And also - on a new config the system seems to keep both apk and opkg selected, is this useful for the transition or may I remove opkg entirely?
<ynezz>
opkg can be removed, yes
<mrkiko>
thanks
n3ph has quit [Ping timeout: 480 seconds]
<dryimpact>
ynezz Thank you. I will try :)
<mrkiko>
robimarko: thanks for reporting this in the ML
<KanjiMonster>
\x: there isn't anything against custom snapshots per se, it's just that the kernel ABI changes based on the configuration, which is where the hash comes from, and if you do your own build, the kernel configuration is likely different
<KanjiMonster>
if you don't have any local kernel changes in your snapshot, there is a certain probability that you can generate a compatible kernel by enabling ALL_KMODS when initially configuring your build, which should then end up the same kernel config and hash
<schmars[m]>
aparcar i'm building a custom package feed with the SDK and some architectures don't seem to generate the Packages file (others do). what's the signing story, do i sign packages.adb instead now that APK is default?
<KanjiMonster>
\x: modversions is disabled in openwrt, so there is no runtime check
<aparcar[m]>
schmars: I'm right now rather busy with other work but please let me know if you need help with anything. I'm not following the full conversation here
<schmars[m]>
aparcar: do i simply sign packages.adb as i previously signed Packages?
aiyion has joined #openwrt-devel
aiyion_ has quit [Ping timeout: 480 seconds]
<aparcar[m]>
schmars: no you use adbsign which is part of apk
<KanjiMonster>
aparcar[m]: when I tried looking into how stuff is signed, I read signall.sh as "signal-l.sh" and it didn't register to me as a relevant script at first
<aparcar[m]>
Hehe
maciekb7218 has quit [Quit: bye]
lucenera has quit [Read error: Connection reset by peer]
<russell-->
i updated a ubnt,edgerouter-x to master branch ... it would be nice if there was a method to do the compat_version 1.1->2.0 change without having physical access, i'm imagining updating sysupgrade scripts to accept the 2.0 firmwre and do the right thing
goliath has quit [Quit: SIGSEGV]
gromero has quit [Remote host closed the connection]