Paul Spooren writes:
> To avoid hashing of folders `fopen()` is called in `r+` mode which fails
> on folders, as their are not writeable. Regular files work as before.
This prevents mkhash from working with read-only files. That's
unexpected, and IMHO worse than the problem you are trying to fi
Submitted upstream. Shouldn't affect existing devices, but enables new
device support.
https://lore.kernel.org/linux-gpio/20200703080646.23233-1-computersforpe...@gmail.com/
Currently queued for-next:
https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git/commit/?h=for-next&id=1
This commit adds support for the Jotale JS76x8 series development boards.
These devices have the following specifications:
- SOC: MT7628AN/NN, MT7688AN, MT7628DAN
- RAM of MT7628AN/NN and MT7688AN: 64/128/256 MB (DDR2)
- RAM of MT7628DAN: 64 MB (DDR2)
- FLASH:8/16/32 MB (SPI NOR)
- Ethernet:3x 10/
If hashing a file fails mkhash shouldn't just silently fail. Now check
after each call of `hash_file()` the return and exit early in case of
errors. The return value which was previously ignored and would always
return 0.
Signed-off-by: Paul Spooren
---
scripts/mkhash.c | 7 +--
1 file chang
mkhash currently returns the hash of an empty input when trying to hash
a folder. This can be missleading in caseswhere e.g. an env variable is
undefined which should contain a filename. `mkhash ./path/to/$FILE`
would exit with code 0 and return a legit looking checksum.
A better behaviour would b
Hi,
On 16.07.20 21:20, Bjørn Mork wrote:
Paul Spooren writes:
To avoid hashing of folders `fopen()` is called in `r+` mode which fails
on folders, as their are not writeable. Regular files work as before.
This prevents mkhash from working with read-only files. That's
unexpected, and IMHO wo
Matt Johnston [2020-07-16 21:24:43]:
Hi,
> I can't reproduce a problem authenticating to a Dropbear 2020.80 server with
> rsa keys. I've tried with either dbclient 2019.78 (using ssh-rsa sha1
> signatures) or dbclient 2020.80 (rsa-sha2-256 signatures). Could you give me
> some steps to reproduce
Brian Norris [2020-07-17 07:23:48]:
Hi,
> Submitted upstream.
nice, thanks.
> Shouldn't affect existing devices, but enables new device support.
I'm just wondering why this patch has to be in the tree now. It would make
more sense to add this as separate commit/patch in the patch series addin
Rosen Penev [2020-07-13 22:43:51]:
Hi,
> GCC 10 defaults to fno-common, which demains unique defenitions.
whats the exact error here? Wouldn't it make sense to move this into packages
feed?
What about upstream, looks like they might find this patch handy.
-- ynezz
___
> On Jul 17, 2020, at 2:50 AM, Petr Štetiar wrote:
>
> Rosen Penev [2020-07-13 22:43:51]:
>
> Hi,
>
>> GCC 10 defaults to fno-common, which demains unique defenitions.
>
> whats the exact error here? Wouldn't it make sense to move this into packages
> feed?
No idea what this package is fo
On 2020-07-14 07:43, Rosen Penev wrote:
> GCC 10 defaults to fno-common, which demains unique defenitions.
>
> Signed-off-by: Rosen Penev
> ---
> package/network/utils/iftop/Makefile | 2 +-
> .../utils/iftop/patches/010-gcc10.patch | 20 +++
> 2 files changed, 21
> On Jul 17, 2020, at 3:06 AM, Felix Fietkau wrote:
>
> On 2020-07-14 07:43, Rosen Penev wrote:
>> GCC 10 defaults to fno-common, which demains unique defenitions.
>>
>> Signed-off-by: Rosen Penev
>> ---
>> package/network/utils/iftop/Makefile | 2 +-
>> .../utils/iftop/patches/010-
Hi,
I've sent a fix using extern declarations upstream, lets see what happens.
~ Jo
signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Petr Štetiar
> Sent: Freitag, 17. Juli 2020 11:50
> To: Rosen Penev
> Cc: openwrt-devel@lists.openwrt.org
> Subject: Re: [PATCH] iftop: fix compilation with GCC 10
>
> Rosen Penev [
On 17.07.20 11:56, Rosen Penev wrote:
On Jul 17, 2020, at 2:50 AM, Petr Štetiar wrote:
Rosen Penev [2020-07-13 22:43:51]:
Hi,
GCC 10 defaults to fno-common, which demains unique defenitions.
whats the exact error here? Wouldn't it make sense to move this into packages
feed?
+1
No id
Rosen Penev writes:
>> On Jul 17, 2020, at 3:06 AM, Felix Fietkau wrote:
>>> +--- a/ui_common.h
>>> b/ui_common.h
>>> +@@ -33,12 +33,12 @@ typedef struct host_pair_line_tag {
>>> +
>>> + extern options_t options;
>>> +
>>> +-sorted_list_type screen_list;
>>> +-host_pair_line totals;
>>> +
This commit add a workaround for non working SGMII link observed on some
QCA956x SoCs. The workaround originates part from the U-Boot source code
from QCA, part from the implementation from TP-Link found in the GPL
tarball for the EAP245v1.
Extends commit 0d416a8d3b990e3b78628f0e7546527709c877f7 f
TP-Link EAP245 v1 is an AC1750 (802.11ac Wave-1) ceiling mount access point.
Device specifications:
* SoC: QCA9563 @ 775MHz
* RAM: 128MiB DDR2
* Flash: 16MiB SPI-NOR
* Wireless 2.4GHz (SoC): b/g/n, 3x3
* Wireless 5Ghz (QCA9880): a/n/ac, 3x3
* Ethernet (AR8033): 1× 1GbE, 803.2at PoE
Flashing instr
TP-Link EAP225 v3 is an AC1350 (802.11ac Wave-2) ceiling mount access
point.
Device specifications:
* SoC: QCA9563 @ 775MHz
* RAM: 128MiB DDR2
* Flash: 16MiB SPI-NOR
* Wireless 2.4GHz (SoC): b/g/n, 3x3
* Wireless 5Ghz (QCA9886): a/n/ac, 2x2 MU-MINO
* Ethernet (AR8033): 1× 1GbE, 803.2at PoE
Flashi
TP-Link has developed a number of access points based on the AP152
reference board. In the EAP-series of 802.11ac access points, this
includes the following devices with one ethernet port:
* EAP225 v1/v2
* EAP225 v3
* EAP225-Outdoor v1
* EAP245 v1
Since the only differences between these devices a
This patch series seeks to add support for the following devices:
* TP-Link EAP245 v1
* TP-Link EAP225 v3
* TP-Link EAP225-Outdoor v1
Currently not included:
* TP-Link EAP225 v1/v2
Note that the patches cannot be applied straight to master, but require
(at least) the first four patches (elf sp
TP-Link EAP225-Outdoor v1 is an AC1200 (802.11ac Wave-2) pole or wall
mount access point.
Device specifications:
* SoC: QCA9563 @ 775MHz
* Memory: 128MiB DDR2
* Flash: 16MiB SPI-NOR
* Wireless 2.4GHz (SoC): b/g/n 2x2
* Wireless 5GHz (QCA9886): a/n/ac 2x2 MU-MIMO
* Ethernet (AR8033): 1× 1GbE, PoE
Allow configuration of rgmii-ge0, mii-ge0, gmii-ge0, mii-ge0-master,
mii-ge0-slave, ge0-sgmii, txen-delay, txd-delay, rxdv-delay and
rxd-delay in device-tree for qca956x SoCs.
Signed-off-by: Julien Dusser
Signed-off-by: Sander Vanheule
---
.../net/ethernet/atheros/ag71xx/ag71xx_gmac.c | 14
This patch adds many registers and values for QCA956x GMAC interface.
QCA956X_PLL_SWITCH_CLOCK_CONTROL_REG, QCA956X_PLL_ETH_XMII_CONTROL_REG
and QCA956X_ETH_CFG_RGMII_EN names are fixed to match original names.
Values are taken from U-Boot 1.1.4 of CAF.
Signed-off-by: Julien Dusser
Signed-off-b
Hi Petr,
I still can't reproduce this with OpenSSH_7.6p1 Ubuntu-4ubuntu0.3.
Are you using a rsa key on disk, or using a SSH agent? I wonder if the agent
doesn't support rsa-sha2-256 signatures or something?
Dropbear is meant to be handling the difference between the key names and
signature name
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 ---
АУДИОКНИГИ "МОДЕЛЬ ДЛЯ СБОРКИ"
Сам
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Sander Vanheule
> Sent: Freitag, 17. Juli 2020 13:38
> To: openwrt-devel@lists.openwrt.org
> Cc: Sander Vanheule ; m...@bibbl.com;
> julien.dus...@free.fr; j...@phrozen.org; ra...
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Sander Vanheule
> Sent: Freitag, 17. Juli 2020 13:38
> To: openwrt-devel@lists.openwrt.org
> Cc: Sander Vanheule ; m...@bibbl.com;
> julien.dus...@free.fr; j...@phrozen.org; ra...
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Sander Vanheule
> Sent: Freitag, 17. Juli 2020 13:38
> To: openwrt-devel@lists.openwrt.org
> Cc: Sander Vanheule ; m...@bibbl.com;
> julien.dus...@free.fr; j...@phrozen.org; ra...
This allows the user to disable the RSA algorithm in Dropbear, if not required.
(RSA is still enabled by default, of course, due to its ubiquity.)
Size comparison of the dropbear executable (cortex-a9+neon)…
RSA + Ed25519: 182804 bytes
Ed25519 only: 166356 bytes
… which amounts to over 16 kiB
Sometimes when using the DNS-313 memory usage can peak and
with a simple swap partition we can avoid running into the
roof and invoking the OOM killer. Set this partition to
128MB (twice the size of the memory of the DNS-313).
Signed-off-by: Linus Walleij
---
.../linux/gemini/image/dns313_gen_hd
This allows the user to disable the RSA algorithm in Dropbear, if not required.
(RSA is still enabled by default, of course, due to its ubiquity.)
Size comparison of the dropbear executable (cortex-a9+neon):
RSA + Ed25519: 182804 bytes
RSA only: 170496 bytes
Ed25519 only: 166356 bytes
S
Patches submitted upstream at
https://patchwork.ozlabs.org/project/uboot/list/?series=189178
Tested on Banana Pi R2 and U7623-06.
Signed-off-by: David Woodhouse
---
package/boot/uboot-mediatek/Makefile | 9 +-
...ix-mmc_get_boot_dev-for-platforms-wi.patch | 51 +++
...-Add-support-f
Currently the user space stack cookies work well also when the kernel
stack cookies are not activated. This is handled completely in user
space and does not need kernel support.
This dependency was probably needed some years ago when the libc did not
support stack cookies.
Signed-off-by: Hauke Me
Switch to binutils version 2.34 for all CPUs by default. The ARC CPUs
do not need any sepcial binutils version any more.
Tested on lantiq, ipq40xx
Signed-off-by: Hauke Mehrtens
---
toolchain/binutils/Config.in | 3 +--
toolchain/binutils/Config.version | 4 +---
2 files changed, 2 insertio
This fixes a warning in the SPI driver at bootup. This warning is seen
in kernel 5.4 on lantiq deives.
Signed-off-by: Hauke Mehrtens
---
...c-Fix-warning-by-using-WQ_MEM_RECLAI.patch | 35 +++
1 file changed, 35 insertions(+)
create mode 100644
target/linux/lantiq/patches-5.4/0
On Fri, Jul 17, 2020 at 2:53 PM Hauke Mehrtens wrote:
>
> Switch to binutils version 2.34 for all CPUs by default. The ARC CPUs
> do not need any sepcial binutils version any more.
>
> Tested on lantiq, ipq40xx
>
> Signed-off-by: Hauke Mehrtens
Acked-by: Rosen Penev
I've been using this since i
On Fri, Jul 17, 2020 at 3:21 AM Jo-Philipp Wich wrote:
>
> Hi,
>
> I've sent a fix using extern declarations upstream, lets see what happens.
Where? I don't see a merge request on the git link referenced in the Makefile.
>
> ~ Jo
>
> ___
> openwrt-devel
On Fri, Jul 17, 2020 at 3:49 AM Bjørn Mork wrote:
>
> Rosen Penev writes:
> >> On Jul 17, 2020, at 3:06 AM, Felix Fietkau wrote:
>
> >>> +--- a/ui_common.h
> >>> b/ui_common.h
> >>> +@@ -33,12 +33,12 @@ typedef struct host_pair_line_tag {
> >>> +
> >>> + extern options_t options;
> >>> +
>
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 ---
> Until now it has not been possib
On Fri, Jul 17, 2020 at 1:59 AM Petr Štetiar wrote:
> Or is there any other valid reason I'm missing right now?
I put my main reason in the original email:
"Submitting this separately, partly because the device-support patches
are a bit bigger and likely will take a little work."
Particularly, t
Matt Johnston [2020-07-17 19:54:51]:
Hi,
> Are you using a rsa key on disk, or using a SSH agent? I wonder if the agent
> doesn't support rsa-sha2-256 signatures or something?
I'm using Yubikeys as my key storage, so it's gpg-agent (GnuPG) 2.2.4 with
libgcrypt 1.8.1 running on Ubuntu 18.04. Dis
42 matches
Mail list logo
