mtk-20170518/target/linux/ramips/mt7621/config-4.4, branch v17.01.2 MTK 20170518 : Mediatek SDK based on OpenWRT Barrier Breaker ramips: Add I2C driver to the default kernel config 2017-01-15T16:43:05+00:00 Rosen Penev rosenp@gmail.com 2017-01-13T15:14:38+00:00 80768ddccd6275d1506badcf57ae31560ca19da2 I made a commit that added the RTC driver to the kernel config with the intent that it would fix hctosys. Unfortunately while the RTC driver is in there, it's connected through I2C, the driver for which comes in module form and is thus loaded late. After this commit, it works fine. Signed-off-by: Rosen Penev <rosenp@gmail.com> 
I made a commit that added the RTC driver to the kernel config with
the intent that it would fix hctosys. Unfortunately while the RTC
driver is in there, it's connected through I2C, the driver for which
comes in module form and is thus loaded late. After this commit, it
works fine.

Signed-off-by: Rosen Penev <rosenp@gmail.com>
kernel: remove ubifs xz decompression support 2017-01-09T13:07:06+00:00 Felix Fietkau nbd@nbd.name 2017-01-09T13:00:24+00:00 018d80007e6d9469077d938872e605f826010767 It has been unused, and less useful than squashfs for cases where flash space usage matters. Signed-off-by: Felix Fietkau <nbd@nbd.name> 
It has been unused, and less useful than squashfs for cases where flash
space usage matters.

Signed-off-by: Felix Fietkau <nbd@nbd.name>
ramips: Add RTC driver to kernel for working hctosys 2016-10-31T15:41:26+00:00 Rosen Penev rosenp@gmail.com 2016-10-30T03:50:45+00:00 369884c2a18cf082f0d13652deaf2415700dc842 Build the RTC driver into the kernel, (and remove the optional module), in order to make hctosys working. (Currently the module is loaded after hctosys has failed previously) Signed-off-by: Rosen Penev <rosenp@gmail.com> 
Build the RTC driver into the kernel, (and remove the optional module), in order
to make hctosys working. (Currently the module is loaded after hctosys has failed previously)

Signed-off-by: Rosen Penev <rosenp@gmail.com>
ramips: fix wrong blocksizes 2016-09-15T07:53:37+00:00 Mathias Kresin dev@kresin.me 2016-09-14T17:11:19+00:00 eb88a9cacb41a69cdeb335298882b218361ff825 The D-Link DIR-860L B1 has a flash chip which doesn't support 4K sectors. Since the DIR-860L B1 was the only mt7621 board which had the 4k blocksize set, the 4K sector support is removed from the kernel config. I've checked the flash chips of all boards having set a 4K blocksize again. This time I searched harder to finding bootlogs instead of relying on wikis articles and/or the device tree source file. The Planex MZK-DP150N has an en25q32b instead of the mentioned one in the dts. Albeit the en25q32b supports 4K sectors, 4K support is not enabled in the driver. Change the blocksize for this board back to 64K. Reported-by: Russell Senior <russell@personaltelco.net> Signed-off-by: Mathias Kresin <dev@kresin.me> 
The D-Link DIR-860L B1 has a flash chip which doesn't support
4K sectors. Since the DIR-860L B1 was the only mt7621 board which had
the 4k blocksize set, the 4K sector support is removed from the kernel
config.

I've checked the flash chips of all boards having set a 4K blocksize
again. This time I searched harder to finding bootlogs instead of
relying on wikis articles and/or the device tree source file.

The Planex MZK-DP150N has an en25q32b instead of the mentioned one in
the dts. Albeit the en25q32b supports 4K sectors, 4K support is not
enabled in the driver. Change the blocksize for this board back to 64K.

Reported-by: Russell Senior <russell@personaltelco.net>
Signed-off-by: Mathias Kresin <dev@kresin.me>
ramips: enable 4K sector support in kernel config 2016-09-13T20:06:08+00:00 Mathias Kresin dev@kresin.me 2016-09-13T19:47:25+00:00 925e63e71fa6691f3fa374f71c77d0a91c7e7539 This is a follow up to 28110727f1d513a6c4c13aa87ecb606aa5d306eb "ramips: set blocksize for 4MB devices". I've missed to include the required changes of the kernel configs to enable 4K sector size support. The option is only enabled for targets having boards with 4k sector size flash chips. Signed-off-by: Mathias Kresin <dev@kresin.me> 
This is a follow up to 28110727f1d513a6c4c13aa87ecb606aa5d306eb
"ramips: set blocksize for 4MB devices". I've missed to include the
required changes of the kernel configs to enable 4K sector size
support.

The option is only enabled for targets having boards with 4k sector
size flash chips.

Signed-off-by: Mathias Kresin <dev@kresin.me>
ramips: mt7621: add missing kernel symbol 2016-07-16T11:59:12+00:00 Jo-Philipp Wich jo@mein.io 2016-07-16T11:59:06+00:00 b051ac76e83f2245f06fda852b0779f328d2954b Signed-off-by: Jo-Philipp Wich <jo@mein.io> 
Signed-off-by: Jo-Philipp Wich <jo@mein.io>
ramips: fix the number of uarts for each SoC 2016-06-03T10:20:33+00:00 Álvaro Fernández Rojas noltari@gmail.com 2016-05-29T10:55:12+00:00 604b92dbd0597e1a12a16c05ce0bb2c979326137 - Use default number of uarts (2) for rt288x/rt305x/rt3883/mt7620. - Allow up to 3 uarts on MT7621 and MT7628. - Remove unneeded SERIAL_8250_RT288X for MT7628. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> 
- Use default number of uarts (2) for rt288x/rt305x/rt3883/mt7620.
- Allow up to 3 uarts on MT7621 and MT7628.
- Remove unneeded SERIAL_8250_RT288X for MT7628.

Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
ramips: add linux 4.4 support, update mt7621 subtarget to 4.4 2016-03-07T16:33:34+00:00 Felix Fietkau nbd@openwrt.org 2016-03-07T16:33:34+00:00 d041e8b44b042d373b0b474ee69caed840f9a541 Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 48951 
Signed-off-by: Felix Fietkau <nbd@openwrt.org>

SVN-Revision: 48951