mtk-20170518/target/linux/brcm47xx/Makefile, branch master MTK 20170518 : Mediatek SDK based on OpenWRT Barrier Breaker brcm47xx: switch to the kernel 4.14 2018-05-08T07:55:10+00:00 Rafał Miłecki rafal@milecki.pl 2018-05-05T22:06:14+00:00 97f3c0f041e7299884985ac4459f4668a2ceb726 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> 
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>
brcm47xx: use kernel 4.9 by default 2017-10-18T21:27:17+00:00 Hauke Mehrtens hauke@hauke-m.de 2017-10-18T19:53:31+00:00 2af10c30fe5a7f1d13a790187868c1ee2209a575 Kernel 4.9 is now working on the brcm47xx boards, we just recently fixed the problem that some boards did not boot at all, by changing the memory regions used to relocate the kernel to in the loader. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> 
Kernel 4.9 is now working on the brcm47xx boards, we just recently fixed
the problem that some boards did not boot at all, by changing the memory
regions used to relocate the kernel to in the loader.

Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
brcm47xx: bump kernel to 4.4 2016-10-24T15:22:23+00:00 Rafał Miłecki rafal@milecki.pl 2016-10-24T15:03:48+00:00 06405df7a8da24b7d735b32454c7d3b1f2ebaabc Kernel 4.4 was ready for brcm47xx for almost a year now but I kept postponing the bump due to problems with Linksys WRT300N v1.0. OpenWrt and LEDE with 4.4 were hanging at the booting with the: > Starting program at 0x80001000 (the last CFE message). This was a permanent state, "make distclean" wasn't helping, I spent hours debugging this and I was reliably reproducing the issue every time. I also reported it on linux-mips ML in the thread: > BCM4704 stopped booting with 4.4 (due to vmlinux size?) After ~month I started working on WRT300N again. I got hangs as expected every time I switched from 4.1 to 4.4. I started experimenting with: 1) TRX content (I tried dropping rootfs partition) 2) BZ_TEXT_START of lzma-loader 3) Flashing other variants of image: lzma compressed kernel (without a loader), gzip compressed one, uncompressed one. At some point I got rootfs-less image booting and after that I couldn't reproduce problem anymore, even with a complete firmware. It seems like hardware was in some locked/unstable state that got magically fixed. I have LEDE working now, tested it even with "make distclean", it seems we can bump kernel now. I'll keep testing it on WRT300N for some time. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> 
Kernel 4.4 was ready for brcm47xx for almost a year now but I kept
postponing the bump due to problems with Linksys WRT300N v1.0. OpenWrt
and LEDE with 4.4 were hanging at the booting with the:
> Starting program at 0x80001000
(the last CFE message).

This was a permanent state, "make distclean" wasn't helping, I spent
hours debugging this and I was reliably reproducing the issue every
time. I also reported it on linux-mips ML in the thread:
> BCM4704 stopped booting with 4.4 (due to vmlinux size?)

After ~month I started working on WRT300N again. I got hangs as expected
every time I switched from 4.1 to 4.4. I started experimenting with:
1) TRX content (I tried dropping rootfs partition)
2) BZ_TEXT_START of lzma-loader
3) Flashing other variants of image: lzma compressed kernel (without a
   loader), gzip compressed one, uncompressed one.

At some point I got rootfs-less image booting and after that I couldn't
reproduce problem anymore, even with a complete firmware. It seems like
hardware was in some locked/unstable state that got magically fixed.

I have LEDE working now, tested it even with "make distclean", it seems
we can bump kernel now. I'll keep testing it on WRT300N for some time.

Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
build: fix subtarget descriptions 2016-09-04T11:35:11+00:00 Felix Fietkau nbd@nbd.name 2016-09-04T11:34:18+00:00 aa53f78038d541052de8764323f6f26578327606 Move Target/Description above the target.mk include Signed-off-by: Felix Fietkau <nbd@nbd.name> 
Move Target/Description above the target.mk include

Signed-off-by: Felix Fietkau <nbd@nbd.name>
brcm47xx: update to kernel 4.1 2015-09-11T18:52:42+00:00 Hauke Mehrtens hauke@hauke-m.de 2015-09-11T18:52:42+00:00 5b04888848d160d8ba545ada4b7a66b0fbd450f3 This makes bcm53xx use kernel 4.1 by default now. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 46878 
This makes bcm53xx use kernel 4.1 by default now.

Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>

SVN-Revision: 46878
brcm47xx: switch to the otrx for verifying TRX images 2015-04-09T05:22:04+00:00 Rafał Miłecki zajec5@gmail.com 2015-04-09T05:22:04+00:00 44b128b0aa202e6539b9375197a0703c2c37dc36 This adds checking CRC32 of provided firmware image. Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 45316 
This adds checking CRC32 of provided firmware image.

Signed-off-by: Rafał Miłecki <zajec5@gmail.com>

SVN-Revision: 45316
brcm47xx: switch to 3.18 2015-03-16T23:05:43+00:00 Rafał Miłecki zajec5@gmail.com 2015-03-16T23:05:43+00:00 8f63c1405f4dcbe354ad18e1f36a3b768bdf6d0b Tested on BCM5357B0, BCM47186B0 and BCM4706. Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 44853 
Tested on BCM5357B0, BCM47186B0 and BCM4706.

Signed-off-by: Rafał Miłecki <zajec5@gmail.com>

SVN-Revision: 44853
kernel: makefiles: make use of new var KERNEL_PATCHVER 2014-10-24T19:34:02+00:00 Felix Fietkau nbd@openwrt.org 2014-10-24T19:34:02+00:00 c288d2d6d9a2dcca593157dae8175d40267135f4 replace all occurences of LINUX_VERSION with the cleaner approach. future kernel upgrades must mostly touch only one file. the only platform left is netlogic, because it uses a intermediate kernel 3.14.16 Signed-off-by: Bastian Bittorf <bittorf@bluebottle.com> SVN-Revision: 43047 
replace all occurences of LINUX_VERSION with the cleaner
approach. future kernel upgrades must mostly touch only
one file. the only platform left is netlogic, because it
uses a intermediate kernel 3.14.16

Signed-off-by: Bastian Bittorf <bittorf@bluebottle.com>

SVN-Revision: 43047
kernel: update 3.14 to 3.14.18 2014-09-10T21:40:19+00:00 Luka Perkov luka@openwrt.org 2014-09-10T21:40:19+00:00 02629d8f87303a03e3ac36f48c508242d9b8cb09 Targets were build tested and patches are refreshed. Signed-off-by: Luka Perkov <luka@openwrt.org> SVN-Revision: 42463 
Targets were build tested and patches are refreshed.

Signed-off-by: Luka Perkov <luka@openwrt.org>

SVN-Revision: 42463
brcm47xx/bcm53xx: improve description 2014-08-18T20:29:26+00:00 Hauke Mehrtens hauke@hauke-m.de 2014-08-18T20:29:26+00:00 32b3f9cdc66f2a89ecd4556725acb57d39c3a54d Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 42204 
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>

SVN-Revision: 42204