On Wed, Jun 10, 2020 at 4:05 AM Rui Salvaterra wrote:
>
> Hi, Jason,
>
> On Wed, 10 Jun 2020 at 10:31, Rui Salvaterra wrote:
> >
> > Good question. :) You're testing in QEMU (which I personally never
> > used), right? I don't know how familiar you are with OpenWrt, but I
> > can surely send you
Hello Community,
I have recently discovered that there is a conversion problem with the
ubus lua binding.
I think it is due to the following commit [1] from the ubus project.
Can anyone confirm this?
I have a lua program that loads the json object from ubus and extracts a
value.
On a 32 bit
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
The script was previously
Hi Rui,
I'm unable to reproduce this:
$ git clone https://git.zx2c4.com/wireguard-linux-compat
$ ARCH=arm make -C wireguard-linux-compat/src test-qemu -j$(nproc)
[... big test suite ...]
$ vim wireguard-linux-compat/qemu-build/arm/linux-5.5.14/.config
[... enable CONFIG_THUMB2_KERNEL=y ...]
$
Hi, Jason,
I'm trying to build OpenWrt master with Thumb-2 instructions for my
Turris Omnia (both kernel and userspace) with GCC 9.3.0 and Binutils
2.34 from the toolchain. [1] Everything seems to work apart from
WireGuard, for some reason the module won't load, throwing the
relocation error in
Hi,
Hi Paul,
I gave this today a test on my spare computer, but it still complained about
the missing libncurses.
I tested with snapshot imagebuilder (r13519-8a858363b0) with just calling
"make image"
Any ideas?
It's just a PR and not yet merged. Once merged give it another 24 hours.
Best,
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Fixes: FS#2086
The logic for
Hi, Jason,
Thanks for the quick reply!
On Wed, 10 Jun 2020 at 10:20, Jason A. Donenfeld wrote:
>
> Is there some config combination you can stick into the test harness
> to repro what you're seeing?
Good question. :) You're testing in QEMU (which I personally never
used), right? I don't know
On Wed, Jun 10, 2020 at 6:27 PM Kevin Darbyshire-Bryant
wrote:
>
> IPKG_INSTROOT is only set under image builder and we won't be running
> this script at build time either, so remove the reference before it gets
> cargo-culted into other scripts.
>
> Signed-off-by: Kevin Darbyshire-Bryant
This is required for the D-Link DAP-2695-A1.
Signed-off-by: Stijn Tintel
---
package/system/mtd/src/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/system/mtd/src/Makefile b/package/system/mtd/src/Makefile
index e504a04478..6da31a04a4 100644
---
This is required for the D-Link DAP-2695-A1.
Signed-off-by: Stijn Tintel
---
target/linux/ath79/config-4.19 | 1 +
target/linux/ath79/config-5.4 | 1 +
2 files changed, 2 insertions(+)
diff --git a/target/linux/ath79/config-4.19 b/target/linux/ath79/config-4.19
index cfa0ebd759..81fd017aba
Hardware:
* SoC: Qualcomm Atheros QCA9558
* RAM: 256MB
* Flash: 16MB SPI NOR
* Ethernet: 2x 10/100/1000 (1x 802.3at PoE-PD)
* WiFi 2.4GHz: Qualcomm Atheros QCA9558
* WiFi 5GHz: Qualcomm Ahteros QCA9880-2R4E
* LEDS: 1x 5GHz, 1x 2.4GHz, 1x LAN1(POE), 1x LAN2, 1x POWER
* Buttons: 1x RESET
* UART: 1x
This series adds support for the D-Link DAP-2695-A1 to the ath79 target.
Also available in the ath79_dap-2695-a1 branch of my staging tree at [0].
Successfully tested sysupgrade from ar71xx to ath79.
As discussed on IRC, I prefer to keep the network setup identical to
ar71xx, so this wasn't
Hi,
I am trying to utilize fstools mount_root to enable using UBIFS RW overlay
on top of SquashFS on a non OpenWrt based embedded system.
I have used a shell script as the init process that mounts /proc and then
executes mount_root and after that is done calls /sbin/init so systemd will
then be
Hi, I am a software engineering consultant. I want to contact the hiring
manager or CEO of "Luci.AI Inc.". I can help you with my engineering service. I
am a Sr.Developer with 7 years of experience. I can create a management system,
portal, mobile application or a website for "Luci.AI Inc.".
-
This is required for the D-Link DAP-2695-A1.
Signed-off-by: Stijn Tintel
---
package/system/mtd/src/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/system/mtd/src/Makefile b/package/system/mtd/src/Makefile
index e504a04478..6da31a04a4 100644
---
This series adds support for the D-Link DAP-2695-A1 to the ath79 target.
Also available in the ath79_dap-2695-a1 branch of my staging tree at [0].
Successfully tested sysupgrade from ar71xx to ath79.
As discussed on IRC, I prefer to keep the network setup identical to
ar71xx, so this wasn't
This is required for the D-Link DAP-2695-A1.
Signed-off-by: Stijn Tintel
---
target/linux/ath79/config-4.19 | 1 +
target/linux/ath79/config-5.4 | 1 +
2 files changed, 2 insertions(+)
diff --git a/target/linux/ath79/config-4.19 b/target/linux/ath79/config-4.19
index cfa0ebd759..81fd017aba
Hardware:
* SoC: Qualcomm Atheros QCA9558
* RAM: 256MB
* Flash: 16MB SPI NOR
* Ethernet: 2x 10/100/1000 (1x 802.3at PoE-PD)
* WiFi 2.4GHz: Qualcomm Atheros QCA9558
* WiFi 5GHz: Qualcomm Ahteros QCA9880-2R4E
* LEDS: 1x 5GHz, 1x 2.4GHz, 1x LAN1(POE), 1x LAN2, 1x POWER
* Buttons: 1x RESET
* UART: 1x
Hi,
a few minor comments below.
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Stijn Tintel
> Sent: Mittwoch, 10. Juni 2020 22:15
> To: openwrt-devel@lists.openwrt.org
> Cc: m...@adrianschmutzler.de
> Subject: [OpenWrt-Devel]
IPKG_INSTROOT is only set under image builder and we won't be running
this script at build time either, so remove the reference before it gets
cargo-culted into other scripts.
Signed-off-by: Kevin Darbyshire-Bryant
---
package/network/services/odhcpd/Makefile| 2 +-
Currently I'm unable to boot initramfs image with `console=ttyS0,115200`
kernel commandline as the bootloader mangling resets kernel commandline
if there is no `root=` option provided, efectively clearing whatever I
pass to the kernel, making the `root=` option mandatory.
Signed-off-by: Petr
22 matches
Mail list logo
