<soxrok2212>
n00b question: xiaomi devices store MAC address for eth0/1 and wlan0/1 in Bdata/factory partition. booting from initramfs tftpboot wouldn't grab those MACs correctly, right? cause they're wrong every time
dangole has quit [Remote host closed the connection]
dangole has joined #openwrt-devel
goliath has quit [Quit: SIGSEGV]
Ansuel has joined #openwrt-devel
hanetzer has quit []
rua has quit [Quit: Leaving.]
Ansuel has quit [Ping timeout: 480 seconds]
<dwfreed>
soxrok2212: the device tree has fields to tell the driver where to pull the MACs from
<soxrok2212>
hm okay then its probably an issue with my device tree not having partitions correct
Ansuel has joined #openwrt-devel
hanetzer has joined #openwrt-devel
<soxrok2212>
dwfreed: i think its because my nand device isn't recognized. i don't see it in the boot log
<dwfreed>
there's no "recognizing" with embedded; it's all device tree
dangole has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
Ansuel has quit [Ping timeout: 480 seconds]
<soxrok2212>
care to have a look?
<dwfreed>
I'm not familiar with the device, so I wouldn't be able to tell
<soxrok2212>
hrmmm
<hanetzer>
dwfreed: well, that's not quite right per se. it could be his kernel or u-boot doesn't have the right nand id programmed in.
<soxrok2212>
kernel should have support for it
lynxis has quit [Remote host closed the connection]
Tapper has quit [Read error: Connection reset by peer]
goliath has joined #openwrt-devel
MaxSoniX has joined #openwrt-devel
borek has joined #openwrt-devel
danitool has joined #openwrt-devel
noltari_ has joined #openwrt-devel
noltari has quit [Ping timeout: 480 seconds]
<T-Bone>
does fw3 send a ubus signal when the firewall is fully configured? There appears to be a random issue with chilli where chilli starts after wan is up but while firewall is configuring and this clobbers the chilli firewall rules
T-Bone is now known as f00b4r0
<dwfreed>
I mean, you could ubus monitor and find out :)
<jow>
Ansuel: yeah I figured. Still what are we using distutils for in the first place?
<jow>
especially as host toolk
<jow>
are we fetching python modules?
<jow>
isn't that a bad idea? long term availability, pinned versions etc.
<Ansuel>
quoting "<sure. but meson will fail to compile several packages when distutils is missing for IIRC python < 3.10
<jow>
that is disturbing
<robimarko>
distutils are deprecated, and will be gone with Python 3.12
indy has quit [Ping timeout: 480 seconds]
<f00b4r0>
ever so reliable python ;P
<Ansuel>
python = anarchy
f00b4r0 has quit [Ping timeout: 480 seconds]
f00b4r0 has joined #openwrt-devel
<f00b4r0>
well that's a first. It would seem my openwrt router crashed
borek has joined #openwrt-devel
srslypascal has quit [Quit: Leaving]
borek has quit [Remote host closed the connection]
<Ansuel>
pstore?
srslypascal has joined #openwrt-devel
indy has joined #openwrt-devel
<Ansuel>
digitalcircuit ping?
soxrok2212 has quit [Read error: Connection reset by peer]
soxrok2212 has joined #openwrt-devel
dangole has joined #openwrt-devel
guidosarducci_ has joined #openwrt-devel
guidosarducci has quit [Ping timeout: 480 seconds]
minimal has joined #openwrt-devel
valku has joined #openwrt-devel
Misanthropos has quit [Ping timeout: 480 seconds]
soxrok2212 has quit [Ping timeout: 480 seconds]
srslypascal is now known as Guest112
srslypascal has joined #openwrt-devel
Guest112 has quit [Ping timeout: 480 seconds]
goliath has quit [Quit: SIGSEGV]
borek has joined #openwrt-devel
soxrok2212 has joined #openwrt-devel
<aparcar[m]>
jow: did you decide on a yaml lib for ucode?
soxrok2212_ has joined #openwrt-devel
soxrok2212 has quit [Ping timeout: 480 seconds]
Misanthropos has joined #openwrt-devel
<jow>
aparcar[m]: well it's probably going to be libyaml, but I didn't really spent time on it yet
goliath has joined #openwrt-devel
cbeznea has quit [Quit: Leaving.]
<aparcar[m]>
jow: ack
<aparcar[m]>
Ansuel: what is the current status of the CI PRs? I'd like to get things to move forward
Misanthropos has quit [Ping timeout: 480 seconds]
<Ansuel>
aparcar if the workaround is acceptable we should just take the decision on what the user said about limiting it to openwrt repository_owner and it's ready
<Ansuel>
as you can see i tested it on a testing organization and the container is correctly pushed
<aparcar[m]>
I'll have a look
<Slimey>
these waps take forever to boot
<robimarko>
Ansuel: You backported all of the qca8k changes up to the code split?
<Ansuel>
robimarko yes but still not pushed
<Ansuel>
but i have them ready
<robimarko>
Ansuel: Ok, I am now working on adding IPQ4019 support to the split driver along with the v4 of IPQESS
<robimarko>
So, I want to backport that to 5.15 for OpenWrt to replace the not so pretty IPQESS and qca8k fork in IPQ40xx DSA PR
<Ansuel>
oh ok i will push the missing patch then
<Ansuel>
they are almost on par with linux-next aside from some changes to the bridge and lag function
<Ansuel>
guess bootlin finally pished v4 ess if you are working on an upstream ready version
<Ansuel>
aparcar added some comments if you missed them
<robimarko>
Yeah, they pushed v4 last week
<robimarko>
It still has some comments, but even so its way better than the pre-cleanup driver
<robimarko>
Ansuel: He added them to the PR or?
<Ansuel>
took them a lot did they reimplement everything o.o
<robimarko>
Not really, as far as I can tell they cleaned it up
<robimarko>
Reimplemented the tagger as a kind of universal out of band one
<robimarko>
And added the Phylink ops that were missing
<robimarko>
Ansuel: Thanks, I was hoping to get it already done
<robimarko>
But I am going to Dublin for ELCE tommorow so its not gonna be done this week
<Ansuel>
robimarko i think we will have to put extra work on it as Vladimir asked some abstraction of the probe and setup while proposing the code split so we will have to have EXTRA FUN with that
<robimarko>
Ansuel, I dont see what can be abstracted
<robimarko>
The thing I have no idea how to properly do is the damn PSGMII calibration
<robimarko>
Cause, we have to mess with the PHY directly
<Ansuel>
about that we will for sure ask some feedback from net reviwers cause for real it's a difficult thing to solve...
russell-- has quit [Ping timeout: 480 seconds]
[florian1 is now known as [florian]
russell-- has joined #openwrt-devel
mrnuke has quit [Remote host closed the connection]
SlimeyX has joined #openwrt-devel
mrnuke has joined #openwrt-devel
borek has quit [Ping timeout: 480 seconds]
Borromini has joined #openwrt-devel
csrf has joined #openwrt-devel
<Ansuel>
mbd ping ?
<Ansuel>
nbd*
<Ansuel>
any reason why we never created a md5 based on the md5 of the files?
csrf has quit [Ping timeout: 480 seconds]
csrf has joined #openwrt-devel
<nbd>
Ansuel: you mean for the build stamp files?
<Ansuel>
i mean for the package files (makefile, patches...)
Misanthropos has joined #openwrt-devel
<Ansuel>
we currently create the hash based on the mtime but that gets set to whatever time is set when you git clone
<nbd>
could be some corner cases where it will be more expensive
<nbd>
maybe a hash of filename + timestamp would be enough?
<nbd>
so that it's not just based on the latest timestamp of all files
<Ansuel>
saddly mtime can't be used for hash generation as git clone doesn't set the original mtime
<nbd>
it doesn't have to be the original mtime, as long as it changes somehow when switching to a different revision
<nbd>
or is your problem too many rebuilds?
<Ansuel>
problem is that .prepared file change across different buildroot and this makes impossible to recycle a tar with prebuilt tools
<nbd>
maybe it would be a good idea to hash the contents, but only when CONFIG_AUTOREMOVE is set
<nbd>
so that it only affects buildbot type workloads
<Ansuel>
MH
<Ansuel>
NICE IDEA!
<nbd>
without slowing down typical development
<Ansuel>
sorry caps
<Ansuel>
yeah my main concern was the slowdown of creating an hash of each file
<nbd>
we should definitely measure the difference
<nbd>
on a buildbot run a few seconds of extra cpu time probably won't matter much
<nbd>
but for normal development, i'm very sensitive about it
<Ansuel>
i will limit this to AUTOREMOVE so we can make progress on the CI and in the meantime we can check if this cause real slowdown
<Ansuel>
(the real slowdown should be only for kernel build since it needs to gen hash of each patch and files but i don't think it will be that relevant)
<Ansuel>
Mangix can you use this to generate fixes tag ? git --no-pager show -s --abbrev-commit --abbrev=12 --pretty=format:"%h (\"%s\")%n" THE_HASH
<Ansuel>
as it produce
<Ansuel>
26a6a6a60ba7 ("ramips: add support for Belkin RT1800")
tlj has joined #openwrt-devel
tlj has quit []
tlj has joined #openwrt-devel
<Mangix>
Ansuel: Done
tlj has quit [Remote host closed the connection]
<Ansuel>
Mangix thanks a lot i would merge it tomorrow as I would like if there is a chance to use a new way to flag it as merged in github
<Ansuel>
I wold like to check*
<Ansuel>
(god today i can't write correct english)
<Ansuel>
(aparcar don't know if you god my private email)
<Ansuel>
got* -.-'''
tlj has joined #openwrt-devel
<aparcar[m]>
Ansuel: I looked into it a while ago but it was somehow difficult to change. I can look into it again
<aparcar[m]>
technically you can just checkout the branch locally, rebase it, then merge it and push again. it should automatically close the PR. However that's some extra steps to take care of
<Ansuel>
oh wow really? tought it was just a simple change and access the github bot account to add an ssh key
<Ansuel>
aparcar problem is that jow- tag
<Ansuel>
or you were referring to some type of bidirectional stuff to permit the merge from github?
<hexa->
Question about bridge port forwarding on the edgerouter-x; we are running openwrt-22.03 and tried to enable bridge port forwarding for multiple DSA ports (eth{1,2,3,4}) in a single bridge, but the isolation simple does not happen
<hexa->
in fact we can see isolated show 1 on every brif in sysfs
<hexa->
the working theory that this is caused by hardware offloading of the bridge port forwarding
<hexa->
I wonder what offloading knob we should disable (via ethtool -K) to test this theory
<hexa->
the switch is MT7621AT
MaxSoniX has quit [Quit: Konversation terminated!]