▲ | evanjrowley a day ago | |||||||
I'd like to see more collaboration between OpenWRT and SBC makers like Banana Pi. While I love FriendlyELEC and GLi.Net for creating fantastic OpenWRT hardware, I abhor the fact that I they use OpenWRT forks. As an OpenWRT user, I really want to just upload my config files and hit the ground running. Not interested in fooling around with the user interfaces of these 3rd party spinoffs. I'd also like to see the Wiki examples supported by complete configurations. A lot of the routing examples don't show enough of what's actually required to make them work. Perhaps create complete configurations that can be applied to a virtualized OpenWRT instance? | ||||||||
▲ | likeabatterycar a day ago | parent | next [-] | |||||||
Is it really a burden worth complaining about to overwrite the factory fork with OpenWRT? It takes five minutes of your time. You should be doing this regardless, even if it shipped with vanilla OpenWRT, because factory firmware is often outdated out of the box. | ||||||||
| ||||||||
▲ | frankharv a day ago | parent | prev [-] | |||||||
BananaPi dont make anything from what I see. SinoVOIP is one manufacturer but who will make up the boards Device Tree Overlays???? Leave it to poor saps on a Wiki to do it for them... Raxda has tried to support some but they use a shitty old u-boot Linero tree like many of these joke boards. Hello. Please upsteam your work and get rid of the 2017 Uboot tree. Geez |