This could be used on Netgear R6250 once we get NAND working correctly.
Signed-off-by: Rafał Miłecki
---
target/linux/bcm53xx/image/Makefile| 4
target/linux/bcm53xx/image/ubinize.cfg | 24
2 files changed, 28 insertions(+)
create mode 100644 target/linux/bcm5
I reflashed a whole new binary and it worked.
发件人: Yousong Zhou [mailto:yszhou4t...@gmail.com]
发送时间: 2014年9月22日 22:36
收件人: swigger
抄送: Weijie Gao; OpenWrt Development List; gch981...@gmail.com;
blo...@openwrt.org
主题: Re: 答复: [PATCH] ar71xx: qihoo-c301: reset imageNtrynum after each
successfu
hi, swigger
On Sep 22, 2014 10:04 PM, "swigger" wrote:
>
> It does NOT run on my router.
>
> root@OpenWrt:~# cat /etc/config/ubootenv
> config ubootenv
> option dev '/dev/mtd9'
> option offset '0x0'
> option envsize '0x1'
> option secsize '0x1'
> root@OpenWrt:~# fw_printenv
> Cannot p
It does NOT run on my router.
root@OpenWrt:~# cat /etc/config/ubootenv
config ubootenv
option dev '/dev/mtd9'
option offset '0x0'
option envsize '0x1'
option secsize '0x1'
root@OpenWrt:~# fw_printenv
Cannot parse config file: No such file or directory
What's wrong?
-邮件原件-
still wandering around the openwrt code base and, every so often, i
come across the explicit use of "FORCE" prerequisites, like this in
target/sdk/files/Makefile:
clean: FORCE
rm -rf $(BUILD_DIR) $(BIN_DIR)
dirclean: clean
rm -rf $(TMP_DIR)
# check prerequisites before startin
From de6e557c769c29be97a56e909a1b31a0c67625d5 Mon Sep 17 00:00:00 2001
From: Geoffrey McRae
Date: Mon, 22 Sep 2014 22:48:01 +1000
Subject: [PATCH 2/2] Add target TP-Link TD-W8980
Signed-off-by: Geoffrey McRae
---
.../lantiq/base-files/etc/uci-defaults/02_network |2 +-
target/linux/lantiq
From 349a53426c78da1d02ecb8b8ade6b8c4de4057c2 Mon Sep 17 00:00:00 2001
From: Geoffrey McRae
Date: Mon, 22 Sep 2014 21:49:32 +1000
Subject: [PATCH 1/2] Lantiq: Fix the ath9k pci eeprom init code to use
the
BAR0 base address instead of a fixed address
Fixes support for AR9287 on TP-Link TD-W898
On 22 September 2014 16:42, swigger wrote:
> NO, not seama. Seama is only a container, not an encrypted format.
>
> The original OEM firmware is encrypted by AES ECB mode and have a
> RSA-1024 signuature.
> The aes key is base64_decode("lbhySwdj31NGnuebNn9FmQ==");
>
> The oem's upgrade firmware we
Qihoo C301 has 2 flash chips of which one is used as primary and the
other is used as backup. OEM U-Boot will try to boot an activeregion N
with imageNstatus=0 and imageNtrynum <= imagemaxtry. If such a region
is found, bootloader will try to increment imageNtrynum and boot it.
This patch tries
Flashing back to OEM through OpenWrt's sysupgrade process is also OK,
but you should cut-off extra seama header from the decrypted OEM
firmware.
then just run:
mtd -r write your-decrypted-oem-firmware firmware
On Mon, Sep 22, 2014 at 4:10 PM, Yousong Zhou wrote:
> Just got the device... Wow
>
>
NO, not seama. Seama is only a container, not an encrypted format.
The original OEM firmware is encrypted by AES ECB mode and have a
RSA-1024 signuature.
The aes key is base64_decode("lbhySwdj31NGnuebNn9FmQ==");
The oem's upgrade firmware web page ONLY allows encrypted firmware
while the u-boot a
Just got the device... Wow
On 22 September 2014 15:47, swigger wrote:
> Well, it's a good idea.
> But I don't know how to create a wiki page.
>
> QIhoo 360 C301 (http://luyou.360.cn/parameter.html, Simplified Chinese
> ONLY), has two 16M flash.
> The first flash is full functional, and the second
El 22/09/14 01:51, Claudio Leite ha escrit:
> I'm not sure the MediaTek driver still uses the old format from the
> Ralink driver. If so, this might be helpful:
>
> https://github.com/WRTnode/openwrt-packages/blob/master/ralink/ralink-wifi/files/lib/wifi/ralink.sh
>
> I think that was for a proj
Well, it's a good idea.
But I don't know how to create a wiki page.
QIhoo 360 C301 (http://luyou.360.cn/parameter.html, Simplified Chinese
ONLY), has two 16M flash.
The first flash is full functional, and the second has just a backup firmware.
U-boot will boot into the second flash when it believe
14 matches
Mail list logo
