mtk-20170518/target/linux/ramips/image/rt305x.mk, branch v17.01.3 MTK 20170518 : Mediatek SDK based on OpenWRT Barrier Breaker ramips: fix Omnima MiniEMBWiFi image 2017-08-02T19:16:20+00:00 Mathias Kresin dev@kresin.me 2017-07-31T18:21:12+00:00 48798af6d224ae5c2e567be5b4ff88283ab9c208 Reference the Omnima MiniEMBWiFi device tree source file in the image build code. Otherwise the dts of the image processed before is used. Signed-off-by: Mathias Kresin <dev@kresin.me> 
Reference the Omnima MiniEMBWiFi device tree source file in the image
build code. Otherwise the dts of the image processed before is used.

Signed-off-by: Mathias Kresin <dev@kresin.me>
ramips: build HuaWei HG255D image 2017-08-02T19:16:20+00:00 Mathias Kresin dev@kresin.me 2017-07-31T18:19:14+00:00 1a050c83ac25b4c65b68f704fd70c9f90f4c25ed The code to build an image was disabled some time ago for unknown reasons albeit the image looks fine. Signed-off-by: Mathias Kresin <dev@kresin.me> 
The code to build an image was disabled some time ago for unknown
reasons albeit the image looks fine.

Signed-off-by: Mathias Kresin <dev@kresin.me>
ramips: add om-watchdog to rut5xx DEVICE_PACKAGES 2017-05-15T20:56:01+00:00 Steffen Weinreich steve@weinreich.org 2017-04-25T14:44:39+00:00 4bd98e9224cfd89a2d8de5759a7823964d89225f Add om-watchdog as default package for rut5xx. Signed-off-by: Steffen Weinreich <steve@weinreich.org> 
Add om-watchdog as default package for rut5xx.

Signed-off-by: Steffen Weinreich <steve@weinreich.org>
ramips: added image size into dwr-512 DT 2017-02-13T09:25:19+00:00 Giuseppe Lippolis giu.lippolis@gmail.com 2017-02-11T17:53:33+00:00 e5060b32e5c662899971f450ea0983005e02ec57 Signed-off-by: Giuseppe Lippolis <giu.lippolis@gmail.com> 
Signed-off-by: Giuseppe Lippolis <giu.lippolis@gmail.com>
ramips: fix NixcoreX1 profiles 2016-12-28T22:05:24+00:00 Rafał Miłecki rafal@milecki.pl 2016-12-28T22:01:11+00:00 939ef157da1bb88a99453a59d0ae5bc2c7779aa5 There was a typo in Makefile that prevented using these profiles. Fixes: a75ce960ac1 ("ramips: use different board names for variants") Signed-off-by: Rafał Miłecki <rafal@milecki.pl> 
There was a typo in Makefile that prevented using these profiles.

Fixes: a75ce960ac1 ("ramips: use different board names for variants")
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
ramips: use new image build code for more devices 2016-12-24T09:03:38+00:00 Mathias Kresin dev@kresin.me 2016-11-21T07:46:48+00:00 0cf581ca3a2a692938003a7038d93f2e24d9125a Signed-off-by: Mathias Kresin <dev@kresin.me> 
Signed-off-by: Mathias Kresin <dev@kresin.me>
ramips: use different board names for variants 2016-12-24T09:03:38+00:00 Mathias Kresin dev@kresin.me 2016-12-23T08:46:48+00:00 a75ce960ac1b9d67af280e17e1e653b3b39def20 Use different names for flash size related board variants, to make sure that only images for the actual flash size are considered as valid by the image validation code. Remove the flash size suffix from the string returned by ramips_board_detect() to ensure that existing scripts relying on the former used boardname are still working. Signed-off-by: Mathias Kresin <dev@kresin.me> 
Use different names for flash size related board variants, to make sure
that only images for the actual flash size are considered as valid by
the image validation code.

Remove the flash size suffix from the string returned by
ramips_board_detect() to ensure that existing scripts relying on the
former used boardname are still working.

Signed-off-by: Mathias Kresin <dev@kresin.me>
ramips: sort rt305x image file alphabetical 2016-12-24T09:03:38+00:00 Mathias Kresin dev@kresin.me 2016-11-27T09:46:20+00:00 29f5e643ad130c138507dc767187744ad710208a Signed-off-by: Mathias Kresin <dev@kresin.me> 
Signed-off-by: Mathias Kresin <dev@kresin.me>
ramips: fix image validation errors 2016-12-24T09:03:38+00:00 Mathias Kresin dev@kresin.me 2016-12-01T06:37:03+00:00 d2b6bf141662429d542b23e9e8f44245a77710a5 The name from the Device define will be used in the metadata. Due to typos/different spelling, this name might not match the one exported in /lib/ramips.sh. Fix all name mismatches which were found by checking if the name used in the metadata exists in /lib/ramips.sh. Signed-off-by: Mathias Kresin <dev@kresin.me> 
The name from the Device define will be used in the metadata. Due to
typos/different spelling, this name might not match the one exported in
/lib/ramips.sh.

Fix all name mismatches which were found by checking if the name used
in the metadata exists in /lib/ramips.sh.

Signed-off-by: Mathias Kresin <dev@kresin.me>
ramips: Add device DLINK DWR-512-B 2016-11-23T07:36:11+00:00 Giuseppe Lippolis giu.lippolis@gmail.com 2016-11-13T22:36:00+00:00 ec1de9b1a6cd957bb2cb68f7eda294ab73bf9102 The Dlink DWR-512-B modem is a ralink 5350 processor based embedding a 3G mini-pcie router. The oem JBOOT bootloader has to be replaced by a RT5350 SDK U-Boot such as https://github.com/stevenylai/ralink_sdk - U-Boot configured for the RT5350 256MiB SDR. Main reason to change the bootloader is the encrypted header used to store the kernel image. In this way an image can only be generated using the propietary binboy tool (included in the GPL distribution from Dlink). The binboy tool doesn't allow to modify the kernel/rootfs partition scheme. This is considered a big constraint (limited kernel size and inefficient usage of flash space). For interested people I pubblished the details of my investigation about the encrypted firmware header here: http://lists.infradead.org/pipermail/lede-dev/2016-October/003435.html Signed-off-by: Giuseppe Lippolis <giu.lippolis@gmail.com> 
The Dlink DWR-512-B modem is a ralink 5350 processor based embedding
a 3G mini-pcie router.

The oem JBOOT bootloader has to be replaced by a RT5350 SDK
U-Boot such as https://github.com/stevenylai/ralink_sdk - U-Boot
configured for the RT5350 256MiB SDR.

Main reason to change the bootloader is the encrypted header used to
store the kernel image. In this way an image can only be generated
using the propietary binboy tool (included in the GPL distribution
from Dlink). The binboy tool doesn't allow to modify the kernel/rootfs
partition scheme. This is considered a big constraint (limited kernel
size and inefficient usage of flash space).

For interested people I pubblished the details of my investigation
about the encrypted firmware header here:
http://lists.infradead.org/pipermail/lede-dev/2016-October/003435.html

Signed-off-by: Giuseppe Lippolis <giu.lippolis@gmail.com>