<fpsusername[m]>
Zixel T-54 and Zixel FMG3005-R20A P2P
<Harm__>
fpsusername[m]: Nice
<Habbie>
oh neat
dangole has joined #openwrt-devel
<fpsusername[m]>
Good stuff?
<fpsusername[m]>
The modem has an SFP connector, like why
<fpsusername[m]>
As if any ordinary household uses thst
<fpsusername[m]>
I did have an sfp cable, 50cm. They're damn expensive. Nobody wanted to buy it so I threw it away (5+ years ago)
<Habbie>
gotta stick that FTTH somewhere
<fpsusername[m]>
Ftth?
<robimarko>
SFP is for FTTH
<Habbie>
fiber to the home
<fpsusername[m]>
But that's where the other box comes in place
<robimarko>
They will just provide a DT fiber/Zyxel PMG3000-D20B
<fpsusername[m]>
Fiber to wan
<fpsusername[m]>
So SFP isn't even used
<Habbie>
oh, right
<fpsusername[m]>
Maybe for other countries
<robimarko>
They are using it in Germany, Netherlands etc
<fpsusername[m]>
Is it a good modem? Like what chipset does it have? Broadcom, qualcomm, intel
<Habbie>
you tell us!
<Habbie>
(i have no idea)
<robimarko>
Well, if it has FCC ID just look it up
<fpsusername[m]>
Will see
<robimarko>
I have not seen any pictures
<robimarko>
BTW, Its Zyxel DX5401 with DT FW
<fpsusername[m]>
There's a serial number on the back, is that it or not?
<fpsusername[m]>
Yes a 5401
<fpsusername[m]>
DX5401-BO-NL02V1F
<robimarko>
Looks like a EU only model
<robimarko>
So, no FCC ID
<fpsusername[m]>
First hardware model, revision F
cbeznea has joined #openwrt-devel
srslypascal has quit [Ping timeout: 480 seconds]
<\x>
hows the outlook on ipq50xx robimarko, is the hardware worth the trouble?
<robimarko>
\x: Havent used it so far
<robimarko>
Only have one board, Motorola Q14
<robimarko>
However, it looks to be the as cheap as we can do it style SoC
<robimarko>
As its just dual core, has one radio built-in
<robimarko>
I even think there is a version with RAM built-in
<\x>
in theory for just pure networking itll be better than 806x just cpu wise
<\x>
or nahh
<robimarko>
I suspect they will be the same
<robimarko>
As this junker is just Dual core A53@1.0GHz
<robimarko>
Its gonna be popular for bottom tier designs
<robimarko>
As 2.4G AX 2x2@40MHz radio is fully built-in
<robimarko>
Even Bluetooth
<robimarko>
FFS its DDR3L only
<karlp>
is sdwalker here? who runs the uscan thing? I wanted to suggest that the emails include a link to the https://sdwalker.github.io/uscan/ page.
<\x>
if they spec it up good and it becomes usable it might replace the current scene where its all 7621
<\x>
at that point thats a real upgrade for those
<robimarko>
\x: I think they are aiming at exactly the ultra low cost MIPS designs
<robimarko>
Cause, its gonna wipe the floor with those
<\x>
yeah, its an upgrade hardware wise.
<\x>
software wise is the next question seeing how mature 7621a is and how much tweaking and mods has been done on it
<robimarko>
Well, that is why they made sure it has a NSS core again
<robimarko>
So its offloading everything
<robimarko>
They cut networking down though, there are 2 ports
<robimarko>
One 1G with built-in PHY
<robimarko>
And one SGMII+/SGMII SerDes so you can hook up a switch
<\x>
ehh thats good enough, many people here always think that 1G and such is low but look at what people are buying for openwrt
<robimarko>
So, basically number one focus was cost
<\x>
yup
<robimarko>
You can pretty much slap something together with few external components
<\x>
and two 1GHz A53 sounds enough to fully saturate those 1GbE
<robimarko>
Well, that depends on the driver
<robimarko>
But it looks like they used and off the shelf Synopsis stuff for ethernet
<robimarko>
Plus they are gonna offload everything in QSDK anyway
<stintel>
karlp: swalker
<stintel>
afaik
<\x>
im starting to sell my 7621a stuff. been with me since 2018
<\x>
twas a good run
<\x>
<robimarko> Well, that depends on the driver
<\x>
maybe time will come and someone pulls off another 4721
<oliv3r[m]>
I see some 'mac label' and man lan' references in ucidef functions. What is a 'mac label'? it's beeing loaded from uboots 'ethaddr' which is the 'management' ethernet device MAC address, e.g. a SoC's NIC.
<karlp>
it's how to get the mac address that's priunted on the label on the device itself, if it has one.
<karlp>
no matter what that mac migth actually be.
<oliv3r[m]>
ok, so it's the label on the box; got it. But what device should be associated with that MAC address? the managment NIC? the switch.0 bridge? the first LAN port?
* karlp
shrugs that's a different question altogether :)
<mrkiko>
what's the support status of the AX6000 ?
<robimarko>
Non existant
<mrkiko>
\x: ehehe, if FTC VDSL counts, I am one of them
<\x>
sucks aye?
<mrkiko>
robimarko: thanks
<\x>
i think dsl is still common on like Australia
<robimarko>
mrkiko: So far QCA hasnt even upstreamed their usuall base stuff
<robimarko>
Like pinctrl and GPIO
<jow>
nbd: so phy0-ap0, phy0-ap1, ... for now?
<jow>
lgtm
<mrkiko>
\x: well, in general no - 16.x megabytes/sec on peaks in download, don't exactly know how much upload but 2.x megabytes or something like that, peaks. The problem is performance isn't as constant as I would like, even tough lately it has been pretty constant to be honest. Waiting for FTTH... maybe, one day...
<nbd>
jow: yes
<mrkiko>
robimarko: thanks; I seen some things about the AX6000 but to be honest I was thining it was mtk based, not qca
<robimarko>
mrkiko: Redmi model is I think Filogic
<robimarko>
There is a PR for it
<mrkiko>
ok, so I was confused about model names.
<robimarko>
They messed up by having 2 AX6000 models
<robimarko>
Xiaomi one is IPQ5018 but Redmi is Filogic 7986
<\x>
redmi and xiaomi is different atleast here in asia people knows
gladiac has joined #openwrt-devel
<\x>
xiaomi is like "flagship" redmi is like "mid to lower"
<mrkiko>
and this makes a difference - because I know sometime xiaomi goes out of its way to stop you from using their hw with openwrt, maybe redmi doesn't? Don't know...
<nbd>
and afterwards i only need to add the board.json data + phy rename logic
<\x>
do they really?
<robimarko>
mrkiko: They are the same
<robimarko>
SW wise
<\x>
meanwhile they allow bootloader unlocking on their phones
<robimarko>
Locked up completely, so you have to find a Lua exploit to enable at least SSH and UART
<mrkiko>
btw, I know some routers are available only on aliexpress - still when I tried to use their mobile phone app, accessibility wasn't great. But maybe I am confusing it with alibaba or someting= :D
<karlp>
I'm getting "OF: Bad cell count for /ahb/spi@1f000000/flash@0/partitions" on boot, on 22.03, but I can't imagine what's wrong witht he partitions. https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=target/linux/ath79/dts/ar9331_etactica_eg200.dts;hb=HEAD#l89 ?
<karlp>
obviosuly, nothing bad actually happens, it all still works, but.. be nice to fix it?
<\x>
aliexpress is easy mrkiko. also tbh, the variability isnt there.
<\x>
taobao/xianyu is where its at
<mrkiko>
robimarko: but, ipq806x platform (e.g.: R7800) - was it a commercial success or not? To me it seems devices based on it are pretty rare, even tough in OpenWrt community the R7800 became pretty known
<karlp>
I get it four times, so presumably once for each partition.
<mrkiko>
\x: easy in what sense? I am talking about usability of the app with assistive technology like screen reader software
<\x>
its just like any chinese app, lots of ads lots of clickables, youll have to get used to it
<jow>
nbd: phy name as section name will likely break a lot of downstream use cases
<jow>
I bet the majority of downstream automations hardcodes radio0, radio1 instead of enumerating @wifi-device
<jow>
just a gut feeling though
<mrkiko>
\x: well, if they are labelled correctly and so the screen reader app recognized them, I am going to cope with it :D but otherwise... but I should try, maybe I am misremembering or talking about the wrong app
<nbd>
jow: so you prefer to leave it out for now?
<jow>
nbd: I am unsure. Maybe we should announce it on the devel list and facilitate feedback?
* mrkiko
remembers when he was trying to avoid hardcoding firewall zones...
<hurricos>
karlp: ditto
<hurricos>
... on ar7161-based board, had no idea what it was about
<hurricos>
once per partition
<hurricos>
Let me link the dts
valku has joined #openwrt-devel
<karlp>
I noticed it when I updated my tree from 21.02 to 22.03,
<robimarko>
mrkiko: It probably was for routing applications or high end routers at that time
Tapper has joined #openwrt-devel
Gaspare has joined #openwrt-devel
gladiac has quit [Quit: k thx bye]
Gaspare has quit [Quit: Gaspare]
Gaspare has joined #openwrt-devel
dangole has quit [Remote host closed the connection]
<hauke>
ldir: is there a problem with the iommu stuff?
<karlp>
hurricos: yeah, from a quick scan of the ath79 dts, I kinda expect ~most? of the ath79 devices are producing these warnings now?
<ldir>
hauke: it prompted me for at least 3 symbols - I decided I didn't want it at that point :-)
<hurricos>
probably!
<hurricos>
it's odd, there may be an upstream bug involved :^)
<hurricos>
I almost wish OpenWrt coudl afford to be *more* agressive about testing new kernels, we've seen a lot of bugs leak in through stable backports which are always a pita to resolve
<hurricos>
lol
<hurricos>
but someone has to do the work. I should get started on testing 5.15
<karlp>
careful, maybe the partitions warning will be upgraded to, "lol, don't recognise this poorly formatted partition, deprecated since 5.10...." ;)
<hurricos>
that's why I keep a drawer full of serial-connected test boards
<stintel>
ynezz: how is one supposed to install OpenWrt on olinuxino a64 if the emmc image tries to boot from emmc and the non-emmc image does not support the emmc?
<stintel>
the emmc is empty so the emmc image on sd hangs at boot, there is no prompt to abort boot, and the non-emmc image ... well you cannot access the emmc
isak has quit [Quit: leaving]
SlimeyX has quit [Ping timeout: 480 seconds]
SlimeyX_ is now known as SlimeyX
isak has joined #openwrt-devel
Borromini has quit [Read error: No route to host]
Tapper has quit [Ping timeout: 480 seconds]
danitool has joined #openwrt-devel
cmonroe_ has joined #openwrt-devel
Ansuel has quit [Quit: Probably my PC decided to sleep or I decided to sleep.]
SlimeyX has quit [Ping timeout: 480 seconds]
SlimeyX has joined #openwrt-devel
<tmn505>
stintel: use target/linux/tegra/image/generic-bootscript, replace zImage with uImage, ${soc}-${board}.dtb with dtb, bootz with booti, compile the script and put it boot partition. Should work (TM). Details: devtype and devnum will be set from where the first valid boot.scr will be found.
<stintel>
thanks, will try ... later, need to sleep, travelling tomorrow