aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ipq40xx/patches-4.14/050-0005-mtd-nand-force-drivers-to-explicitly-send-READ-PROG-.patch
diff options
context:
space:
mode:
authorRafał Miłecki <rafal@milecki.pl>2018-05-06 00:06:14 +0200
committerRafał Miłecki <rafal@milecki.pl>2018-05-08 09:55:10 +0200
commit97f3c0f041e7299884985ac4459f4668a2ceb726 (patch)
tree1fdf7500d7632c3858e833f32ffff4504cdf0930 /target/linux/ipq40xx/patches-4.14/050-0005-mtd-nand-force-drivers-to-explicitly-send-READ-PROG-.patch
parentf9dcdc7fefcab5ec9b15b0f3c87dfebef37ecaa3 (diff)
downloadupstream-97f3c0f041e7299884985ac4459f4668a2ceb726.tar.gz
upstream-97f3c0f041e7299884985ac4459f4668a2ceb726.tar.bz2
upstream-97f3c0f041e7299884985ac4459f4668a2ceb726.zip
brcm47xx: switch to the kernel 4.14
The biggest (and the only?) disadventage of this is obviously an increased image size. For mips74k the size of vmlinux goes up from 4186684 B to 4701436 B. Most devices use LZMA compressed kernel so probably more important is vmlinux.lzma size which goes up from 1342945 B to the 1508498 B. Still this isn't something that should stop target kernel bump. There are various adventages of kernel 4.14. If kernel / image size is a serious concern for anyone, it's perfectly possible to use previous release which is pretty solid for the brcm47xx. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> Cc: Paul Wassi <p.wassi@gmx.at> Cc: Hauke Mehrtens <hauke@hauke-m.de>
Diffstat (limited to 'target/linux/ipq40xx/patches-4.14/050-0005-mtd-nand-force-drivers-to-explicitly-send-READ-PROG-.patch')
0 files changed, 0 insertions, 0 deletions