guerby has quit [Read error: Connection reset by peer]
guerby has joined #openwrt-devel
opal has quit [Ping timeout: 240 seconds]
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
opal has joined #openwrt-devel
nitdega has quit [Quit: ZNC - 1.6.0 - http://znc.in]
nitdega has joined #openwrt-devel
silverwhitefish has quit [Quit: One for all, all for One (2 Corinthians 5)]
<guidosarducci>
For devs using/maintaining ppc, was a QEMU-based target ever looked into, similar to armvirt or malta? Any foreseeable problems? A virtual ppc target would be handy for coverage and testing.
eigma_ has joined #openwrt-devel
jas4711 has quit [Remote host closed the connection]
zjason has joined #openwrt-devel
<mangix>
guidosarducci: I don't think there are many PPC devices
<mangix>
There are some but the vast majority is MIPS and ARM
<guidosarducci>
mangix: I know that, but ppc has a history of causing.. err revealing other SW problems, hence useful for test/debug. While it *is* possible to simply build one's SW against ppc targets (and I do), being able to run it too is better.
<pkgadd>
big endian ppc as a whole is rather dead
black_ant has joined #openwrt-devel
black_ant has joined #openwrt-devel
black_ant has quit [Changing host]
valku has quit [Quit: valku]
slh64 has quit [Ping timeout: 260 seconds]
Acinonyx has quit [Ping timeout: 240 seconds]
Acinonyx has joined #openwrt-devel
skrzyp has quit [Ping timeout: 250 seconds]
<plntyk>
stintel, thank you !
poljar1 has joined #openwrt-devel
poljar has quit [Read error: Connection reset by peer]
sbrown_ has quit [Remote host closed the connection]
sbrown_ has joined #openwrt-devel
sbrown_ has quit [Remote host closed the connection]
sbrown_ has joined #openwrt-devel
eigma_ has quit [Quit: leaving]
rmilecki has joined #openwrt-devel
Tapper has joined #openwrt-devel
dedeckeh has joined #openwrt-devel
sbrown_ has quit [Remote host closed the connection]
sbrown_ has joined #openwrt-devel
slh64 has joined #openwrt-devel
goliath has joined #openwrt-devel
ivanich has joined #openwrt-devel
Tost has joined #openwrt-devel
<stintel>
plntyk: you're welcome!
xback has quit [Ping timeout: 240 seconds]
xback has joined #openwrt-devel
snh has quit [Read error: Connection reset by peer]
* rsalvaterra
looks at the interrupt distribution on his MT7621 device and wonders…
<rsalvaterra>
… has anyone around here tried irqbalance on MT7621?
<rsalvaterra>
The distribution I see doesn't look bad (Ethernet on one core, both Wi-Fi devices on the other core, one on each sibling), though…
rmilecki has quit [Read error: Connection reset by peer]
<stintel>
yay got my DACs
victhor has joined #openwrt-devel
rmilecki has joined #openwrt-devel
<rsalvaterra>
stintel: DACs? As in audio ones?
<stintel>
no, Direct Attached Copper
<stintel>
to link the CN6640-SNIC10E to my switch ;)
<stintel>
for a DAC ... I'm waiting for Khadas Tone Board 2 in board/kit to become available
<stintel>
I will then try adding it to my DIY UcD400 PA
nitroshift has joined #openwrt-devel
<rsalvaterra>
Overkill. Both of them. :P
Habbie has joined #openwrt-devel
<nitroshift>
rsalvaterra, o/
<rsalvaterra>
nitroshift: Hi, there!
<Habbie>
hello! if i suspect a packaging bug in some things in the packages tree, would i discuss that here or in #openwrt?
<rsalvaterra>
stintel: Actually… that UCD400 looks sweet. Single channel, class D…
<Habbie>
(of course i'm happy to file tickets or PRs but i first want to make sure i'm not missing things)
<stintel>
rsalvaterra: the kit was dual channel
<stintel>
rsalvaterra: wanted the Nc400 actually and got confused with the 400 # :P
<stintel>
rsalvaterra: but the Nc400 is only available in single channel kit
<stintel>
Habbie: if it's purely about packaging I'd say here is better - do mind that not all people who have access to the packages feed are on IRC
<stintel>
is it about any of the PowerDNS daemons :)
<rsalvaterra>
stintel: What preamp are you using?
<stintel>
rsalvaterra: it's not really a pre, but I wanted to move my most expensive speakers away from the main amp to reduce the risk of clipping when I'm going nuts :P
<stintel>
NAD T778
<stintel>
and the DIY kit was also kind of an experiment
<stintel>
when I build my own place, I'll go nuts on object based surround with something like Anthem AVM 70 prepro, and each channel on some NcXXX monoblock
<stintel>
with the monoblocks as close to the speaker as possible and balanced xlr from the prepro to the monoblocks
<stintel>
or that's the idea that's currently in my head, at least :)
guidosarducci_ has joined #openwrt-devel
guidosarducci has quit [Ping timeout: 240 seconds]
guidosarducci_ is now known as guidosarducci
<rsalvaterra>
stintel: I'm happy with my cheap-as-chips TPA3116D2, for the time being. XD
<stintel>
that's all that matters!
<Habbie>
stintel, thanks! and yes, i'm currently looking at 'opkg install dnsdist' which needs 19.9MB and i suspect it could be smaller
<Habbie>
for example
<rsalvaterra>
Besides, getting the lady to approve all the cabling… yeah, wound't be a trivial task.
<rsalvaterra>
*wouldn't
<stintel>
Habbie: ahh that's pretty awesome! smaller sounds good
<Habbie>
libh2o-evloop appears to contain 3 identical copies of a .so
<Habbie>
not symlinked, not hardlinked
<stintel>
rsalvaterra: I'd probably hide the xlr in the walls and ceiling
<Habbie>
and ruby is pulled in for no reason that i can find
<Habbie>
(also boost but that's an empty shell)
<stintel>
I'm actually running pdns-recursor on OpenWrt and I'm asking myself questions about the memory usage when loading large blocklists and using multiple threads
<Habbie>
i can probably answer those - might make more sense in OFTC #powerdns but i'm not picky
<stintel>
alright, good to know (haven't paid much attention to it yet as it's some kind of side project)
<stintel>
I have to run now, meeting
<stintel>
actually I have both dnsdist and pdns-recursor on that device
<stintel>
-rw-r--r-- 1 stijn users 1,3M dec 12 07:46 bin/packages/aarch64_cortex-a53/packages/dnsdist_1.5.1-1_aarch64_cortex-a53.ipk
<stintel>
I guess you're talking about dnsdist + deps
<Habbie>
yep
<Habbie>
the dnsdist ipk is around 1,3-1,5M yes
<Habbie>
but with all deps it adds up to 19,9M installed
<stintel>
alright, it's hard for me to check that as I'm building custom images
<Habbie>
ah
<Habbie>
i'm just toying with the rootfs image from the docker hub right now, and installing via opkg
<stintel>
so opkg install dnsdist pulls in ruby?
<Habbie>
yes, because libh2o-evloop depends on it
<Habbie>
i think it is a build dep for it
<Habbie>
but not a runtime dep
<Habbie>
so that might be as simple as removing one word from libs/h2o/Makefile
<stintel>
the package defines it as a normal dependency, not a build dep
<Habbie>
PKG_BUILD_DEPENDS:=ruby/host libwslay
<Habbie>
i guess -this- line means it needs ruby on the machine that is running the compiler?
<stintel>
yeah, that's a host build
<Habbie>
and then later it indeed lists it as a normal dep, and i can't see a reason for that
<stintel>
so it needs ruby on the host to be able to build it
<stintel>
seems that dep is there since initial commit of h2o (c9fa74bf43cfa535d6220a9db8cf43e20c4f104c)
<stintel>
don't know if the maintainer is on IRC
<Habbie>
he's been on #powerdns on occasion
<Habbie>
but not recently
<stintel>
maybe drop him an email first to ask why that dep is there?
<Habbie>
yep, makes sense
<stintel>
maybe it's just a leftover before he figured out PKG_BUILD_DEPENDS ruby/host
<stintel>
from before*
<Habbie>
likely - the 3 copies of the .so also probably stem from inexperience (while he certainly has more than i do, at this point)
<Habbie>
i'll ping him while i get a build env set up
<Habbie>
thanks
<stintel>
I can actually try and remove that dep
<stintel>
I have a working build env
<Habbie>
'dan graag' :)
<stintel>
geef me ff ;)
Strykar has quit [Quit: /quit]
Strykar has joined #openwrt-devel
<stintel>
nice, tools/zstd doesn't build
<stintel>
always the same problem when you want to "quickly do X"
<Habbie>
hehe
<Habbie>
looks like zstd itself has not been touched on master for a while
<stintel>
maybe I need a make clean
<Habbie>
it looks like i am a bunch of makes away from being able to do anything, but that's to be expected as a new user i'd say :)
<Habbie>
it's building a lot of things my Debian already has ;)
<stintel>
yeah the problem is that the device that I'm running pdns-recursor/dnsdist on is not supported yet and my current work doesn't rebase cleanly on master
<Habbie>
ouch
<Habbie>
i'm keeping life simple on x86 for now
<Habbie>
what device is it?
<stintel>
I've got arm, arm64, mips, mips64, powerpc64, x86