swex_ has quit [Read error: Connection reset by peer]
guerby has joined #openwrt-devel
swex has joined #openwrt-devel
biangbiangmian has joined #openwrt-devel
swalker has quit [Ping timeout: 260 seconds]
RoboMWM has quit [Read error: Connection reset by peer]
FirstTime_NoTime has joined #openwrt-devel
swalker has joined #openwrt-devel
biangbia_ has joined #openwrt-devel
biangbiangmian has quit [Ping timeout: 246 seconds]
RoboMWM has joined #openwrt-devel
biangbia_ has quit [Remote host closed the connection]
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
gch9812139697 has joined #openwrt-devel
gch981213969 has quit [Ping timeout: 260 seconds]
gch9812139697 is now known as gch981213969
biangbiangmian has joined #openwrt-devel
black_ant has joined #openwrt-devel
black_ant has quit [Changing host]
black_ant has joined #openwrt-devel
hbug_ has joined #openwrt-devel
hbug has quit [Ping timeout: 240 seconds]
biangbia_ has joined #openwrt-devel
biangbiangmian has quit [Read error: Connection reset by peer]
philipp64 has joined #openwrt-devel
tobleminer-tSYS has quit [Quit: AS4242423214]
hbug_ has quit [Remote host closed the connection]
tobleminer-tSYS has joined #openwrt-devel
hbug_ has joined #openwrt-devel
philipp64 has quit [Read error: Connection reset by peer]
Pix has quit [Ping timeout: 258 seconds]
biangbia_ has quit []
Pix has joined #openwrt-devel
gch9812139695 has joined #openwrt-devel
gch981213969 has quit [Read error: Connection reset by peer]
gch9812139695 is now known as gch981213969
heffer has quit [Quit: heffer]
goliath has quit [Quit: SIGSEGV]
<FirstTime_NoTime>
I got feedback to use DT trigger instead of set_wifi_led "$boardname:white:wifi"
<FirstTime_NoTime>
What is that one referring to?
rsalvaterra1 has joined #openwrt-devel
rsalvaterra has quit [Ping timeout: 246 seconds]
Huntereb has joined #openwrt-devel
philipp64 has joined #openwrt-devel
gch981213969 has quit [Read error: Connection reset by peer]
gch981213969 has joined #openwrt-devel
<rr123>
checked out master this morning worked well, just did a git pull and on my tp-link c7 eth0.2 is gone
<FirstTime_NoTime>
@rr123: Looking at the log there doesn't seem to be anything that should have affected it, judging by the descriptions... could have been an effect of flashing the firmware a second time?
<rr123>
yes reflashed it, power cycle it, I could not do : ip link set eth0.2 up, also, dmesg|grep eth0 only showed eth0.1
<rr123>
i normally do two builds of master, one in the morning one at night, this is the first non-working build I had for weeks
<rr123>
i'm 'make distclean' and rebuild the whole thing now
<rr123>
Cannot find device "eth0.2"
<FirstTime_NoTime>
"generic: platform/mikrotik: implement multi caldata" <- that should not have any impact on eth0.2
<FirstTime_NoTime>
But looking at the datasheet, that should all be the same driver
<FirstTime_NoTime>
(*module)
<PaulFertser>
FirstTime_NoTime: DT trigger means that you can configure wifi led in the DTS of the board
<PaulFertser>
rr123: check your switch config, eth0.2 would be vlan2 on eth0.
<rr123>
PaulFertser: don't understand, how to check switch-config
<FirstTime_NoTime>
PaulFertser: Would you know if I can drop aliases
<FirstTime_NoTime>
I can see that other DTS files still have that section for the LEDs. I will keep it for now
black_ant has quit [Ping timeout: 260 seconds]
<FirstTime_NoTime>
@rr123: You should be able to check it in LUCI (web interface)
<FirstTime_NoTime>
rr123: Should be system -> switch and should give you a drop down menu
<FirstTime_NoTime>
Oh, I have another (stupid) question.. if my device has 2 separate Ethernet chips (same model though). Should they come up as eth0 and eth1 or eth0.1 and eth0.2?
FirstTime_NoTime has quit [Remote host closed the connection]
<olmari>
Usually eth0 and eth1
<olmari>
"major" number points to actual device, be it yot
FirstTime_NoTime has joined #openwrt-devel
<FirstTime_NoTime>
Got disconnected
<olmari>
"major" number points to actual device, be it your traditional NIC or "switch device" like oftentimes in OpenWrt scope
<olmari>
So eth0 and eth1
<FirstTime_NoTime>
That's what I expected.. the stock FW uses eth0.1 and eth0.2
<olmari>
Obviously at driver level there could be any form of "mapping" anyhow
<FirstTime_NoTime>
I thought it was an openWRT convention
<olmari>
well I don't know how would one then use any VLANs with that, so sounds weird
<FirstTime_NoTime>
It did confuse me
<FirstTime_NoTime>
ralink_soc_eth 10100000.ethernet: connected port 4 to PHY at mdio-bus:04
<FirstTime_NoTime>
ralink_soc_eth 10100000.ethernet: connected port 5 to PHY at mdio-bus:05
<FirstTime_NoTime>
Maybe I don't understand the way the whole thing is wired up internally
<olmari>
I also know some of switch devices has 2 "cpu ports", having the opposite possible and single device being capable offering eth0 and eth1 (and VLANS to them)
<FirstTime_NoTime>
It definitely has two RTL8211F (from memory) chips on it.
<FirstTime_NoTime>
One at the back offering PoE and one at the front
<olmari>
you sure there are 2 actual NICs or "just" physical tranceivers etc?
<FirstTime_NoTime>
Probably the later
<FirstTime_NoTime>
So the distinction escapes me
<FirstTime_NoTime>
ralink_soc_eth 10100000.ethernet: connected port 4 to PHY at mdio-bus:04 [uid=001cc916, driver=Generic PHY]
<FirstTime_NoTime>
ralink_soc_eth 10100000.ethernet: connected port 5 to PHY at mdio-bus:05 [uid=001cc916, driver=Generic PHY]
<FirstTime_NoTime>
They share the same uid
<FirstTime_NoTime>
I have got to go... seems like I will have to look into this some more
<FirstTime_NoTime>
thank you
FirstTime_NoTime has quit [Remote host closed the connection]
nitroshift has joined #openwrt-devel
<aparcar[m]>
rsalvaterra1: yea we'd need the -z I guess
<PaulFertser>
rr123: switch config is in /etc/config/network , as usual. Board description file is /etc/board.json.
<ynezz>
and I plan to push it once we branch 21.yy
<mangix>
people still build on CentOS 7
<aparcar[m]>
ynezz: I'd be fine with a hourly scheduled CI job. that seems secure enough
<ynezz>
mangix: yeah, they can update gcc
<mangix>
Hmm?
<mangix>
CentOS 7 uses GCC 4.8.2
<aparcar[m]>
how will people with this new apple m1 chip compile openwrt...
<mangix>
aparcar[m]: oh compiling on an ARM host actually works
<ynezz>
mangix: that is default, it has package manager, you can update to something newer
<aparcar[m]>
ynezz: can you please remove the collect.py script corn job and I build a hourly CI?
<mangix>
weird. last i looked there was no newer GCC available
<mangix>
maybe needs some 3rd party repo
<mangix>
mostly my question is what does killing support for GCC 4 and 5 bring?
<ynezz>
mangix: less issues
<ynezz>
there was a thread about it in v1
valku1 has quit [Quit: valku1]
<mangix>
Besides some host packages that need C++-14, CentOS 7 can build all packages with GCC 4.8.2
<mangix>
sorry, C++17
<mangix>
although that's also a problem with GCC 6...
Borromini has joined #openwrt-devel
<ynezz>
the main issue is CI/QA, if you want to support such older compilers, you need to test the changes on those compilers as well
<ynezz>
otherwise you risk bug reports from people using such old compilers
<ynezz>
buildbots wont catch those either
<mangix>
The host GCC is only used to compile the toolchain and host packages. Why would the host GCC be relevant when a newer toolchain GCC is used?
<ynezz>
it's still quite big set of packages
<ynezz>
if we don't test against such old compiler, why to support it officially?
<ynezz>
if you're going to triage that bug/patch/PR, you're likely going to spin up that affected distro in Docker and verify it
<mangix>
I'm asking as I compile all packages in my CentOS 7 VM to see if anything broke. Everything that breaks specifically with CentOS 7 is a host package failure
<mangix>
any other failure breaks everywhere else
<aparcar[m]>
ynezz: firmware selector does seem to work now, did you do anything?
<ynezz>
aparcar[m]: I've deployed the new collect.py and changed the commandline in the cron job
<mangix>
Although the former is a GCC extension and not standard C.
decke has joined #openwrt-devel
muhaha has joined #openwrt-devel
dedeckeh has joined #openwrt-devel
rsalvaterra1 has quit [Quit: Leaving.]
rsalvaterra has joined #openwrt-devel
<rsalvaterra>
'morning!
<rsalvaterra>
aparcar[m]: Alright, I'll send it as a follow-up, or include it in a v2 if changes are needed.
<Grommish>
Morning rsalvaterra
<rsalvaterra>
(I swear, my ISP gateway must be running a cron job to reboot it every day at 4:30 in the morning.)
<aparcar[m]>
rsalvaterra: they do have that kind of cronjob usually
<SwedeMike>
I know ISPs who bounce the PPPoE session at the same time every day
<SwedeMike>
... and thus forcing IP address change
<rsalvaterra>
SwedeMike: Yeah, but I have a (Euro)DOCSIS connection, so it's bridged.
Net147 has quit [Quit: Quit]
Net147 has joined #openwrt-devel
dopje has quit [Quit: Checking other places]
gch981213969 has quit [Read error: Connection reset by peer]
gch981213969 has joined #openwrt-devel
jg_ has quit [Ping timeout: 264 seconds]
dopje has joined #openwrt-devel
<rsalvaterra>
rr123: Master is broken. The netifd changes need to be reverted.
<rsalvaterra>
I already wrote this yesterday…
<rsalvaterra>
Either reverted or fixed. But I'm sure they weren't thoroughly tested, at least on switchdev and/or one-armed routers.
<Grommish>
How do I call defined functions to build? I've got a define Host/InstallBinaries but if I do make -j1 V=sc package/feeds/packages/rust/host/installbinaries it tells me it valid
<Grommish>
err tells me its not valid
Borromini has quit [Quit: Lost terminal]
<rsalvaterra>
So, would someone with commit access please revert a0be58576cfc25f93f10aabf45908f6056d9f848 for the time being…?
dedeckeh has quit [Remote host closed the connection]
Grommish has quit [Ping timeout: 256 seconds]
Grommish has joined #openwrt-devel
Ycarus has joined #openwrt-devel
Olipro has quit [Ping timeout: 272 seconds]
Openwrt11111 has joined #openwrt-devel
Openwrt11111 has left #openwrt-devel [#openwrt-devel]
<nbd>
pushed a fix to netifd.git, will update netifd in openwrt next
<nbd>
rsalvaterra: done. should work now
<rsalvaterra>
f00b4r0: I don't think so, because VLAN 1 came up, just not VLAN 2. It was weird, indeed.
<nbd>
the problem was this:
<nbd>
one of my commits moved some checks to a later point in time for vlan devices by setting dev->config_pending = true
<nbd>
when dev->config_pending is set, the core calls device_check_state later
<rsalvaterra>
nbd: Let me guess: commit 3a2b21001c3c93dbe8502a8df465e415f18a84b1?
<nbd>
no, that's just dummy code
<rsalvaterra>
Ah, well.
<nbd>
the commit that triggered the bug was a3016c4512487a9673d13a4b09ba05e774df1e73
<nbd>
the real bug was the fact that system_if_check checks device present state for all device types
<rsalvaterra>
I see now.
<nbd>
so the vlan code would set present=true, but before it would be brought up, system_if_check would set it to false again because it couldn't find the linux netdevice with that name
<nbd>
before the vlan commit, the order was the other way around
<nbd>
that's why it worked before
<rsalvaterra>
Alright, I'm going to take it for a spin here, thanks a lot for the quick turnaround, nbd!
aszeszo has quit [Read error: Connection reset by peer]
aszeszo has joined #openwrt-devel
noltari has quit [Quit: Bye ~ Happy hacking!]
<rsalvaterra>
nbd: Lunch time here, just tested a new build and it's perfect.
<nbd>
great
<jow>
nbd: is that fix applying to macvlan devices as well?
<jow>
didn't have time to look into your fix yet but seen a macvlan regression report today related to the netifd bump
mrkiko has joined #openwrt-devel
<mrkiko>
Hello all!!
<nbd>
jow: no idea how my changes would have broken macvlan (based on a quick look, i'd expect it to have been broken before as well)
<nbd>
jow: but my change might fix it as well
<mrkiko>
gch981213969: hello! I am trying to figure out the mips boot process, for curiosity and maybe do some writings, who knows. I was using R6220 as reference. Of course I am faced with the MT7621 stage1 code, which seems closed and proprietary. Why do some devices use it and some not? And - I replaced the bootloader with breed on some of my r6220s, so probably my CPU isn't executing this code anymore.
<mrkiko>
why does all work well ?
<mrkiko>
gch981213969: i.e.: I guess my GnuBee PC1 doesn't use that code?
<mrkiko>
gch981213969: then, I am faced with mt7621_stage_L2.bin as well :)
<mrkiko>
gch981213969: or, better - as I understand it, calibration code is still present in the U-boot git repo, but can't determine for sure if it's used or not
valku has joined #openwrt-devel
owrt-snap-builds has quit [Quit: buildmaster reconfigured: bot disconnecting]
owrt-snap-builds has joined #openwrt-devel
feriman has quit [Ping timeout: 264 seconds]
owrt-1806-builds has quit [Quit: buildmaster reconfigured: bot disconnecting]
owrt-1806-builds has joined #openwrt-devel
owrt-1907-builds has quit [Quit: buildmaster reconfigured: bot disconnecting]
owrt-1907-builds has joined #openwrt-devel
owrt-1806-builds has quit [Remote host closed the connection]
owrt-1907-builds has quit [Remote host closed the connection]
owrt-snap-builds has quit [Remote host closed the connection]
owrt-1907-builds has joined #openwrt-devel
owrt-snap-builds has joined #openwrt-devel
owrt-1806-builds has joined #openwrt-devel
decke has quit [Quit: Leaving.]
MichaelOF has joined #openwrt-devel
<rr123>
the netifd fix brought eth0.2 back, cool.
noltari has joined #openwrt-devel
noltari has quit [Client Quit]
noltari has joined #openwrt-devel
<mrkiko>
gch981213969: ok, sorry, even GB-PC1 uses it. For breed, don't know - the binary appears somewhat compressed
Darkmatter66 has joined #openwrt-devel
Darkmatter66 has quit [Ping timeout: 265 seconds]
Darkmatter66 has joined #openwrt-devel
muhaha has quit [Quit: Connection closed]
MichaelOF has quit [Quit: Konversation terminated!]
awgh_ has quit [Ping timeout: 264 seconds]
heffer has joined #openwrt-devel
m4t has quit [Quit: m4t]
adrianschmutzler has joined #openwrt-devel
<adrianschmutzler>
hi, is there a policy where to put a backported kernel patch on DTS files that touches more than one target?