02.07.2017 17:17, Rafał Miłecki:
From: Rafał Miłecki
LEDE supports 6 devices using TP-Link firmware format (V2 or V3):
ArcherC20i, ArcherC50, ArcherMR200, TDW8970, TDW8980 and VR200v.
Testing mktplinkfw2 tool with official (vendor generated) firmware files
for all above devices has shown an er
From: Rafał Miłecki
It seems simpler to store all custom (command line set) option values in
a struct identical to the predefined ones. It doesn't require:
1) Having so many global variables
2) Copying data from the predefined boards
Signed-off-by: Rafał Miłecki
---
tools/firmware-utils/src/mk
Le 07/02/17 à 01:49, Yousong Zhou a écrit :
> On 1 July 2017 at 07:34, Florian Fainelli wrote:
>> If we manage to accidentally get a module installed that does not match
>> the system endianess (there is currently nothing preventing that in
>> OpenWrt/LEDE) we will hit a segmentation fault when do
Hello Rafał,
On 02.07.2017 17:17, Rafał Miłecki wrote:
From: Rafał Miłecki
LEDE supports 6 devices using TP-Link firmware format (V2 or V3):
ArcherC20i, ArcherC50, ArcherMR200, TDW8970, TDW8980 and VR200v.
I included (in 24043a0d2e01b9843c0dc529205b3b0bc7ecbbf9) another two
TP-Link devices
From: Rafał Miłecki
LEDE supports 6 devices using TP-Link firmware format (V2 or V3):
ArcherC20i, ArcherC50, ArcherMR200, TDW8970, TDW8980 and VR200v.
Testing mktplinkfw2 tool with official (vendor generated) firmware files
for all above devices has shown an error when comparing calculated and
i
On 07/02/2017 04:27 PM, Jo-Philipp Wich wrote:
> Hi,
>
> I think you're supposed to use "lede-brcm47xx-legacy-standard-squashfs.trx".
>
> ~ Jo
Thanks it works with that image, it was some time ago I flashed an image
to my brcm47xx devices.
But there is some code in the platform sysupgrade code
On 07/02/2017 04:05 PM, Hauke Mehrtens wrote:
> Hi,
>
> I just tried to run sysupgrade on a WRT53GS (brcm47xx) device and it
> failed. I am running LEDE r4504.
>
> Hauke
Hmm, the "Could not get image magic" and "Image check failed." message are
from mtd itself. What exactly does mtd check here?
Hi,
I think you're supposed to use "lede-brcm47xx-legacy-standard-squashfs.trx".
~ Jo
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Hi,
I just tried to run sysupgrade on a WRT53GS (brcm47xx) device and it
failed. I am running LEDE r4504.
Hauke
root@LEDE:/tmp# wget
http://192.168.1.195/hauke-web/lede/targets/brcm47xx/legacy
/lede-brcm47xx-legacy-linksys-wrt54gs-squashfs.bin
Downloading
'http://192.168.1.195/hauke-web/lede/ta
Some days ago I received an invitation from the Bundesamt für Sicherheit
in der Informationstechnik (BSI) (English: Federal Office for
Information Security) to a kickoff meeting regarding the “Technische
Richtlinie Breitband-Router” (English: Technical guideline broadband
router) in Bonn, Germany o
Hi all, me again,
What happened to
option ttylogin '1'
in /etc/config/system ??
If I put it in, my system in inacessible.
[ 29.903337] NET: Registered protocol family 24
[ 30.027492] usbcore: registered new interface driver carl9170
[ 30.036255] usbcore: registered new interface driver
From: Rafał Miłecki
1) Be consistent and use tabs
2) Drop FIXME from boot comments - some images use these fields normally
3) Add V3 specific fields (signatures)
4) Add V3.0.0.3 region field
Signed-off-by: Rafał Miłecki
---
tools/firmware-utils/src/mktplinkfw2.c | 75 ++
On 06/26/2017 05:03 PM, Evgeniy Didin wrote:
> arc-2017.03 is the most recent release toolchain for ARC cores
> and it is based on upstream Binutils 2.28 and GCC 6.3.0
>
> Signed-off-by: Evgeniy Didin
> Cc: Alexey Brodkin
> Cc: John Crispin
> ---
> package/devel/gdb-arc/Makefile
On 06/27/2017 07:47 AM, Alexey Brodkin wrote:
> Hi Hauke,
>
> On Mon, 2017-06-26 at 22:45 +0200, Hauke Mehrtens wrote:
>> On 06/26/2017 05:03 PM, Evgeniy Didin wrote:
>>>
>>> arc-2017.03 is the most recent release toolchain for ARC cores
>>> and it is based on upstream Binutils 2.28 and GCC 6.3.0
On 06/25/2017 05:14 PM, Stefan Tomanek wrote:
> Tested on TP-Link Archer C7
>
> Signed-off-by: Stefan Tomanek
> ---
> utils/triggerhappy/Makefile |9 -
> 1 file changed, 4 insertions(+), 5 deletions(-)
The package feed is maintained here:
https://github.com/openwrt/packages
Please
On 1 July 2017 at 07:34, Florian Fainelli wrote:
> If we manage to accidentally get a module installed that does not match
> the system endianess (there is currently nothing preventing that in
> OpenWrt/LEDE) we will hit a segmentation fault when doing this:
>
> sh = (Elf32_Shdr *) (map + e->e_sho
16 matches
Mail list logo
