Adding MT7628DAN SoC Board to OpenWrt Hardware Support List

Dear OpenWrt Community,

I am a user who has developed a board based on the MT7628DAN SoC. I am eager to contribute this hardware to the OpenWrt supported hardware list. However, I am unsure about the process to do so.

Could someone kindly guide me on how to add this hardware to the OpenWrt support list? Any assistance or pointers to relevant documentation would be greatly appreciated.

Thank you for your support and guidance.

Best regards,
Steven

https://openwrt.org/docs/guide-developer/adding_new_device
https://openwrt.org/docs/guide-developer/add.new.device

1 Like

Should I open a device support request here on the OpenWrt forums, or would reaching out via the mailing list be more appropriate? I want to ensure that I follow the correct procedure and engage with the community most effectively.

Any advice or recommendations on how to proceed would be greatly appreciated.

Thank you in advance for your assistance!

no one's is filling requests, unless you provide them with free hw samples.

you own the device, it's up to you to make support happen.

you can search for devices using the same SoC at https://openwrt.org/toh/views/toh_extended_all
then search for those devices in https://git.openwrt.org/?p=openwrt/openwrt.git;a=summary, to find
a git commit adding their support.

for instance https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=f204c812e996d51f36972d5f4414ada3d4588c93

1 Like

Regarding

no one's is filling requests, unless you provide them with free hw samples.

Do they have an address where I can provide them with the HW sample?

@frollic, the challenge we are facing is that we built our own board around the MT7628 SoC, which has a different .dts file from other hardware with the same MT7628 CPU. The compiled OpenWRT firmware could not work for other hardware even if it belongs to the same 76x8 subtarget.

So, I'd rather open a new entry to the OpenWRT Table of Hardware by sending them a sample of our device. The question is whether OpenWRT has a mailing address for me to send our hardware to them. Thanks.

Hi, @mango, how many pcs your hw boards on the market? If it less than 1000pcs, no need to add it to openwrt lists.

You could fork openwrt repo on github, and do all your changes for your special, we could think it as a Community Build for openwrt.

Once your board gets very large qty. selling, add it to openwrt list will be very simple.

Thank you, @RadioOperator, for your explanation. Unfortunately, that doesn't seem to work. The devices listed in the Table of Hardware (ToH) may not always be powered by OpenWrt anymore. For instance, I came across the TP-Link TL-WA850RE on the ToH list and purchased one from Amazon in 2022 to learn OpenWrt. However, it turned out that the TL-WA850RE, despite having the same enclosure, operates on different hardware than the one indicated on the ToH. As a consumer relying on the ToH, I'm concerned about whether the products listed there are readily available in the retail market and, more importantly, whether they function as described. I'm interested in understanding the approach that OpenWrt takes to ensure the compatibility of the entries listed.

9 out of 10 cases they are, but some vendors swap the hw during the life cycle of a device, and add a V2 to the model name.
Some just change the hw, and people find out the hard way.

They were, when device support was added.

That's user driven.
Sooner or later someone will soft brick their device, because TP-Link released a V2, or Xiaomi changed the flash chip, again.

Thank you, @frollic. It appears that OpenWRT sets the threshold for qualifying a device into its Table of Hardware (ToH) list at 1,000 marketable units. Once a device is listed on OpenWRT's ToH, it remains there unless there's a report indicating it shouldn't be. Consequently, it's reasonable to inquire about how OpenWRT measures whether a device has reached this threshold. Additionally, I'm curious about the procedure for manufacturers to connect with OpenWRT and notify them of the readiness of a new marketable OpenWRT device. Any clarification on these matters would be greatly appreciated. Thank you.

They will remain there, with the latest version of Openwrt supporting them listed, this doesn't have to be the latest available release of Openwrt though.

Not sure if manufacturers actually do this, or if people just buy device X, and port it.

Thanks @frollic. As @RadioOperator explains, if a manufacturer has 1,000 pieces of marketable devices, OpenWRT can list the devices in its ToH list. Meanwhile, if the "board gets very large qty. selling, add it to openwrt list will be very simple". There is a process that OpenWRT uses to choose which manufacturers' devices are on its ToH list. Though I don't know how exactly the process works, it must be related to the number of devices available on the market. The unclear part so far is how the process gets that marketing info input in without involving manufacturers.

GL having any manufacturer disclosing their "Openwrt supported hw sales".

Thanks @frollic. Would it be possible for you to further elaborate on

having any manufacturer disclosing their "Openwrt supported hw sales"

Should there be a bulletin board, email address, or some other communication channels that manufacturers can utilize to disclose their sales to OpenWrt?

I need some clarification. There are hundreds of dev boards boasting as operating by OpenWrt in the market, but their firmware is not included in the OpenWrt repository. I cannot blame those manufacturers for claiming their product as OpenWRT supported because OpenWrt refuses to list their firmware under its support list (ToH), for the dev kits' owners have too small market shares to mention. Then customers like myself, who want to get in touch with OpenWRT firmware, turn to the OpenWRT ToH list, but only find out the products there are not maintained and some are not running on OpenWRT anymore. I need help understanding the purpose of the ToH that OpenWRT provides on its site. Thanks.

if they're using some spinoff version of OpenWRT, and claim it's "OpenWRT", who should be blamed for the false advertising ?

why would they, if those devices aren't using native OpenWRT ?
if they're not supported "here", why should they be listed ?

you need to understand the differance between 3rd party firmwares, "based on" OpenWRT, and the real thing.
the "based on" part, is something they obviously don't tell you, it's not like it's boosting the sales.

Think it the other way round: Those manufacturers refuses to provide driver documentations to upstream their devices to linux kernel which OpenWrt team is unable to support them. If the device is capable and can be upstreamed, more users will tend to get them because the support is sustainable.

It's for users to understand the devices, even some of them are not supported, there should be a reason (e.g. Broadcom doesn't have driver, RAM/ROM too small for recent versions, etc....), it helps users to avoid unsupported device (or if you are a dev and interested to hack into it you can get better info first).

Thank you, @frollic and @fakemanhk, for your comments on this. Do you suggest the ToH guarantees the vendors' OpenWRT software standard? So far, my understanding is that OpenWRT does not verify products for startup manufacturers with a small market footprint. Still, the question is whether vendors need to initiate the procedure of enlisting their customized OpenWRT products to ToH after meeting a certain market threshold, such as 1,000 units.

Openwrt doesn't have anything to do with the vendor firmwares.
Will BMW guarantee the authenticity of your Toyota, if you slap on a BMW sticker ?

Someone does, doesn't matter if it's the vendor or someone who happens to own the device.

No one is checking market shares, nor will any vendor disclose them.

There is no point adding anything to the ToH, until the device is supported by genuine/ unmodified OpenWrt.

--
Yes, there is some small overlap, while support is pending/ close and patches in flight, but not merged yet, but we're talking about a couple of weeks here (and a clear indication that it will become official soon).
Anything that has production runs that exceed basement-built prototypes (many hundreds) basically qualifies - if someone does the work to get it supported).