<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mtk-20170518/target/linux/ramips/rt305x, branch master</title>
<subtitle>MTK 20170518 : Mediatek SDK based on OpenWRT Barrier Breaker</subtitle>
<link rel='alternate' type='text/html' href='http://www.chd.sx/cgit/mtk-20170518/'/>
<entry>
<title>kernel: only optimized for size if small_flash</title>
<updated>2018-07-12T16:15:32+00:00</updated>
<author>
<name>Mathias Kresin</name>
<email>dev@kresin.me</email>
</author>
<published>2018-07-09T18:48:56+00:00</published>
<link rel='alternate' type='text/html' href='http://www.chd.sx/cgit/mtk-20170518/commit/?id=cf7154db07c0b8746be290c9e11dcab3c91d237e'/>
<id>cf7154db07c0b8746be290c9e11dcab3c91d237e</id>
<content type='text'>
Add a new config option to allow to select the default compile
optimization level for the kernel.

Select the optimization for size by default if the small_flash feature is
set. Otherwise "Optimize for performance" is set.

Add the small_flash feature flag to all (sub)targets which had the
optimization for size in their default kernel config.

Remove CC_OPTIMIZE_FOR_* symbols from all kernel configs to apply the new
setting.

Exceptions to the above are:

  - lantiq, where the optimization for size is only required for the
    xway_legacy subtarget but was set for the whole target
  - mediatek, ramips/mt7620 &amp; ramips/mt76x8 where boards should have
    plenty of space and an optimization for size doesn't make much sense
  - rb532, which has 128MByte flash

Signed-off-by: Mathias Kresin &lt;dev@kresin.me&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Add a new config option to allow to select the default compile
optimization level for the kernel.

Select the optimization for size by default if the small_flash feature is
set. Otherwise "Optimize for performance" is set.

Add the small_flash feature flag to all (sub)targets which had the
optimization for size in their default kernel config.

Remove CC_OPTIMIZE_FOR_* symbols from all kernel configs to apply the new
setting.

Exceptions to the above are:

  - lantiq, where the optimization for size is only required for the
    xway_legacy subtarget but was set for the whole target
  - mediatek, ramips/mt7620 &amp; ramips/mt76x8 where boards should have
    plenty of space and an optimization for size doesn't make much sense
  - rb532, which has 128MByte flash

Signed-off-by: Mathias Kresin &lt;dev@kresin.me&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ramips: add dwr-512 jboot firmware configuration</title>
<updated>2018-04-08T07:51:06+00:00</updated>
<author>
<name>Giuseppe Lippolis</name>
<email>giu.lippolis@gmail.com</email>
</author>
<published>2018-04-05T16:01:41+00:00</published>
<link rel='alternate' type='text/html' href='http://www.chd.sx/cgit/mtk-20170518/commit/?id=1680ae7eae2602dd85463a71f88d0012b236bff7'/>
<id>1680ae7eae2602dd85463a71f88d0012b236bff7</id>
<content type='text'>
The previous fw version require the replacement of the stock bootloader
with u-boot. This prevent an easy stock restore of the original fw.

Now a proper fw util has been developed to manage the stock jboot
bootloader. Therefore make sense have a fw image for the stock
bootloader.

The old fw configuration (u-boot) is not compatible with the new one
and will not be supported anymore.

So at the end 2 image can be generated:

1) factory image with jboot bootloader
     openwrt-ramips-rt305x-dwr-512-b-squashfs-factory.bin
2) sysupgrade image with jboot bootloader
     openwrt-ramips-rt305x-dwr-512-b-squashfs-sysupgrade.bin

Signed-off-by: Giuseppe Lippolis &lt;giu.lippolis@gmail.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The previous fw version require the replacement of the stock bootloader
with u-boot. This prevent an easy stock restore of the original fw.

Now a proper fw util has been developed to manage the stock jboot
bootloader. Therefore make sense have a fw image for the stock
bootloader.

The old fw configuration (u-boot) is not compatible with the new one
and will not be supported anymore.

So at the end 2 image can be generated:

1) factory image with jboot bootloader
     openwrt-ramips-rt305x-dwr-512-b-squashfs-factory.bin
2) sysupgrade image with jboot bootloader
     openwrt-ramips-rt305x-dwr-512-b-squashfs-sysupgrade.bin

Signed-off-by: Giuseppe Lippolis &lt;giu.lippolis@gmail.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ramips: drop linux 4.9 support</title>
<updated>2018-04-06T16:21:45+00:00</updated>
<author>
<name>Felix Fietkau</name>
<email>nbd@nbd.name</email>
</author>
<published>2018-04-06T16:20:46+00:00</published>
<link rel='alternate' type='text/html' href='http://www.chd.sx/cgit/mtk-20170518/commit/?id=dea9922acd290b37a784d354892a44684a8fb696'/>
<id>dea9922acd290b37a784d354892a44684a8fb696</id>
<content type='text'>
4.14 has been tested a lot by a number of users, and we want to use it
for the release.

Signed-off-by: Felix Fietkau &lt;nbd@nbd.name&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
4.14 has been tested a lot by a number of users, and we want to use it
for the release.

Signed-off-by: Felix Fietkau &lt;nbd@nbd.name&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>kernel: optimize for performance by default starting with 4.14</title>
<updated>2018-02-24T15:05:28+00:00</updated>
<author>
<name>Felix Fietkau</name>
<email>nbd@nbd.name</email>
</author>
<published>2018-02-22T19:18:58+00:00</published>
<link rel='alternate' type='text/html' href='http://www.chd.sx/cgit/mtk-20170518/commit/?id=46c49d83815a84225c1bfcb54fd96b9f73c7c2cb'/>
<id>46c49d83815a84225c1bfcb54fd96b9f73c7c2cb</id>
<content type='text'>
Keep size optimizations for smaller targets that already switched

Signed-off-by: Felix Fietkau &lt;nbd@nbd.name&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Keep size optimizations for smaller targets that already switched

Signed-off-by: Felix Fietkau &lt;nbd@nbd.name&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ramips: preliminary support for 4.14</title>
<updated>2018-02-15T09:46:39+00:00</updated>
<author>
<name>Roman Yeryomin</name>
<email>roman@advem.lv</email>
</author>
<published>2018-01-16T22:07:58+00:00</published>
<link rel='alternate' type='text/html' href='http://www.chd.sx/cgit/mtk-20170518/commit/?id=f4e5880d0f3496a3151fe24d87ca2d08d3403a83'/>
<id>f4e5880d0f3496a3151fe24d87ca2d08d3403a83</id>
<content type='text'>
- removed upstreamed patches
- 0901-spansion_nand_id_fix.patch is disabled, not clear if it's needed

Signed-off-by: Roman Yeryomin &lt;roman@advem.lv&gt;
Signed-off-by: John Crispin &lt;john@phrozen.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
- removed upstreamed patches
- 0901-spansion_nand_id_fix.patch is disabled, not clear if it's needed

Signed-off-by: Roman Yeryomin &lt;roman@advem.lv&gt;
Signed-off-by: John Crispin &lt;john@phrozen.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>kernel: add support for limiting 4K erase sector support based on flash chip size</title>
<updated>2017-11-06T15:38:25+00:00</updated>
<author>
<name>Felix Fietkau</name>
<email>nbd@nbd.name</email>
</author>
<published>2017-11-03T08:53:54+00:00</published>
<link rel='alternate' type='text/html' href='http://www.chd.sx/cgit/mtk-20170518/commit/?id=c08293893aadca182b52ef96d3c2b1700282f0f2'/>
<id>c08293893aadca182b52ef96d3c2b1700282f0f2</id>
<content type='text'>
Some targets need 4K sectors for small flash chips (e.g. some
routerboards, where the entire chip is just one "erase block"), whereas
on other devices 4K sectors lead to horrible flash erase/write
performance.

Set the default limit in the generic kernel configuration to 4 MiB to
ensure that all new platforms don't use 4K sectors for bigger flash
chips. On all existing targets use 16 MiB for now to avoid regressions.
They will be changed individually in follow-up commits.

Signed-off-by: Felix Fietkau &lt;nbd@nbd.name&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Some targets need 4K sectors for small flash chips (e.g. some
routerboards, where the entire chip is just one "erase block"), whereas
on other devices 4K sectors lead to horrible flash erase/write
performance.

Set the default limit in the generic kernel configuration to 4 MiB to
ensure that all new platforms don't use 4K sectors for bigger flash
chips. On all existing targets use 16 MiB for now to avoid regressions.
They will be changed individually in follow-up commits.

Signed-off-by: Felix Fietkau &lt;nbd@nbd.name&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ramips: drop stray kernel 4.4 configs</title>
<updated>2017-07-27T07:17:25+00:00</updated>
<author>
<name>Mathias Kresin</name>
<email>dev@kresin.me</email>
</author>
<published>2017-07-25T17:37:08+00:00</published>
<link rel='alternate' type='text/html' href='http://www.chd.sx/cgit/mtk-20170518/commit/?id=7985bf23efe19a48f84381f9f565dc64e8c4b753'/>
<id>7985bf23efe19a48f84381f9f565dc64e8c4b753</id>
<content type='text'>
The kernel 4.4 patches where already removed with the bump to 4.9. Drop
the the subtarget configs as well.

Signed-off-by: Mathias Kresin &lt;dev@kresin.me&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The kernel 4.4 patches where already removed with the bump to 4.9. Drop
the the subtarget configs as well.

Signed-off-by: Mathias Kresin &lt;dev@kresin.me&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>kernel: cleanup CONFIG_SCHED_HRTICK</title>
<updated>2017-06-29T02:46:59+00:00</updated>
<author>
<name>Stijn Tintel</name>
<email>stijn@linux-ipv6.be</email>
</author>
<published>2017-06-29T02:46:59+00:00</published>
<link rel='alternate' type='text/html' href='http://www.chd.sx/cgit/mtk-20170518/commit/?id=880f73c327799e402a5bd47bb2f324848951af63'/>
<id>880f73c327799e402a5bd47bb2f324848951af63</id>
<content type='text'>
Remove CONFIG_SCHED_HRTICK from target configs, as it was added to the
generic config in b47fd7656336162360ebf66147326763ddae3f8d.

Signed-off-by: Stijn Tintel &lt;stijn@linux-ipv6.be&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Remove CONFIG_SCHED_HRTICK from target configs, as it was added to the
generic config in b47fd7656336162360ebf66147326763ddae3f8d.

Signed-off-by: Stijn Tintel &lt;stijn@linux-ipv6.be&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>kernel: disable CONFIG_SG_POOL by default</title>
<updated>2017-06-07T16:31:10+00:00</updated>
<author>
<name>Sergey Ryazanov</name>
<email>ryazanov.s.a@gmail.com</email>
</author>
<published>2017-05-30T21:46:40+00:00</published>
<link rel='alternate' type='text/html' href='http://www.chd.sx/cgit/mtk-20170518/commit/?id=68e7a2a0b7d8730933d3788806c3480c8f0d09de'/>
<id>68e7a2a0b7d8730933d3788806c3480c8f0d09de</id>
<content type='text'>
CONFIG_SG_POOL symbol is selected only by CONFIG_SCSI, since the last
one is disabled by default then disable CONFIG_SG_POOL by default too.
And explicitly enable it only for platforms that use CONFIG_SCSI.

Signed-off-by: Sergey Ryazanov &lt;ryazanov.s.a@gmail.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
CONFIG_SG_POOL symbol is selected only by CONFIG_SCSI, since the last
one is disabled by default then disable CONFIG_SG_POOL by default too.
And explicitly enable it only for platforms that use CONFIG_SCSI.

Signed-off-by: Sergey Ryazanov &lt;ryazanov.s.a@gmail.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ramips: purge default packages on MT7621</title>
<updated>2017-05-04T12:13:23+00:00</updated>
<author>
<name>Daniel Golle</name>
<email>daniel@makrotopia.org</email>
</author>
<published>2017-05-04T12:07:47+00:00</published>
<link rel='alternate' type='text/html' href='http://www.chd.sx/cgit/mtk-20170518/commit/?id=d17cb4a68a4544dca690629ee9a2483da29fa42a'/>
<id>d17cb4a68a4544dca690629ee9a2483da29fa42a</id>
<content type='text'>
In order to have a smaller initramfs image remove all packages not
needed on all devices and add them explicitely for those actually
needing them. Also remove wpad-mini from ramips default package set
and add it to all sub-targets except for MT7621.
While at it reorder packages alphabetically and replace kmod-mt76 with
kmod-mt7603 and/or kmod-mt76x2 depending on the chip actually used on
a specific board.

Hopefully fixes FS#758

Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
In order to have a smaller initramfs image remove all packages not
needed on all devices and add them explicitely for those actually
needing them. Also remove wpad-mini from ramips default package set
and add it to all sub-targets except for MT7621.
While at it reorder packages alphabetically and replace kmod-mt76 with
kmod-mt7603 and/or kmod-mt76x2 depending on the chip actually used on
a specific board.

Hopefully fixes FS#758

Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
</pre>
</div>
</content>
</entry>
</feed>
