I'm going to buy this router: https://www.alibaba.com/product-detail/product_1600644831261.html
I would like to build a firmware for it according to my needs.
Based on which firmware is it better to do this?
What exactly should I ask the manufacturer to be able to build the firmware?
build as in from source, or customize by adding you config and modules ?
firmware, or image ?
Tenbay - KuWfi T-MB5EU, if the ToH is correct.
depends, are you using "our" openwrt, or their old, molested, spin off ?
Build as in from source, by adding my config and modules
As this: https://github.com/VladimirKalachikhin/MT7620_openwrt_firmware
but for other device.
frollic
January 17, 2023, 11:36am
4
if you're using 19.07, you're on your own, it's EOL, and there's no AX support in proper openwrt 19.07.
frollic
January 17, 2023, 12:01pm
6
the wifi standard the product you linked to, is using.
No problem.
The 19.07 is the last which can be installed on my WE826 router. But we are now talking about a completely different device.
What target should I specify to build the last OpenWRT firmware for the specified in start topic device?
frollic
January 17, 2023, 12:13pm
8
it's not, it's the latest one provided by the vendor .
WE826 is supported here - https://openwrt.org/toh/zbtlink/we-826
the Alibaba device you liked to, isn't however the WE826.
which device are we talking about, specifically ?
you've already asked the question once before, and received a reply.
Adding a new device A good all-round advice would be to start by looking at recent commits about adding a new device, to see what files where changed and how. Many files try to be as self-explanatory as possible, most of the times just opening them...
frollic:
it's not,
It's yes, but that's not what we're discussing.
I'm sorry you couldn't help me. I'm sorry to have taken up your time.
frollic
January 17, 2023, 12:25pm
10
How would I/we know?
Why bring it up in the 1st place ?
I'm sorry you're unclear, mixing two different devices ...
Should we start talking space travel too ? it's equally (ir)relevant.
See response from a developer:
What does OEM need to do if architecture/target doesn't exist
What to do if already exists
Why did the chip manufacturer give me this different SDK, how was it developed from OpenWrt, etc.
Supply patches to upstream Linux kernel to add hardware support. Once hardware is supported in Linux kernel, we can add (ie. backport) support to OpenWrt.
Then it's easy, all they have to do is submit board support code (ie. device tree and board-specific user-space scripts).
Chip designers supply downstream board manufacturers with a software development kit. Usually this contains a (terribly outdated) Linux kernel and a minimal Linux user-space distribution, often times based on OpenWrt. Usually this is developed behind closed doors by the chip designer and it wouldn't even make much sense for them to send any of it upstream at the point the chip designer is working on it , as the chip is not yet mass-produced and no devices for testing/validation are available in the market.