When append-kernel is used and a KERNEL_SIZE is defined, we need to make
sure that our kernel fits within it's partition size.
Signed-off-by: Chris Blake
---
target/linux/ar71xx/image/generic.mk | 4 ++--
target/linux/ar71xx/image/ubnt.mk| 2 +-
2 files changed, 3 insertions(+), 3 deletions(
When append-kernel is used and a KERNEL_SIZE is defined, we need to make
sure that our kernel fits within it's partition size.
Signed-off-by: Chris Blake
---
target/linux/kirkwood/image/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/target/linux/kirkwood/image/M
Adding a default KERNEL_SIZE will ensure that we have an option for
check-size when used on any future targets.
Signed-off-by: Chris Blake
---
target/linux/apm821xx/image/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/target/linux/apm821xx/image/Makefile
b/target/linux/apm821xx/im
When append-kernel is used and a KERNEL_SIZE is defined, we need to make
sure that our kernel fits within it's partition size.
Signed-off-by: Chris Blake
---
target/linux/apm821xx/image/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/target/linux/apm821xx/image/M
When append-kernel is used and a KERNEL_SIZE is defined, we need to make
sure that our kernel fits within it's partition size.
Signed-off-by: Chris Blake
---
target/linux/mvebu/image/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/mvebu/image/Makefile
b
When append-kernel is used and a KERNEL_SIZE is defined, we need to make
sure that our kernel fits within it's partition size.
Signed-off-by: Chris Blake
---
target/linux/ipq806x/image/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/ipq806x/image/Makefil
These patches are the outcome of discussions had at
http://lists.infradead.org/pipermail/lede-dev/2016-September/002693.html,
where append-kernel was failing to properly offset kernels due to a typo. Out
of this, it was also
found that kernels are not checked for size, which can cause issues down
On 12 September 2016 at 00:12, Stijn Tintel wrote:
> Signed-off-by: Stijn Tintel
> ---
> package/boot/uboot-envtools/files/ar71xx | 1 +
> target/linux/ar71xx/base-files/etc/board.d/01_leds | 5 +
> .../linux/ar71xx/base-files/etc/board.d/02_network | 5 +
> .../etc/hotplug.d/fir
On 11 September 2016 at 18:12, Stijn Tintel wrote:
> Based on fixseama.
And that way you could inherit some issues from seama support. So it's
not just your fault that much ;)
> @@ -53,6 +53,7 @@
>
> #define TRX_MAGIC 0x48445230 /* "HDR0" */
> #define SEAMA_MAGIC
From: Rafał Miłecki
Using few packages will allow saving some space by decreasing rootfs
size. Dropping 43602a1 firmware saves 316 580 B. Dropping 4366b1 saves
468 188 B.
Moreover there are more firmware files that may require packaging and
even more to come later (e.g. 4366c0).
This can especi
11.09.2016 20:24, Chris Blake:
@Mathias,
Just to make sure, is check-size (IMAGE_SIZE) also affected by
this bug as well? If so, let me know and I can rebase this patch again
later tonight to fix that as well.
- Chris Blake
I've tested the build of a few images and (IMAGE_SIZE) seams
@Mathias,
Just to make sure, is check-size (IMAGE_SIZE) also affected by
this bug as well? If so, let me know and I can rebase this patch again
later tonight to fix that as well.
- Chris Blake
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
Per http://lists.infradead.org/pipermail/lede-
dev/2016-September/002693.html, this patch adds check-size
$$(KERNEL_SIZE) when append-kernel is used to ensure kernels are not
over their max KERNEL_SIZE, as this is not checked by append-kernel.
Signed-off-by: Chris Blake
---
target/linux/ar71xx/i
11.09.2016 17:40, Chris Blake:
It appears that (KERNEL_SIZE) was not passing to append-kernel,
causing sysupgrade images to brick units due to the invalid rootfs
offset. This is fixed by removing the 2 extra $$'s in front of the
variables. Additionally, check-size was added to ensure that we
Signed-off-by: Stijn Tintel
---
package/boot/uboot-envtools/files/ar71xx | 1 +
target/linux/ar71xx/base-files/etc/board.d/01_leds | 5 +
.../linux/ar71xx/base-files/etc/board.d/02_network | 5 +
.../etc/hotplug.d/firmware/11-ath10k-caldata | 4 +
.../base-files/etc/uci-de
Based on mkwrgimg.c.
Signed-off-by: Stijn Tintel
---
tools/firmware-utils/Makefile| 1 +
tools/firmware-utils/src/mkwrggimg.c | 282 +++
2 files changed, 283 insertions(+)
create mode 100644 tools/firmware-utils/src/mkwrggimg.c
diff --git a/tools/firmw
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.
With the stock firmware, this device is only usable a
Support splitting WRGG images, found in some D-Link devices (e.g.
DAP-2695).
Signed-off-by: Stijn Tintel
---
target/linux/ar71xx/config-4.4 | 1 +
target/linux/generic/config-3.18 | 1 +
target/linux/generic/config-4.1| 1 +
target/
Signed-off-by: Stijn Tintel
---
.../base-files/etc/uci-defaults/09_fix-checksum | 19 +++
.../base-files/etc/uci-defaults/09_fix-trx-header | 19 ---
2 files changed, 19 insertions(+), 19 deletions(-)
create mode 100644
target/linux/ar71xx/base-files/et
Based on fixseama.
Signed-off-by: Stijn Tintel
---
package/system/mtd/src/Makefile | 3 +-
package/system/mtd/src/mtd.c| 28 +-
package/system/mtd/src/mtd.h| 1 +
package/system/mtd/src/wrgg.c | 189
package/system/mtd/src/wrgg.h | 2
11.09.2016 17:43, Chris Blake:
Additionally, it appears that other devices like the ZyXEL NBG6616 may
be affected by this.
I'm working on the same at the moment. And till now the ZyXEL NBG6616
and the Ubiquiti UAP Pro are affected by the same error as well. I'm
compiling a few more targets to
On Sun, Sep 11, 2016 at 10:40 AM, Chris Blake wrote:
> It appears that (KERNEL_SIZE) was not passing to append-kernel,
> causing sysupgrade images to brick units due to the invalid rootfs
> offset. This is fixed by removing the 2 extra $$'s in front of the
> variables. Additionally, check-size
It appears that (KERNEL_SIZE) was not passing to append-kernel,
causing sysupgrade images to brick units due to the invalid rootfs
offset. This is fixed by removing the 2 extra $$'s in front of the
variables. Additionally, check-size was added to ensure that we don't
have a kernel larger than o
Hi,
I have some new Intel DSL PHY drivers and a new DSL Firmware in my
staging tree. I am using it for some days now and also did a little
testing in the lab. Please test it and report any regression you see
with it, if it is working good I will commit it to the main development
branch in the next
11.09.2016 06:07, J Mo:
On 09/10/2016 06:36 PM, J Mo wrote:
diff --git
a/target/linux/ipq806x/base-files/lib/preinit/06_set_iface_mac
b/target/linux/ipq806x/base-files/lib/preinit/06_set_iface_mac
new file mode 100644
index 000..b4ed225
--- /dev/null
+++ b/target/linux/ipq806x/base-files/l
11.09.2016 03:36, J Mo:
On 09/10/2016 10:27 AM, Mathias Kresin wrote:
10.09.2016 03:35, J Mo:
--- a/include/image-commands.mk
+++ b/include/image-commands.mk
@@ -168,3 +168,19 @@ define Build/sysupgrade-tar
--rootfs $(call
param_get_default,rootfs,$(1),$(IMAGE_ROOTFS)) \
$@
10.09.2016 03:35, J Mo:
diff --git a/target/linux/ipq806x/patches-4.4/800-devicetree.patch
b/target/linux/ipq806x/patches-4.4/800-devicetree.patch
index 85f2534..ae174fd 100644
--- a/target/linux/ipq806x/patches-4.4/800-devicetree.patch
+++ b/target/linux/ipq806x/patches-4.4/800-devicetree.patch
27 matches
Mail list logo
