Hello, On Mon, 15 Jun 2015 17:54:41 +0200, Simon Guinot wrote: > > The current armada-370-neta would limit the HW checksumming features to > > packets smaller than 1600 bytes, while a new armada-xp-neta would not > > have this limit. > > This was also my first idea. But by doing this, we take the risk of > losing the HW checksumming feature with jumbo frames on some currently > working Armada XP setups. This may happen for example if a user is able > to update the kernel but not the on-board DTB. In order to fix a feature > on a SoC, we are breaking the DTB-kernel compatibility for the very same > feature on an another SoC. I am not sure it is OK. > > Are you comfortable with that ? It's either that, or keep a not-ideal solution for this problem. I'm not a strong believer in the need of enforcing the DT as a stable ABI, and I am not aware of anyone using Marvell platforms with a DTB that isn't changed together with the kernel. So my preference goes to fixing the problem properly, rather than doing non-ideal solutions. Though this is just my own opinion, and I am not a maintainer of the mach-mvebu platform. Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html