On Thu, 16 May 2019 22:35:35 +0200 Tomasz Maciej Nowak <[email protected]> wrote:
> Hi Marek, > > W dniu 16.05.2019 o 20:38, Marek Behún pisze: > > Add support for kernel 4.19 to the mvebu target. > > > > This is the first version, unfortunately I only have Turris Omnia and > > Turris Mox to test this on, and Turris Mox is not yet supported in these > > patches. > > You beat me to it, but not only You > https://github.com/openwrt/openwrt/pull/1646. > Only recently I had time to look at it and this: > https://github.com/tmn505/openwrt/tree/mvebu-4.19 > is my shot at it (based on initial Marko Ratkaj work). I asked Sébastien in > mentioned PR on GitHub if I can send it here. > > Just yesterday and today I got report from owners of WRT1900AC and WRT32X > that their > NAND chips are working: > https://forum.openwrt.org/t/kernel-4-19-upgrade-issue-on-mvebu-target-s/32966/32 > https://forum.openwrt.org/t/kernel-4-19-upgrade-issue-on-mvebu-target-s/32966/34 > So it seems that most difficult devices are working. Unfortunately I don't > have > anything with SFP, so would be nice to know if anything needs to be added. > > > > > So if you guys could try this and give feedback. > > Most of the kept patches are similar and on ESPRESSObin everything seems to > work OK. This is not only ESPRESSObin but also the 32 bit mvebu devices. Ok, I will probably try to merge my changes with those in those pull requests. Should I then open a github pull request? Or send a patch series via email? Marek _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
