Thanks! Blocksize turned out to be the issue -- resolved for the devices
in question.
I'm still interested in finding out where the definition of the
"default" sysupgrade.img
is found in make files of the build system.
Jeff
On 7/1/19 1:47 PM, Hannu Nyman wrote:
The smaller, "failing" image
Hi,
based on the recent commit of "scripts/feeds: add src-include method"
I remembered in my patch I sent some time ago.
As Jo suggested it's now adding a dependency to all .mk files in a feeds
root-folder.
I assume it was just overseen or is there something bad? We use it for
some time for our
The smaller, "failing" image contains in /dev/mtd2:
003eebd0 00 01 59 5a be e7 20 00 00 00 00 00 04 80 00 00 |..YZ.. .|
003eebe0 00 00 dc eb 20 00 00 00 00 00 ff ff ff ff ff ff | ...|
003eebf0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ||
*
004000
The smaller, "failing" image contains in /dev/mtd2:
003eebd0 00 01 59 5a be e7 20 00 00 00 00 00 04 80 00 00 |..YZ.. .|
003eebe0 00 00 dc eb 20 00 00 00 00 00 ff ff ff ff ff ff | ...|
003eebf0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ||
*
004000
I've run across some seemingly "wrong" behavior related to sysupgrade
where if the image is "too small" the contents of /sysupgrade.tgz are
not properly recovered on reboot.
It seems as if the various pieces are functioning as expected, but
that they do not work in concert under certain situation
Removed options that can't be turned off because we're building with
--enable-stunnel, some of which affect hostapd's Config.in.
Adjusted the title of OCSP option, as OCSP itself can't be turned off,
only the stapling part is selectable.
Mark options turned on when wpad support is selected.
Add bui
This edjusts the selection of recently removed wolfssl options which
have always been built into the library even in their abscence.
Also remove the selection of libwolfssl itself, allowing the library to
be built as a module.
Signed-off-by: Eneas U de Queiroz
diff --git a/package/network/servic
This series starts with an update to version 3.15.7, which includes a
security fix, and should be cherry-picked to 19.07. I'm not
cherry-picking it to 18.06 because it changes ABI, and it would cause
package breakage because 18.06 is not ABI version-aware.
I've increased the FP_MAX_BITS parameter
This includes a fix for a medium-level potential cache attack with a
variant of Bleichenbacher’s attack. Patches were refreshed.
Increased FP_MAX_BITS to allow 4096-bit RSA keys.
Fixed poly1305 build option, and some Makefile updates.
Signed-off-by: Eneas U de Queiroz
diff --git a/package/libs/
On 01/07/2019 16:23, Alban wrote:
On Mon, 1 Jul 2019 15:48:47 +0200
John Crispin wrote:
On 21/06/2019 17:38, Alban Bedel wrote:
Since commit 11e8afea (runqueue should cal the complete handler from
more places) the call to the complete() callback has been moved to
runqueue_task_complete().
On Mon, 1 Jul 2019 15:48:47 +0200
John Crispin wrote:
> On 21/06/2019 17:38, Alban Bedel wrote:
> > Since commit 11e8afea (runqueue should cal the complete handler from
> > more places) the call to the complete() callback has been moved to
> > runqueue_task_complete(). However in runqueue_task_k
On 16/06/2019 00:10, Jeff Kletsky wrote:
From: Jeff Kletsky
Wifi can, in certain situations, cause sysupgrade to fail silently
with a 256 return value as all processes can't be killed.
One of these situations is mesh with batman-adv active.
Added `wifi down` just prior to the killall sequence
Hello,
The following patch (submitted by you) has been updated in Patchwork:
* openwrt: [OpenWrt-Devel] libubox: add macros for remaining logging severities
- http://patchwork.ozlabs.org/patch/1117474/
- for: OpenWrt development
was: New
now: Changes Requested
This email is a
Hi,
patch is malformed and fails to apply
John
--2019-07-01 15:54:52-- http://patchwork.ozlabs.org/patch/1117474/mbox/
Resolving patchwork.ozlabs.org (patchwork.ozlabs.org)... 203.11.71.1,
2401:3900:2:1::2
Connecting to patchwork.ozlabs.org
(patchwork.ozlabs.org)|203.11.71.1|:80... connec
On 21/06/2019 17:38, Alban Bedel wrote:
Since commit 11e8afea (runqueue should cal the complete handler from
more places) the call to the complete() callback has been moved to
runqueue_task_complete(). However in runqueue_task_kill()
runqueue_task_complete() is called before the kill() callback
Can someone review this series of patch i sent some times ago?
https://patchwork.ozlabs.org/patch/1116584/
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Preserve optionality of libcap by having configuration script follow the
HAVE_CAP environment variable, used similarly to the HAVE_ELF variable.
Signed-off-by: Alin Nastac
---
package/network/utils/iproute2/Makefile| 18 ++
.../iproute2/patches/150-keep_libcap_opt
17 matches
Mail list logo
