CPU: 2x1.8GHz ARM, RAM: 512MiB
Storage: 4MiB serial Flash, 3.9GiB MMC
NIC: 2x1GBit/s, Switch with 5 external and 2 internal ports
WiFi: Dualband, ath10k 2.4GHz, 5GHz MU-MIMO
For installation copy xx-mmcblk0p4-kernel.bin and xx-mmcblk0p5-rootfs-full.bin
to device. Then run:
cat xx-mmcblk0p4-kernel.
Signed-off-by: André Valentin
---
package/boot/uboot-envtools/files/ipq | 3 +++
1 file changed, 3 insertions(+)
diff --git a/package/boot/uboot-envtools/files/ipq
b/package/boot/uboot-envtools/files/ipq
index 8cf0ddb..369f90f 100755
--- a/package/boot/uboot-envtools/files/ipq
+++ b/package/boo
Add new way of flashing to mmc devices based on rootfs split with loop devices.
Signed-off-by: André Valentin
---
.../ipq806x/base-files/lib/upgrade/platform.sh | 12 +++
.../linux/ipq806x/base-files/lib/upgrade/zyxel.sh | 87 ++
2 files changed, 99 insertions(+)
create
Signed-off-by: André Valentin
---
.../patches-4.4/477-mtd-add-spi-nor-add-mx25u3235f.patch | 10 ++
1 file changed, 10 insertions(+)
create mode 100644
target/linux/generic/patches-4.4/477-mtd-add-spi-nor-add-mx25u3235f.patch
diff --git
a/target/linux/generic/patches-4.4/477-mtd
Support for NBG6817 comes with several challenges:
-enable mmc support on platform
-use fstools rootfs split on block devices ( creates a loop dev with offset )
-extend sysupgrade support to format the loop fs and save config
Changes to v3:
-build sysupgrade images padded to overlay block size
-r
mkfs.ext4 und losetup are needed for sysupgrade support on mmc devices
with automatic rootfs split (loopback device usage).
Signed-off-by: André Valentin
---
package/base-files/files/lib/upgrade/common.sh | 2 ++
1 file changed, 2 insertions(+)
diff --git a/package/base-files/files/lib/upgrade/
Hi,
after some recent changes in the fstools repo this patch applies but
causes a compile error. could you please rebase/test/send the patch
there were also a lot of whitespace errors. please use tabs to indent
your c code
John
On 21/10/2016 14:54, Alberto Bursi wrote:
> added the code t
> It seems I'm experiencing the same crazy problem. Local builds work
> for me (as explained in commit message), but image from buildbot
> doesn't boot. This is some totally crazy thing :|
I opt for staying at 4.4 and not reverting, since the issue already occured
on kernel 4.1 for the WRT54GL (an
On 24 October 2016 at 18:43, wrote:
>> I started working on this today, I reproduce see the issue during a
>> lot of tests until it magically disappeared. Then LEDE started booting
>> on my unit with kernel 4.4.
>
> Oh - that rings a bell.
> May I point you to a discussion we had earlier this yea
From: Rafał Miłecki
For mips74k subtarget we don't have ssb compiled into to the kernel,
so allow using it as package. This can be useful for MIPS74k SoCs with
PCIe cards using ssb (like BCM4322).
Signed-off-by: Rafał Miłecki
---
I'm thinking about switching Linksys WRT610N v2 and Linksys E3000
Hi all,
Sorry for my last couple of messages, I'm re-implementing my delay
mechanism so that I don't mess things up again; I do want to help both
OpenWrt and LEDE, not create another bad situation; maybe in a week or
few the things I'm dealing with will be sorted enough to remove that.
At this po
From: Rafał Miłecki
Signed-off-by: Rafał Miłecki
---
target/linux/brcm47xx/image/Makefile | 99 ++--
1 file changed, 95 insertions(+), 4 deletions(-)
diff --git a/target/linux/brcm47xx/image/Makefile
b/target/linux/brcm47xx/image/Makefile
index 8cc336a..5d8e6ff
These boards do not have a switch, so they should have never been added
to this file in the first place.
Signed-off-by: Chris Blake
---
.../ar71xx/base-files/etc/uci-defaults/03_network-switchX-migration | 2 --
1 file changed, 2 deletions(-)
diff --git
a/target/linux/ar71xx/base-files/etc
On the stock Meraki Firmare for the MR12/MR16, a chunk of SPI space
after u-boot-env is used to store the boards Mac address. Sadly as this
was removed on any device already on OpenWRT/LEDE, moving forward a new,
64k partition named "mac" will be used to store the mac address for the
device (which
This moves the Meraki MR12 and Meraki MR16 to the new generic target.
Tested and verified working on both devices.
Note that kernel/rootfs images are still generated. This is because they
are used for the inital flashing process due to the fun pace at which
UBoot erases/writes to SPI.
Signed-off-
Currently the reset script will try to run jffs2reset on boards that are
running a rw rootfs, such as ext4. This will cause jffs2reset to fail
and the board to never reboot while the LED blinks until a manual
reboot.
This commit does two different things:
1. Disables reset on boards that do not ha
On 24.10.2016 19:26, Val Kulkov wrote:
> Hi Jo,
>
Part of the problem, I
think, is the lack of clear and consistent (and visible) governance and
communication makes the project unappealing for companies to be
interested in paying developers to work on either. It's not enou
Hi Jo,
>>> Part of the problem, I
>>> think, is the lack of clear and consistent (and visible) governance and
>>> communication makes the project unappealing for companies to be
>>> interested in paying developers to work on either. It's not enough to
>>> have code and commits, there needs to
I forgot to mention the builtin sdcard reader in the original post.
On Saturday, October 22, 2016 6:10:52 PM CEST Christian Lamparter wrote:
> Hello,
>
> On Saturday, October 22, 2016 11:22:35 AM CEST Rafał Miłecki wrote:
> > From: Rafał Miłecki
> >
> > The old usbdev trigger never supported as
Hi yanosz,
Alberto kindly pointed out that your inquiry didn't receive any response
so far, so please excuse the lack of communication.
> running a community based wifi network based on OpenWRT I'm thinking
> about using lede. Do you have any suggestions on this?
The general suggestion is always
on 2016-10-24 Felix Fietkau wrote:
> On 2016-10-19 23:31, Charles wrote:
> >
> > Questions:
> >
> > 1. Why does LEDE show four regulatory domain blocks while OpenWrt shows
> >only one?
> This was added in Linux upstream. LEDE uses a newer version of mac80211.
OK. Problem is, iw as a movi
> I started working on this today, I reproduce see the issue during a
> lot of tests until it magically disappeared. Then LEDE started booting
> on my unit with kernel 4.4.
Oh - that rings a bell.
May I point you to a discussion we had earlier this year?
http://lists.infradead.org/pipermail/lede-d
Hi!
Am 24.10.2016 um 10:05 schrieb Felix Fietkau:
>> I think we need to store the blocksize in the sysupgrade/control. Because it
>> could
>> change between 2 firmwares. What dou you think. In this case an fstools
>> patch is
>> not needed.
> You're right. I don't think we have a good place to
On 10/24/2016 03:12 PM, Jo-Philipp Wich wrote:
> we need to
> find some more people compensate the missing developer time.
>
I'd say that you might want to make some kind of public announcement on
the main site about this, stating what kinds of people you need and so on.
Maybe also contact Phor
On 23 October 2016 at 19:49, Rafał Miłecki wrote:
> On 23 October 2016 at 12:15, wrote:
>> As one of LEDE's TODOs is "Bump all kernels to v4.4", I've done
>> some testing on two brcm47xx devices (brcm47xx is still on kernel 4.1).
>>
>> The devices I tested on + bootlog:
>> Linksys WRT54GL - http
From: Paul Wassi
Minor fix in the usage message on the explanation of the -p option.
Signed-off-by: Paul Wassi
---
system/mtd/src/mtd.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/system/mtd/src/mtd.c b/package/system/mtd/src/mtd.c
--- a/package/system/mtd/sr
From: Paul Wassi
Remove redundant code: merge boards/cases that share
the same network configuration.
Also fix the alphabetical ordering of the cases.
Signed-off-by: Paul Wassi
---
linux/kirkwood/base-files/etc/board.d/02_network | 15 -
1 file changed, 5 insertions(+), 10 deleti
On 21/10/2016 17:34, Stijn Tintel wrote:
> This patch series adds support for D-Link DAP-2695 rev. A1.
>
> Both the factory and the sysupgrade can be used to flash the device from
> the bootloader. When flashing via the web interface of the stock
> firmware, only the factory image can be used.
>
Hi Alberto,
> I think it's mostly because of the usual reasons in opensource projects.
> Core developers are overloaded, and in what little time they have they
> prefer to code (understandable, but same self-defying issues in OpenWRT).
IMHO this summarizes the current situation quite nicely and
On 21/10/2016 13:54, Chris Blake wrote:
> On the stock Meraki Firmare for the MR12/MR16, a chunk of SPI space
> after u-boot-env is used to store the boards Mac address. Sadly as this
> was removed on any device already on OpenWRT/LEDE, moving forward a new,
> 64k partition named "mac" will be us
On 24/10/2016 08:41, p.wa...@gmx.at wrote:
> From: Paul Wassi
>
> Minor fix in the usage message on the explanation of the -p option.
>
> Signed-off-by: Paul Wassi
this one also fails to apply
John
> ---
> system/mtd/src/mtd.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletio
On 23/10/2016 12:42, p.wa...@gmx.at wrote:
> From: Paul Wassi
>
> Remove redundant code: merge boards/cases that share
> the same network configuration.
>
> Signed-off-by: Paul Wassi
patch does not apply to current HEAD. what tree did you base this on ?
John
> ---
> linux/kirkwood
Hi Daniel,
> Several months after the split it looks like things have pretty much
> ended up where they were before the split. It's starting to look
> like the talk of encouraging new blood, and being more open and
> transparent was more talk than real intention.
I am sorry to hear that this
On 20 October 2016 at 08:02, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> If we want to use some of new features like per device rootfs we will
> need this to specify them there.
>
> Signed-off-by: Rafał Miłecki
Pushed with spaces instead of tabs to match other targets. Thanks Felix.
___
On 2016-10-19 23:31, Charles wrote:
> Hello,
>
> on a TP-Link WDR3600 v1 (dual-band wifi, ath9k, wireless settings are
> attached below, most notably wireless.radioX.country=DE), the output
> of command 'iw reg get' is
>
> with OpenWrt 15.05.1:
>
> country DE: DFS-ETSI
> (2400 - 2483 @ 40)
On 2016-10-24 09:51, André Valentin wrote:
> Hi!
>
> Am 23.10.2016 um 16:44 schrieb Felix Fietkau:
>> On 2016-10-23 16:25, André Valentin wrote:
>>> Add new way of flashing to mmc devices based on rootfs split with loop
>>> devices.
>>>
>>> Signed-off-by: André Valentin
>>> ---
>>> .../ipq806x/
Hi!
Am 23.10.2016 um 16:44 schrieb Felix Fietkau:
> On 2016-10-23 16:25, André Valentin wrote:
>> Add new way of flashing to mmc devices based on rootfs split with loop
>> devices.
>>
>> Signed-off-by: André Valentin
>> ---
>> .../ipq806x/base-files/lib/upgrade/platform.sh | 12 +++
>> .../
Hi!
Am 23.10.2016 um 16:38 schrieb Felix Fietkau:
> On 2016-10-23 16:25, André Valentin wrote:
>> CPU: 2x1.8GHz ARM, RAM: 512MiB
>> Storage: 4MiB serial Flash, 3.9GiB MMC
>> NIC: 2x1GBit/s, Switch with 5 external and 2 internal ports
>> WiFi: Dualband, ath10k 2.4GHz, 5GHz MU-MIMO
>>
>> For install
38 matches
Mail list logo
