Adding MT7628DAN SoC Board to OpenWrt Hardware Support List

For Developers
42

https://openwrt.org/docs/guide-developer/working-with-github-pr

43

Thanks @frollic for providing the link. I have created the following remote Github repositories:

root@257322c3c053:/WorkingwithGitHub/openwrt_mango# git remote -v
origin	https://github.com/xxxxx/openwrt_mango.git (fetch)
origin	https://github.com/xxxxx/openwrt_mango.git (push)
upstream	https://github.com/openwrt/openwrt.git (fetch)
upstream	https://github.com/openwrt/openwrt.git (push)

In order to put my PR on OpenWrt Hardware Support List, should I do the following:

# Push new state to GitHub
# The upstream is the Openwrt original repository where I forked the codes from 
git push -f upstream testbranch

With Regards,

44

I recall someone suggesting that I create my pull request (PR) against the master branch in another thread. Iā€™m adding this suggestion here to ensure the thread remains complete and all relevant information is captured.

Thanks for your attention to this matter!

45

So far, the process for adding a new device to the OpenWrt Hardware Support List appears to involve two separate components:

  1. Following the steps outlined in adding a device to the Table of Hardware (ToH).
  2. Adding the source code into the OpenWrt repository as described in Adding a New Device.

I've encountered difficulties at the step where I need to contact the maintainers responsible for the ToH and the OpenWrt repository. Given that there are over 2,000 vendor products listed in the ToH, it seems logical that there is a way to move forward from here. However, I'll pause my efforts and revisit this once my product's market size increasesā€”perhaps around the 1,000 units mark, as someone suggested.

For now, I'll leave this ticket unsolved and plan to explore the process further when the time is right.

Thanks for all the guidance so far.

With Regards,

46

That's not entirely accurate.

In addition you Private Messaged me twice. Perhaps I overlooked it - offer my apologies, but you never mentioned you were trying to add a new make/model to the Table of Hardware.

You may wish to make a thread specifically inquiring this - that's done for users all the time.

EDIT:

Keep this in mind when doing so - I assume this is still relevant:

This has now changed, correct?

47

To be clear, there is no reason to add entries to the ToH until and unless a specific device is either officially supported or it is supportable and within reach of gaining official OpenWrt support. Currently, it appears that the device(s) you are referring to are not that close to supportability since the are using an SDK that does not come from the official project.

As such, entries in the ToH are premature until it can be demonstrated that the official SDK (plus some open source patches) can run produce firmware that will run on the device.

1 Like
48

Hi @lleachii,

Thanks for your message. Let's focus on the procedure about adding "a new make/model" here. Would appreciate any additional input you might have on the following:

  1. Adding a Device to the Table of Hardware (ToH):
    Iā€™m following the procedure outlined here, but Iā€™m currently stuck at step 3. I receive a "permission denied" message when trying to access the dataentry_page_link. Do you have any advice on how to resolve this issue?
  2. Adding Source Code to the OpenWrt Repository:
    According to the guide on Adding a New Device, it seems that specific permissions are required to push source code to the OpenWrt repository. Iā€™m unsure who to contact to obtain these permissions.

Iā€™m looking to understand the process better and get the necessary permissions to proceed. Any guidance or contacts you could provide would be greatly appreciated.

Thanks in advance for your input. Together, we can make the procedure for adding a device to the OpenWrt Hardware Support List more accessible and useful to vendors looking to build applications that comply with OpenWrt standards.

Thanks.

49

You've been told, multiple times, there's no point in doing 1, if 2 isn't even in progress.

Last time, was in the 2nd latest post, by @psherman.

1 Like
50

Have you successfully built OpenWrt (obtained directly from OpenWrt.org) for the device in question?

1 Like
51

Thanks @frollic and @psherman

Yes. I have successfully built OpenWrt, which was cloned from https://git.openwrt.org/openwrt/openwrt.git

Iā€™m currently waiting to move forward with the next steps in the procedure once my device has reached a significant market presence (1,000 units, as someone suggested).

With Regards,

53

Hi @frollic,

I want to clarify that I shouldnā€™t take credit for the number 1,000 units; it was mentioned as an example for large quantities by @RadioOperator in post #7:

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

That said, I am aiming to reach that target.

Iā€™ll probably close this ticket for now and will open a new one when Iā€™m ready to continue with the procedure.

Thanks for your understanding and support!

Best regards,

54

I already told you: forget the qty of 1000 units. It means many units sold out.

1 Like
55

Hi @frollic ,

Before I close this ticket, could you please confirm if there is any dependency between the following two procedures for adding a new device to the Table of Hardware (ToH)?

  1. Following the steps outlined in Adding a Device to the Table of Hardware (ToH).
  2. Adding the source code to the OpenWrt repository as described in Adding a New Device.

Thanks for your assistance!

With Regards,

56

How to identify your product?

Brand name /

Model no / hardware spec / website link ?

1 Like
57

OK.

@mango ,

Can you please explain how I can purchase your device now - commercially, in the US?

I would like to flash OpenWrt on it via suysupgrade (etc.) from official channels to ensure a trusted firmware - and then proceed to use it.

1 Like
58

There isn't, but there's no point in doing 1, until you're almost there with 2.

59

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.