Hi,
I created a pull request on GitHub[0] with a reworked and extended README.
Essentially it uses Markdown instead of plain text and embed the new
logo and handy links to documentation and community resources.
Adrian requested to announce the idea on the lists as it's basically the
On Wed, Jul 22, 2020 at 03:58:34PM +0200, m...@adrianschmutzler.de wrote:
> > Thanks for the scrutiny! I do have some questions here: is the
> > VENDOR/MODEL supposed to match closer to a marketing-friendly/user-
> > friendly name, or a developer/low-level name?
>
> I typically prefer something
On 24.07.20 04:29, Petr Štetiar wrote:
As there is now WolfSSL included by default due to SAE/WPA3 we can
finally switch to TLS/SSL in other parts as well.
Signed-off-by: Petr Štetiar
---
README | 2 +-
include/target.mk | 6 +-
include/version.mk | 2 +-
3 files
On 25.07.20 11:21, m...@adrianschmutzler.de wrote:
-Original Message-
From: Paul Spooren [mailto:m...@aparcar.org]
Sent: Samstag, 25. Juli 2020 23:19
To: Adrian Schmutzler ; openwrt-
de...@lists.openwrt.org
Subject: Re: [PATCH 4/4] lantiq: disable default build for devices with 4M
> -Original Message-
> From: Paul Spooren [mailto:m...@aparcar.org]
> Sent: Samstag, 25. Juli 2020 23:19
> To: Adrian Schmutzler ; openwrt-
> de...@lists.openwrt.org
> Subject: Re: [PATCH 4/4] lantiq: disable default build for devices with 4M
> flash
>
> On 25.07.20 08:29, Adrian
On 25.07.20 08:29, Adrian Schmutzler wrote:
It has been decided that the 19.07 release will be last one to include
4/32 devices.
This disables default build for all devices with 4M flash on lantiq.
Note that this will affect _all_ devices for amazonse ("ase") and
xway_legacy subtarget.
Isn't it
The Ed25519 key pairs are much shorter than RSA pairs and are supported
by default in OpenSSH. Looking at websites explaining how to create new
SSH keys, many suggest using Ed25519 rather than RSA, however consider
the former as not yet widely established. OpenWrt likely has a positive
influence
It has been decided that the 19.07 release will be last one to include
4/32 devices.
This disables default build for all devices with 4M flash on lantiq.
Note that this will affect _all_ devices for amazonse ("ase") and
xway_legacy subtarget.
Signed-off-by: Adrian Schmutzler
---
As this will
It has been decided that the 19.07 release will be last one to include
4/32 devices.
This disables default build for the remaining devices with 4M flash
on ath79. Note that this will leave exactly one enabled device for
ath79/tiny subtarget, PQI Air-Pen, which was moved there due to
kernel size
Netgear currently has a special definition for tiny devices, which
is only used by two devices. Despite, it sets ups the IMAGE/default
definition individually for all devices, although there is actually
only one exception.
This merges the common parts into a single netgear_generic definition
(in
This fixes a few cosmetic issues with partition offset and size
that are inconsistent probably due to copy/pasting.
Signed-off-by: Adrian Schmutzler
---
.../arch/mips/boot/dts/lantiq/amazonse_netgear_dgn1000b.dts | 4 ++--
.../mips/boot/dts/lantiq/danube_arcadyan_arv4518pwr01.dtsi| 2 +-
This disables the remaining 4M flash devices not yet taken care of.
bcm63xx and ramips have already been covered in earlier patches.
I didn't do anything about bcm47xx and bcm53xx, as I'm not familiar
enough with these target. Somebody else should take care there.
Adrian Schmutzler (4):
Hi Todor,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Todor Colov
> Sent: Samstag, 25. Juli 2020 18:30
> To: openwrt-devel@lists.openwrt.org
> Cc: Todor Colov
> Subject: [PATCH 1/1] tools: add firmware utils for
Needed for openwrt-factory flashing over the stock WEB interface for Linksys
E8350-v1(and other linksys devices) The tool source files for "addfwhdr" are
placed in a separate sub-directory src/linksys - following naming convention
for Manufacturer.
Signed-off-by: Todor Colov
---
tools: add firmware utils for linksys-addfwhdr generation. Needed for
openwrt-factory flashing over the stock WEB interface for Linksys E8350-v1(and
other linksys devices) The tool source files for "addfwhdr" are placed in a
separate sub-directory src/linksys - following naming convention for
Signed-off-by: Todor Colov
---
package/base-files/files/lib/upgrade/nand.sh | 1 +
1 file changed, 1 insertion(+)
diff --git a/package/base-files/files/lib/upgrade/nand.sh
b/package/base-files/files/lib/upgrade/nand.sh
index e7d7bf8d13..923c01a72d 100644
---
Required for sysupgrade with KERNEL_IN_UBI ubinized volumes
Todor Colov (1):
base-files: fix nand.sh to remove metadata before ubiformat command
package/base-files/files/lib/upgrade/nand.sh | 1 +
1 file changed, 1 insertion(+)
--
2.27.0
___
Signed-off-by: Todor Colov
---
tools/firmware-utils/Makefile | 4 +-
tools/firmware-utils/src/linksys/addfwhdr.c | 195
tools/firmware-utils/src/linksys/bcmdefs.h| 318 +
.../firmware-utils/src/linksys/code_pattern.h | 396
tools: add firmware utils for linksys-addfwhdr generation. Needed for
openwrt-factory flashing over the stock WEB interface for Linksys E8350-v1(and
other linksys devices) The tool source files for "addfwhdr" are placed in a
separate sub-directory src/linksys - following naming convention for
Signed-off-by: Todor Colov
---
.../ipq806x/base-files/etc/board.d/01_leds| 3 +
.../ipq806x/base-files/etc/board.d/02_network | 1 +
.../base-files/lib/upgrade/platform.sh| 3 +-
.../arm/boot/dts/qcom-ipq8064-e8350-v1.dts| 246 ++
Linksys E8350 is AC2350 (802.11ac Wave-2) router
Device specifications:
ArchitectureARM (armv7l cortex-a15+neon vfpv4)
Vendor Linksys
Bootloader U-Boot
System-On-Chip Qualcomm IPQ8064 @ 1.4 GHz
CPU/Speed 2 x 1.4 GHz
Flash-Chips SPI MX25U3235F + NAND MT29F1G08ABBDAH4
Flash
> Understandably so. But like you said, they already have limited functionality
> at this point: wpad-mini versus wpad-basic. At the same time, a lot of those
> devices are EOL with 19.07, as you pointed out. So it would make more sense
> to just keep them on wpad-mini - and maybe, to make the end
Refresh patches.
Remove upstreamed patches:
bcm63xx/patches-5.4/022-v5.8-mtd-rawnand-brcmnand-correctly-verify-erased-pages.patch
bcm63xx/patches-5.4/024-v5.8-mtd-rawnand-brcmnand-fix-CS0-layout.patch
Drop the cake hack as upstream have backported the changes themselves,
but in a slightly
Mbed TLS 2.16.7 is a maintenance release of the Mbed TLS 2.16 branch,
and provides bug fixes and minor enhancements. This release includes
fixes for security issues and the most severe one is described in more
detail in a security advisory:
Hi,
Op zaterdag 25 juli 2020 om 11u28 schreef Petr Štetiar :
Stijn Segers [2020-07-25 10:24:42]:
Hi,
I read Adrian's reply as 'we'll keep ath79/tiny out of the wpad SSL
push?'
but I might be mistaken of course.
the idea of this patch series is to have the _same_ baseline in _all_
On Sat, Jul 25, 2020 at 10:24:42AM +0200, Stijn Segers wrote:
> ...
> P.S. Is there a way to use mbedtTLS with wpad? That would be neat since one
> could have
> LuCI SSL and wpad lean on the same crypto library. I am now building images
> with mbedTLS
> for LuCI and wolfssl for wpad; it's still
> On Jul 25, 2020, at 1:36 AM, Stijn Segers wrote:
>
> Hi Petr,
>
> Op zaterdag 25 juli 2020 om 10u08 schreef Petr Štetiar :
>> m...@adrianschmutzler.de [2020-07-24 17:36:08]:
>> Hi,
>>> I would prefer to not touch ar71xx here, as this is essentially only used
>>> for backporting, and
Stijn Segers [2020-07-25 10:24:42]:
Hi,
> I read Adrian's reply as 'we'll keep ath79/tiny out of the wpad SSL push?'
> but I might be mistaken of course.
the idea of this patch series is to have the _same_ baseline in _all_ images,
so HTTPS and WPA3-Personal by default. It wouldn't make much
On Sat, Jul 25, 2020 at 10:44:46AM +0200, Petr Štetiar wrote:
> Daniel Golle [2020-07-24 15:51:27]:
>
> Hi,
>
> > On Fri, Jul 24, 2020 at 04:29:38PM +0200, Petr Štetiar wrote:
> > > Add package which provides wpad with WPA-PSK, SAE (WPA3-Personal),
> > > 802.11r and 802.11w support.
> >
> > I
Daniel Golle [2020-07-24 15:51:27]:
Hi,
> On Fri, Jul 24, 2020 at 04:29:38PM +0200, Petr Štetiar wrote:
> > Add package which provides wpad with WPA-PSK, SAE (WPA3-Personal),
> > 802.11r and 802.11w support.
>
> I think this should be merged with wpad-mesh. It's almost the same, but
> only
Hi Petr,
Op zaterdag 25 juli 2020 om 10u08 schreef Petr Štetiar :
m...@adrianschmutzler.de [2020-07-24
17:36:08]:
Hi,
I would prefer to not touch ar71xx here, as this is essentially
only used
for backporting, and changing stuff would only make these backports
more
complicated, while
From: Rafał Miłecki
Both: uh_ubus_send_request() and uh_ubus_send_list() don't use it.
Signed-off-by: Rafał Miłecki
---
ubus.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/ubus.c b/ubus.c
index 97cc1e2..51c58b5 100644
--- a/ubus.c
+++ b/ubus.c
@@ -288,7 +288,7 @@
From: Rafał Miłecki
According to the JSON-RPC 2.0 specification "params" value can be either
an Array or Object. This change makes parse_json_rpc() accept both.
Type validation should be handled by a function that actually reads
"params" depending on expected format. This doesn't change
m...@adrianschmutzler.de [2020-07-24 17:36:08]:
Hi,
> I would prefer to not touch ar71xx here, as this is essentially only used
> for backporting, and changing stuff would only make these backports more
> complicated, while not really providing a benefit. (I'm not sure whether it
> can be still
34 matches
Mail list logo
