<stintel>
does anyone remember things like this for AR8236 / mvebu and a possible solution?
<stintel>
9% is really unacceptable
<stintel>
even 1% is unacceptable
csrf has quit [Read error: Connection reset by peer]
csrf has joined #openwrt-devel
Nick_Lowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
am0rphis has quit [Remote host closed the connection]
Nick_Lowe has joined #openwrt-devel
am0rphis has joined #openwrt-devel
glyph has quit [Quit: End of line.]
glyph has joined #openwrt-devel
Nick_Lowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
hbug___ has joined #openwrt-devel
gch9812138 has joined #openwrt-devel
gch981213 has quit [Read error: Connection reset by peer]
gch9812138 is now known as gch981213
hbug__ has quit [Ping timeout: 240 seconds]
Nick_Lowe has joined #openwrt-devel
tobleminer-tSYS has quit [Quit: AS4242423214]
tobleminer-tSYS has joined #openwrt-devel
Grommish_ has joined #openwrt-devel
Grommish has quit [Ping timeout: 256 seconds]
Grommish_ is now known as Grommish
mbm is now known as [mbm]
goliath has quit [Quit: SIGSEGV]
mwarning has joined #openwrt-devel
Nick_Lowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
gch981213 has quit [Read error: Connection reset by peer]
gch981213 has joined #openwrt-devel
heffer_ has joined #openwrt-devel
heffer__ has joined #openwrt-devel
heffer has quit [Ping timeout: 240 seconds]
heffer_ has quit [Ping timeout: 258 seconds]
mwarning has quit [Ping timeout: 244 seconds]
gch981213 has quit [Read error: Connection reset by peer]
gch981213 has joined #openwrt-devel
danitool has quit [Ping timeout: 240 seconds]
valku has quit [Quit: valku]
mwarning has joined #openwrt-devel
Grommish[M] has quit [Ping timeout: 260 seconds]
Grommish[M] has joined #openwrt-devel
gch981213 has quit [Read error: Connection reset by peer]
gch9812134 has joined #openwrt-devel
phormulate has joined #openwrt-devel
gch981213 has joined #openwrt-devel
gch9812134 has quit [Read error: Connection reset by peer]
mwarning has quit [Ping timeout: 260 seconds]
Borromini has joined #openwrt-devel
dedeckeh has joined #openwrt-devel
<damex>
stintel: is it even a supported target?
phormulate has quit [Ping timeout: 240 seconds]
ivanich has joined #openwrt-devel
feriman has joined #openwrt-devel
Night-Shade has quit [Ping timeout: 265 seconds]
ivanich has quit [Quit: Konversation terminated!]
ivanich_ has joined #openwrt-devel
lynxis has quit [Remote host closed the connection]
zaolin has quit [Remote host closed the connection]
zaolin has joined #openwrt-devel
goliath has joined #openwrt-devel
lynxis has joined #openwrt-devel
danitool has joined #openwrt-devel
danitool has quit [Client Quit]
eduardas has joined #openwrt-devel
Ycarus has joined #openwrt-devel
lep-delete is now known as Guest88073
black_ant has joined #openwrt-devel
black_ant has quit [Changing host]
black_ant has joined #openwrt-devel
gch9812139 has joined #openwrt-devel
gch981213 has quit [Read error: Connection reset by peer]
gch9812139 is now known as gch981213
Guest88073 is now known as lep-delete
feriman has quit [Quit: WeeChat 2.9]
rsalvaterra has joined #openwrt-devel
feriman has joined #openwrt-devel
<stintel>
damex: mvebu ...
<damex>
stintel: well, how about board?
<stintel>
no, I'm working on it
<stintel>
that's why I'm asking if there were any similar cases
<stintel>
to check how it was solved there
<russell-->
at some point, i stumbled across a description of the mediatek (e.g. mt7628an) factory partition format ... can't find it now
feriman has quit [Quit: WeeChat 2.9]
SpaceRat has quit [Quit: Domino .gx.]
Namidairo has quit [Read error: Connection reset by peer]
Namidairo has joined #openwrt-devel
aszeszo has joined #openwrt-devel
aszeszo has quit [Client Quit]
aszeszo has joined #openwrt-devel
Borromini has quit [Quit: Lost terminal]
fredrikhl has joined #openwrt-devel
rsalvaterra1 has joined #openwrt-devel
rsalvaterra1 has quit [Client Quit]
rsalvaterra1 has joined #openwrt-devel
rsalvaterra has quit [Ping timeout: 260 seconds]
rsalvaterra1 has quit [Read error: Connection reset by peer]
rsalvaterra has joined #openwrt-devel
nitroshift has joined #openwrt-devel
nslu2-log_ has joined #openwrt-devel
nslu2-log_ has quit [Remote host closed the connection]
feriman has joined #openwrt-devel
nslu2-log_ has joined #openwrt-devel
nslu2-log_ has quit [Remote host closed the connection]
nslu2-log_ has joined #openwrt-devel
SpaceRat has joined #openwrt-devel
<eduardas>
hello, does anyone know if any work is being done on the IPQ6000/IPQ6010 SoC from Qualcomm?
<eduardas>
or any other Wi-fi 6 capable SoC?
<blogic>
eduardas: the QCA stuff wont be in owrt in a usable manner for a year or two
<blogic>
eduardas: the mediatek stuff is nice and upstream but still pending mass market HW
Acinonyx_ has joined #openwrt-devel
Nick_Lowe has joined #openwrt-devel
<eduardas>
blogic: good to know, thank you
<blogic>
eduardas: so basically 3-6 monhs from now people will be using mt7622/mt7915
Acinonyx has quit [Ping timeout: 256 seconds]
dangole has joined #openwrt-devel
<rsalvaterra>
blogic: I'd be happy with just the mini-PCIe MT7915 cards. Hopefully the Omnia still has enough oomph to drive them… :)
<eduardas>
blogic: is there a difference in level of mainline Linux support for Qualcomm or Mediatek stuff (in general)? Is one vendor better than the other when it comes to interfacing with FOSS community projects?
<blogic>
eduardas: yes
<blogic>
MTK has upstream support
<blogic>
QCA does not
<eduardas>
blogic: Mediatek contribute mainline support themselves or is it 3rd party?
<blogic>
they actively interact witht he upstream community
<eduardas>
blogic: I expect that the SoC docs are still under NDA?
<blogic>
eduardas: some are actually opened up
<eduardas>
blogic: really? did not expect that? you don't happen to know which ones specifically?
Darkmatter66 has quit [Quit: ZNC 1.7.5 - https://znc.in]
Darkmatter66 has joined #openwrt-devel
rsalvaterra1 has joined #openwrt-devel
rsalvaterra1 has quit [Client Quit]
Borromini has joined #openwrt-devel
rsalvaterra has quit [Ping timeout: 258 seconds]
Redfoxmoon has quit [Read error: Connection reset by peer]
Redfoxmoon has joined #openwrt-devel
Redfoxmoon has quit [Changing host]
Redfoxmoon has joined #openwrt-devel
rsalvaterra has joined #openwrt-devel
SpaceRat has quit [Quit: PG = Boy gets girl, R = Villain gets girl, X = Everybody gets girl .gx.]
gch981213 has quit [Read error: Connection reset by peer]
gch9812133 has joined #openwrt-devel
ivanich_ has quit [Quit: Konversation terminated!]
<blogic>
that is the full 2000 page programming guide with almost all registers listed for their latest and greatest arm64 SoC
<blogic>
they even put dxf files and schematics online
dedeckeh has quit [Remote host closed the connection]
DonkeyHotei has quit [Ping timeout: 260 seconds]
<eduardas>
blogic: really cool, thank you
<eduardas>
blogic: what about broadcom? are they trying to mainline their Wireless router stuff at least to some extent?
Ivan_83 has quit [Quit: Miranda NG]
Ivan_83 has joined #openwrt-devel
<Borromini>
eduardas: broadcom doesn't really care about FOSS
dangole has quit [Remote host closed the connection]
dangole has joined #openwrt-devel
valku has joined #openwrt-devel
am0rphis has quit [Remote host closed the connection]
am0rphis has joined #openwrt-devel
<blogic>
eduardas: brokencom has sold its wifi business to microchip
<blogic>
what we will see towards end of 2021 is NXP wifi
<blogic>
NXP bought the mrvell wifi business and are working on fos mac80211 drivers
<eduardas>
blogic: really? when did that take place? news to me
<blogic>
the NXP layerscape SoC are already upstream
<blogic>
but those are big high performance arm SoC
<rsalvaterra>
No love for mwlwifi, still…
<eduardas>
blogic: so the only options of this planet to implement router is to either use Qualcomm, Mediatek, Marvell or Broadcom SoCs?
<eduardas>
blogic: or am I missing some obscure company?
<blogic>
Mediatek or qca
<blogic>
brcm is a no-go option
<blogic>
and nxp/marvl is 12 months down the road
<blogic>
using qca means using a heavily patched v4.4 kernel
<blogic>
basically the AX situation is even worse than the AC one
<eduardas>
blogic: can not find info on broadcom selling wifi business to microchip
<nitroshift>
blogic, if only they'd release the mwlwifi code....
<Borromini>
nitroshift: that's probably an IP can of worms, all that closed firmware
<nitroshift>
Borromini, tell me about that.... :|
<nitroshift>
Borromini, funny enough, running binwalk against that blob says "Copyright string: "Copyright (c) 2007, 2009-2015 by Cisco Systems, Inc. "
<nitroshift>
rofl
<eduardas>
nitroshift: :D
<Borromini>
:P
<Borromini>
i'm finding broadcom put up their wifi business for sale, but nothing about the buyer.
<Borromini>
wouldn't surprise me if blogic knows more than the general public of course :)
<karlp>
broadcom's wifi went to cypress who wold it to infineon...
danitool has joined #openwrt-devel
linzst has joined #openwrt-devel
<damex>
https://github.com/openwrt/openwrt/pull/3519 could someone comment about naming ? it is kinda bother me. i am currently bringing up other 'Libre Computer' boards so need to know how to name them. @adschm seen the post but didn't post any comment
<damex>
<now go generate some platform data from device tree and manually append here>
<karlp>
Borromini: *shrugs* just seems to be what happened?
<damex>
002-spl-remove-dtoc-of-pdata-generation.patch seems like it didn't go through any review?
<damex>
blocktrron: ping ^
<blocktrron>
damex: ?
<damex>
blocktrron: why did you commit that? wouldn't it be better to provide proper dependency for the build process for tool to work?
<damex>
currently i am adding another board and it seems like platform data is different between uboot releases/different dtses. how are you supposed to update that?
<blocktrron>
it obviously needs to be updated per-board on bump for all rk3328
<blocktrron>
if you come up with the required dependencies, I'm grateful dropping this
<stintel>
damex: the problem is we don't have python in openwrt core and core packages are not allowed to depend on packets from the package feed
<stintel>
s/packets/packages/
<blocktrron>
The issue is in the end, that swig drags in around 8 python dependencies last time I've had a look at this
<damex>
is it even a problem for build host?
<blocktrron>
what stintel says
<blocktrron>
this way, swig and it's dependencies need to become host dependencies
<blocktrron>
if you intend on adding an rk3328 board: theres a rockchip uboot 2020.10 in my staging tree which you can build on
<Zero_Chaos>
karlp: apologies, I don't spend much computer time on the weekend lately. I have no idea where the extra macs are supposed to come from, I just know they typically shouldn't collide, and they do. In this case, it seems at least the wifi ones are generated by netifrcd
<Zero_Chaos>
PaulFertser: hola
<damex>
blocktrron: mine expected to work fine with current 2020.07
<damex>
blocktrron: is it a problem that they become a host dependencies?
<blocktrron>
especially with python stuff, this would mean a more narrow selections on which host systems you can use ootb. Especially with python, hosts might not sport the necessary python version required to build the dependency tree
<blocktrron>
i remember there was a similar discussion for the pylibfdt dependency on sunxi which ended in the similar patch
<blocktrron>
didn't follow that through though
<stintel>
we can move python to core
* stintel
hides
<Borromini>
:P
<Borromini>
and up the minimum to 128/64? :P
* blocktrron
follow stintel
<damex>
rockchip devices like that does not have problem with disk space or memory
<damex>
mine is just up to 128gb eMMC or 1T uSD
<damex>
and 4gb ram
<damex>
s/or/and/
<Borromini>
most routers are 8/64 or maybe double, but you'll be hard pressed to find cheap stuff with more headroom. And most people prefer to buy cheap stuff
<blocktrron>
damex: Borromini just brought up similar controversial topics, so this isn't an all to serious point
<Borromini>
blocktrron: would you seriously be considering it?
<Borromini>
if space is no issue i understand. I've seen older ARM devices choke though, as e.g. Salt clients (granted, not the smartest choice :P )
<stintel>
Borromini: this would be a host dep so device mem/storage is not relevant in this case
<Borromini>
stintel: oh. nevermind me.
<blocktrron>
well, python is a host-dependency so not related to the device per-se
Namidairo has quit [Ping timeout: 265 seconds]
Namidairo has joined #openwrt-devel
<damex>
blocktrron: so it should be fine then? just removed patches about removeing swig and dtoc and built it successfully on debian 10 (pretty old already), ubuntu 20.04 and centos 7 (oldest thing);p
<blocktrron>
Is this a fresh debian 10 installation?
<damex>
blocktrron: well, i have had tools installed previously to satisfly build tools but yeah ;p
<damex>
it will require python-dev as you said - i can try it again... i guess
<damex>
vagrant does not care how many times to repeat ;p
<blocktrron>
when I've commited this back in summer, this definitely didn't built on the buildbots nor on debian 10 with the documented minimum requirements
<damex>
blocktrron: i have python2 and python3 installed along with python*-dev
<damex>
blocktrron: so could we add dependencies to buildbot and just drop the patches?
<blocktrron>
damex: drop a mail to the list about your proposed change. i don't feel involved into the buildbots and the build system as a whole in order to make a decision here.
<blocktrron>
In the end, *if* this change is done, the binman hack for the other targets should / has to be also reworked
<damex>
blocktrron: could you first try if it produces a correct result for your board?
gch981213 has quit [Quit: Ping timeout (120 seconds)]
gch981213 has joined #openwrt-devel
AdamM43 has quit [Ping timeout: 245 seconds]
philipp64|work has joined #openwrt-devel
<rsalvaterra>
adrianschmutzler: ping
<adrianschmutzler>
rsalvaterra: pong, but not much time
philipp64|work has quit [Ping timeout: 246 seconds]
philipp64|work has joined #openwrt-devel
<rsalvaterra>
Sure, no problem. I just wanted to ask you if all targets are already at 5.4. From a cursory grep, it seems so.
<rsalvaterra>
Since we're dropping 4.19 support, that means I have to rebase a patch. :)
<adrianschmutzler>
Yes, everything is at 5.4, and that will also be next release kernel.
<rsalvaterra>
Great, thanks!
<adrianschmutzler>
I actually planned to remove 4.19 entirely, but when asking about it I was made aware of jffs2 errors in ath79
<adrianschmutzler>
Not having any target building on 4.19 by default is also an additional reason for removing it, as we have no "automatic" build test anymore ...
<dangole>
grift: aparcar and me were on making the selection of procd-selinux and busybox-selinux vs. procd and busybox a bit more automagic also in the ImageBuilder, so for that your documentation will need to be updated yet another time
<dangole>
grift: please also check my staging tree, I managed to get most services running as non-root, also ntpd now running as it's own user. maybe that makes it distinguishable for your policy as well?
goliath has joined #openwrt-devel
Night-Shade has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
philipp64|work_ has joined #openwrt-devel
philipp64|work has quit [Ping timeout: 256 seconds]
philipp64|work_ is now known as philipp64|work
Redfoxmoon has quit [Ping timeout: 246 seconds]
slh64 has quit [Ping timeout: 246 seconds]
slh64 has joined #openwrt-devel
Redfoxmoon has joined #openwrt-devel
<dangole>
grift: as a result, your policy would need to be updated for logd degrading itself: https://termbin.com/cxry
aszeszo has quit [Quit: aszeszo]
<stintel>
could we also please hide all selinux symbols behind one main selinux symbol? I am tired of saying no to a shitload of irrelevant selinux symbols
<stintel>
especially when the whole thing is experimental at best
dangole has quit [Remote host closed the connection]