I have no experience with creating proper device support patches, and would really appretiate help with upstreaming of Turris Omnia. Even though this router comes with OpenWRT (fork), the devs are shy to submit the patch themselves.
Do you have a repo/branch with the patches applied? I started copying them over one by one a while ago and sometimes the build failed. I suggest we start a new branch and test this very well before submitting a patch.
What target image did you build? The medkit?
How well does the Omnia storage work with ext4? I heard btrfs is better suited (one of the devs said that IIRC on the omnia forum)
I own a Turris Omnia as well, but rely heavily on it. Testing capabilities are limited
The most important thing to get started would be to beat the crucial turris omnia specific hardware support in state acceptable for merging, this means no special kernel/ u-boot forks. For hardware like the turris omnia (with plenty of flash, which lends itself to in-place upgrading), additional features like btrfs might be nice to have, but in the grand scheme of things those will be more difficult to merge and should be much less important (as in optional) than getting basic hardware support applied (in a way that it works and behaves just like any other LEDE router).
git clone --recursive https://github.com/amq/omnia-kiss.git
cd omnia-kiss
rsync -a custom/ lede/
cd lede
./scripts/feeds update -a
./scripts/feeds install -a
make defconfig
make -j2 V=s 2>&1 | tee build.log | grep -i error
I hope that it will be official support from LEDE for Turris Omnia, because I have the impression that Team Turris is not trying to help and develop the project.
I can also volunteer for testing, at the moment my turris is not in a critical role yet.
I've got a lot of experience building custom OpenWRT images, but I'm not a programmer who is really suitable for trying to change the code to meet the quality standards of upstream.
Like slh above, I think the most important thing is to get the kernel and u-boot changes in place (along with a build target). Once that's in place, I'll happily dump the rest of the turris specific software and stick with plain LEDE packages
once we get it running, closing the other gaps will be far easier.
anyone know why omnia-devs wont engage in giving back to wireless freedom?
The usual issue is just that they are busy making it work for their users
(fixing issues, updating version, working out kinks in the software)
Remember, this wasn't done as a croudsourced router for the sake of doing an
open router, this is an organization who needed a router for their own purposes
(to replace prior versions they have deployed), and they decided to expand their
users and gain some funding for the project via croudsourcing. So they have
their internal needs to meet and customers to keep happy, not just us
open-source folks.
While that is probably their reasoning, it's still deeply flawed, because with each week going by, their workload to either backport upstream (OpenWrt or LEDE) or to ignore upstream and start doing everything themselves becomes larger and larger - much larger than committing basic hardware support early on.
I boulding medikit omnia firmware based on Xiche commits.
Image boot OK.
Port WAN not working ( I switch wan to LAN4 port)
When I connect lenovo tablet to 2,4GHz WiFi, router lost connection on LAN/WAN and wifi is down.
WiFi speed is good (tested on intel 7260ac) - ~320Mbit/s
I have omnia with standard compex wireless card.