Hello Zhijun,
On Sat, May 14, 2022 at 8:24 AM Zhijun You wrote:
> Glad to see there's someone else working on encap offload.
> Can confirm it works on my NETGEAR R7800 (QCA9984) with
> ath10k + firmware 10.4-3.9.0.2-00159
> Feel free to add my tested by tag.
>
> Tested-by: Zhijun You
Thank
Hello Oldřich and Edward,
Thank you once more for testing these changes. I additionally tested
QCA6174 and now I am ready to send a formal patch. May I use your
'tested-by' in subsequent submissions?
--
Sergey
___
openwrt-devel mailing list
Hello Jeffery,
On Fri, May 13, 2022 at 2:03 AM Jeffery To wrote:
> On Fri, May 13, 2022 at 6:26 AM Sergey Ryazanov
> wrote:
>>
>> +1
>>
>> Stephan, may I sincerely ask you to stop spamming the list?
>>
>> On Mon, May 9, 2022 at 12:08 PM wro
+1
Stephan, may I sincerely ask you to stop spamming the list?
On Mon, May 9, 2022 at 12:08 PM wrote:
> is the below weekly message of any informational value to _all_? can someone
> maybe block this if it's not? ..thanks ede
>
> On 08.05.2022 23:05, Stephen Walker via openwrt-devel wrote:
>>
Hello Edward,
On Wed, May 11, 2022 at 12:04 AM Edward Matijevic wrote:
> Tested on a TP-Link Archer C2600 (IPQ8064 + QCA9980), using official
> 22.03-rc1 and your patch on top of 22.03
> Load average peaks were still the same but with the offloading 1min
> avg wasn't changing as sharply as
Hello Oldřich,
On Sat, May 7, 2022 at 9:27 AM Oldřich Jedlička wrote:
> .Hi Sergey,
>
> pá 29. 4. 2022 v 3:36 odesílatel Sergey Ryazanov
> napsal:
>>
>> Frame encapsulation from Ethernet into the IEEE 802.11 frame format
>> takes a considerable host CPU time
the performance of their systems
and report their results are welcome :)
1. https://lore.kernel.org/ath10k/20220402153615.9593-1-ryazanov@gmail.com/
Signed-off-by: Sergey Ryazanov
---
...1-ath10k-improve-tx-status-reporting.patch | 55 ++
...-ath10k-turn-rawmode-into-frame_mode.patch | 72
On Wed, Apr 13, 2022 at 10:35 AM Henrik Ginstmark wrote:
> Den tis 15 mars 2022 kl 21:14 skrev Sergey Ryazanov :
>> On Tue, Mar 15, 2022 at 10:36 PM Henrik Ginstmark
>> wrote:
>>> Today it's hard coded to read text messages from SIM card.
>>> Not all devices st
essages
> --get-message
> --delete-message
> --get-raw-message
>
> If --storage is omitted default storage is sim, as before.
>
> Signed-off-by: Henrik Ginstmark
Looks good!
Reviewed-by: Sergey Ryazanov
___
openwrt-devel mailing
me)
> Den mån 14 mars 2022 kl 01:26 skrev Sergey Ryazanov :
>> Hello Henrik,
>>
>> On Sun, Mar 13, 2022 at 10:25 PM Henrik Ginstmark
>> wrote:
>>> Today it's hard coded to read text messages from SIM card.
>>> Not all devices store received text me
Hello Etienne,
On Mon, Mar 14, 2022 at 2:36 AM Etienne Champetier
wrote:
> We currently have some circular dependencies caused by the usage of
> PROVIDES and @IPV6
> https://github.com/openwrt/openwrt/issues/9407
>
> One radical way to fix, suggested by Jow, is to completely remove
> CONFIG_IPV6
Hello Henrik,
On Sun, Mar 13, 2022 at 10:25 PM Henrik Ginstmark wrote:
> Today it's hard coded to read text messages from SIM card.
> Not all devices store received text messages in SIM, they store
> in me, QMI_WMS_STORAGE_TYPE_NV.
> I have added a switch to choose sim or me for --list-messages,
ssage has been wrapped
> automatically by the mailing list software.
>
>
> -- Forwarded message --
> From: Eugenio Tampieri
> To: Sergey Ryazanov
> Cc: OpenWrt Development List
> Bcc:
> Date: Tue, 08 Mar 2022 09:20:08 +
> Subject: Re: ath9k: s
Hello Mike,
On Fri, Mar 4, 2022 at 9:54 PM mk 378 wrote:
> This adds support for the Mikrotik SXT-R LTE device, which is an
> outdoor router that hosts an LTE modem mini PCIe card for its WAN
> connection. The LTE antenna system claims a 9 dBi gain.
>
> Hardware:
> - SoC: QCA9531
> -
ci) that creates tmp files and uses rename() that is expected to be
> atomic.
>
> Signed-off-by: Rafał Miłecki
Acked-by: Sergey Ryazanov
And thank you for such a detailed analysis of the situation!
--
Sergey
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Hello Rafał,
On Fri, Feb 25, 2022 at 5:26 PM Rafał Miłecki wrote:
> my system is setup as follows:
>
> # mount | grep ubifs
> /dev/ubi0_1 on /mount/ubifs type ubifs
> (rw,noatime,assert=read-only,ubi=0,vol=1)
>
> # cat /proc/sys/vm/dirty_writeback_centisecs
> 500
> # cat
Hello Eugenio,
On Sat, Feb 26, 2022 at 1:22 PM Eugenio Tampieri via openwrt-devel
wrote:
> 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
ctionality. Now
the patch looks good for me.
Reviewed-by: Sergey Ryazanov
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
rb91x-nand fail to get a gpio and an error
> is -EPROBE_DEFER, they shouldn't report about this, since this
> actually is not an error and occurs when the gpio-latch probe
> function is called before the rb91x-key probe.
> We fix these related things here too.
>
> Si
On Wed, Jan 19, 2022 at 2:31 AM Hauke Mehrtens wrote:
> On 1/18/22 23:38, Sergey Ryazanov wrote:
>> On Mon, Jan 17, 2022 at 12:35 AM Hauke Mehrtens wrote:
>>> This adds the Atheros AR9381 to the devices list. This card was found in
>>> the TP-LINK TD-W8970.
>>&g
Hello Hauke,
On Mon, Jan 17, 2022 at 12:35 AM Hauke Mehrtens wrote:
> This adds the Atheros AR9381 to the devices list. This card was found in
> the TP-LINK TD-W8970.
>
> Signed-off-by: Hauke Mehrtens
> ---
> devices.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/devices.txt
On Mon, Jan 17, 2022 at 11:52 AM Denis K wrote:
>> I'm seeing this in the bootlogs when using this patch:
>>
>> [5.183305] gpio-latch gpio_latch: failed to get gpio 7: -517
>> [5.235889] rb91x-nand nand_gpio: failed to get gpios: -517
>
> It's okay. The gpio-latch probe function seems to
Hello Mauri,
On Mon, Jan 17, 2022 at 5:11 PM Mauri Sandberg wrote:
> I sent a patch set for review two months back but I am yet to receive
> any comments, ack/nack. Maybe nobody took action since I did not Cc:
> anyone specifically.
>
> Are there ppl who normally carry out reviews or should I
On Wed, Jan 12, 2022 at 6:55 PM Koen Vandeputte
wrote:
> On 17.11.21 00:42, Sergey Ryazanov wrote:
>> On Tue, Nov 16, 2021 at 7:07 PM Denis Kalashnikov
>> wrote:
>>> On MikroTik RB91x board series a reset key shares SoC gpio
>>> line #15 with NAND ALE and NAND
that utilizes alloc_etherdev();
* add the txqueue number argument to the .ndo_tx_timeout callback
function;
* replace ioremap_nocache() which was finally removed from the kernel by
the ioremap() with the same behaviour.
Switch target to the new kernel version.
Signed-off-by: Sergey Ryazanov
---
Changes
the next firmware release.
Suggested-by: Felix Fietkau
Signed-off-by: Sergey Ryazanov
---
Changes in v3:
* update the commit message to make it clear that switching to DSA is
possible but not an option for now
Changes in v2:
* new patch; earlier here was another patch that recovers mvswitch
c
driver, make it ath25 specific in v5.4 and then upgrade the
corresponding patch as usual, thanks Felix for the suggestion
CC: Hauke Mehrtens
CC: Rui Salvaterra
CC: Russell Senior
CC: Bjørn Mork
CC: Stefan Lippers-Hollmann
Sergey Ryazanov (3):
Move mvswitch 88E6060 driver to the ath
new
kernel configuration diff.
Signed-off-by: Sergey Ryazanov
---
Changes in v3:
* no changes
Changes in v2:
* no changes
target/linux/ath25/config-5.4 | 56 ++-
1 file changed, 2 insertions(+), 54 deletions(-)
diff --git a/target/linux/ath25/config-5.4 b/target/linux/at
Hello Stefan,
On Sun, Dec 19, 2021 at 12:12 AM Stefan Lippers-Hollmann wrote:
> On 2021-12-18, Sergey Ryazanov wrote:
>> On Sat, Dec 18, 2021 at 2:25 PM Bjørn Mork wrote:
>>> Sergey Ryazanov writes:
>>>> ath25 can not be switched to the DSA implementation due t
On Sat, Dec 18, 2021 at 6:18 PM Bjørn Mork wrote:
> Sergey Ryazanov writes:
>> But in this particular case, the
>> particular 88E6060 switch support can not be switched to the DSA
>> implementation because the DSA implementation does not support
>> configuration via t
Hello Bjørn,
On Sat, Dec 18, 2021 at 2:25 PM Bjørn Mork wrote:
> Sergey Ryazanov writes:
>> ath25 can not be switched to the DSA implementation due to lack of the
>> DTS support.
>
> I fully understand and accept that this isn't made a priority. But the
> explana
that utilizes alloc_etherdev();
* add the txqueue number argument to the .ndo_tx_timeout callback
function;
* replace ioremap_nocache() which was finally removed from the kernel by
the ioremap() with the same behaviour.
Switch target to the new kernel version.
Signed-off-by: Sergey Ryazanov
---
Changes
o be shure.
Changes in v2:
* instead of recovering mvswitch building with v5.10 as a generic
driver, make it ath25 specific in v5.4 and then upgrade the
corresponding patch as usual, thanks Felix for the suggestion
CC: Hauke Mehrtens
CC: Rui Salvaterra
CC: Russell Senior
Sergey Ryazanov (
as Fonera 2.0g (FON2202). So make it target specific to keep generic
config and patches clean.
Suggested-by: Felix Fietkau
Signed-off-by: Sergey Ryazanov
---
Changes in v2:
* new patch; earlier here was another patch that recovers mvswitch
support under the v5.10 kernel
.../files/drivers/net/phy
new
kernel configuration diff.
Signed-off-by: Sergey Ryazanov
---
Changes in v2:
* no changes
target/linux/ath25/config-5.4 | 56 ++-
1 file changed, 2 insertions(+), 54 deletions(-)
diff --git a/target/linux/ath25/config-5.4 b/target/linux/ath25/config-5.4
index
On Fri, Dec 17, 2021 at 12:34 PM Felix Fietkau wrote:
> On 2021-12-17 10:13, Sergey Ryazanov wrote:
>> On Fri, Dec 17, 2021 at 11:52 AM Felix Fietkau wrote:
>>> On 2021-12-16 23:29, Sergey Ryazanov wrote:
>>>> Support for mvswich driver (Marvell 88E6060 switch
On Fri, Dec 17, 2021 at 11:52 AM Felix Fietkau wrote:
> On 2021-12-16 23:29, Sergey Ryazanov wrote:
>> Support for mvswich driver (Marvell 88E6060 switches) build has been
>> missed during the initial v5.10 kernel introduction. But it is required
>> for AR21xx boards, e.
new
kernel configuration diff.
Signed-off-by: Sergey Ryazanov
---
target/linux/ath25/config-5.4 | 56 ++-
1 file changed, 2 insertions(+), 54 deletions(-)
diff --git a/target/linux/ath25/config-5.4 b/target/linux/ath25/config-5.4
index 4b47470699..10b81f0e03 100644
--- a/ta
that utilizes alloc_etherdev();
* add the txqueue number argument to the .ndo_tx_timeout callback
function;
* replace ioremap_nocache() which was finally removed from the kernel by
the ioremap() with the same behaviour.
Switch target to the new kernel version.
Signed-off-by: Sergey Ryazanov
---
target
ies=277243
CC: Hauke Mehrtens
CC: Rui Salvaterra
CC: Russell Senior
Sergey Ryazanov (3):
kernel: 5.10: recover 88E6060 switches support
ath25: refresh kernel 5.4 config
ath25: add kernel 5.10 support
target/linux/ath25/Makefile |2 +-
target/linux/ath25/c
with the ath25 target.
Fixes: b10d604459 ("kernel: add linux 5.10 support")
CC: Felix Fietkau
Signed-off-by: Sergey Ryazanov
---
.../generic/hack-5.10/700-swconfig_switch_drivers.patch | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/target/linux/generic/hac
in
the generic config since c7182123b9 ("kernel: make cryptoapi support
needed by mac80211 built-in"). So move the above options from the target
configs to the generic config to make it clear why do we need them.
CC: Felix Fietkau
Signed-off-by: Sergey Ryazanov
---
target/linux/apm821xx/c
Both CLANG_VERSION and LLD_VERISON are autogenerated runtime
configuration options, so add them to the kernel configuration filter
and remove from generic and per-target configs to keep configs clean.
Signed-off-by: Sergey Ryazanov
---
target/linux/armvirt/config-5.10 | 1 -
target
red during the ath25 target migration
to the 5.10 kernel (see the next series).
Sergey Ryazanov (2):
kernel: filter out both Clang and LLD versions
kernel: 5.10: consolidate mac80211 crypto options
target/linux/apm821xx/config-5.10 | 2 --
target/linux/archs38/config-5.10
Hello Arvid,
On Wed, Dec 15, 2021 at 2:13 PM Arvid Picciani wrote:
> ZBT-WE1206 has an external watchdog that with stock openwrt resets the board.
What board do you mean? I am unable to locate ZBT-WE1206 neither in
the repository, nor in google.
> should this get disabled in bringup or is this
ically solve one rare issue, we
unintentionally break a lot of running setups by triggering a modem
bug in the airplane mode exiting procedure. Anyway, I am just an
occasional project contributor, not from the core developers staff, so
you can ignore my thoughts all together ;)
> Den sön 5 de
On Sun, Dec 5, 2021 at 7:43 PM Henrik Ginstmark wrote:
> My intention was to speed up the registration to the LTE network.
If we talk about a modem that is part of a router, then I doubt
whether the airplane mode activation will be able to speed up the
registration procedure. After a router
On Sun, Dec 5, 2021 at 5:12 PM Bjørn Mork wrote:
> Sergey Ryazanov writes:
>> On Sun, Dec 5, 2021 at 3:32 PM Bjørn Mork wrote:
>>> Sergey Ryazanov writes:
>>>> I am, as an occasional user of an LTE modem, never faced a case when
>>>> the mode
On Sun, Dec 5, 2021 at 3:32 PM Bjørn Mork wrote:
> Sergey Ryazanov writes:
>> I am, as an occasional user of an LTE modem, never faced a case when
>> the modem is unable to register with a network due to an unconfigured
>> APN. The most prominent fact is that no one else
CC Piotr and Matti to draw some more attention to this case.
On Sun, Dec 5, 2021 at 2:19 AM Henrik Ginstmark wrote:
> Den lör 4 dec. 2021 kl 23:19 skrev Sergey Ryazanov :
>> On Sat, Dec 4, 2021 at 6:22 PM Henrik Ginstmark wrote:
>>> This command make it possible to
Please find a few comments related to a patch submission below. As for
the airplane mode requirements, I would like to split that discussion
into a separate thread and will send a separate reply.
On Sun, Dec 5, 2021 at 2:19 AM Henrik Ginstmark wrote:
> Den lör 4 dec. 2021 kl 23:19 skrev Ser
Hello Henrik,
On Sat, Dec 4, 2021 at 6:22 PM Henrik Ginstmark wrote:
> This command make it possible to query if the modem is in flight mode or not.
>
> If you need to change your APN setting it should be done during flight mode
> on.
Just curious, is this true for any Qualcomm based mode or
Hello Rosen,
On Tue, Nov 30, 2021 at 6:18 AM Rosen Penev wrote:
> On Tue, Nov 16, 2021 at 2:14 AM Sergey Ryazanov
> wrote:
>> Zbtlink ZBT-WG1602 is a Wi-Fi router intendent to use with WWAN
>> (UMTS/LTE/3G/4G) modems. The router board offsers a couple of miniPCIe
>> slo
On Wed, Nov 24, 2021 at 12:51 AM Sergey Ryazanov wrote:
> On Tue, Nov 16, 2021 at 1:09 PM Sergey Ryazanov
> wrote:
>> Zbtlink ZBT-WG1602 is a Wi-Fi router intendent to use with WWAN
>> (UMTS/LTE/3G/4G) modems. The router board offsers a couple of miniPCIe
>> slo
On Tue, Nov 16, 2021 at 1:09 PM Sergey Ryazanov wrote:
> Zbtlink ZBT-WG1602 is a Wi-Fi router intendent to use with WWAN
> (UMTS/LTE/3G/4G) modems. The router board offsers a couple of miniPCIe
> slots with USB and SIM only and another one pure miniPCIe slot as well
> as five Giga
le a polling
> of the key while it works with NAND, and we need to add
> "cansleep" suffix to several gpiolib calls in gpio-latch.
>
> Signed-off-by: Denis Kalashnikov
Please find below one nonsignificant nitpick, in all other respects:
Reviewed-by: Sergey R
emoved.
>
> Reported-by: Denis Kalashnikov
> Signed-off-by: Denis Kalashnikov
> Signed-off-by: Thibaut VARÈNE
Denis, Thibaut, nice catch and fix!
Reviewed-by: Sergey Ryazanov
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://
On Tue, Nov 16, 2021 at 3:40 PM Enrico Mioso wrote:
> Does the device use ZLoader?
If you mean Zyxel bootloader, then no. The board utilizes U-boot with
some PandoraBox patches according to the logo printed to the serial
console.
> Is a recovery mode available? (maybe document it in the commit)
Hello Roger,
On Tue, Nov 16, 2021 at 1:29 PM Roger Pueyo Centelles | Guifi.net
wrote:
> I spotted a very small typo on the commit message:
>
> * Eth: 10/100/100 Mbps Ethernet x5 ports (4xLAN + WAN)
>
> is probably
>
> * Eth: 10/100/1000 Mbps Ethernet x5 ports (4xLAN + WAN)
Sure, this should be
nWrt (LEDE) based, so the sysupgrade image can
be directly used to install OpenWrt. Firmware must be upgraded using the
'force' and 'do not save configuration' command line options (or
correspondig web interface checkboxes) since the vendor firmware is from
the pre-DSA era.
Signed-off-by: Sergey Ryaz
Hello Bastian,
On Thu, Oct 14, 2021 at 9:11 PM Bastian Bittorf wrote:
> I'am also an infrequent user. I do not see an issue
> for the moment, it compiles and runs just fine:
Thank you for taking care of testing it, one less problem.
--
Sergey
___
On Mon, Oct 11, 2021 at 12:12 AM Hauke Mehrtens wrote:
> On 10/10/21 2:44 AM, Sergey Ryazanov wrote:
>> On Fri, Oct 8, 2021 at 4:40 PM Rui Salvaterra wrote:
>>> On Fri, 8 Oct 2021 at 11:09, Rui Salvaterra wrote:
>>>> Nothing in this target has more than 32 MiB of
Hello Rui,
On Fri, Oct 8, 2021 at 4:40 PM Rui Salvaterra wrote:
> On Fri, 8 Oct 2021 at 11:09, Rui Salvaterra wrote:
>> Nothing in this target has more than 32 MiB of RAM (most devices have
>> 16 MiB) [1]. Just put it out of its misery. :)
>
> Scratch that. After chatting with dangole, there
On Fri, Oct 8, 2021 at 10:17 PM Paul Spooren wrote:
> On 10/8/21 5:54 AM, Sergey Ryazanov wrote:
>> On Fri, Oct 8, 2021 at 12:05 PM Paul Spooren wrote:
>>> as previously posted on GitHub[1] I'd like to remove the UML target
>>> since it seems broken, isn't offere
Hello Paul,
thank you for posting this to ML.
On Fri, Oct 8, 2021 at 12:05 PM Paul Spooren wrote:
> as previously posted on GitHub[1] I'd like to remove the UML target
> since it seems broken, isn't offered by our buildbots and it's purpose
> for testing can be replaced by using qemu.
>
> Is
.
>
> This patch adds missing closing quote, fixing the above warning.
>
> Signed-off-by: Paul Blazejowski
Nice catch!
Reviewed-by: Sergey Ryazanov
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Hello Petr,
On Fri, Jul 2, 2021 at 12:31 PM Petr Štetiar wrote:
> Sergey Ryazanov [2021-06-29 02:07:16]:
>> OTOH, Arjun has been trying to draw attention to the patch for comgt
>> for a year. And no one reacted to his quite reasonable fix.
>
> As always, any additional `Te
On Mon, Jun 28, 2021 at 11:57 PM Lech Perczak wrote:
> W dniu 2021-06-28 o 21:55, Paul Spooren pisze:
>> On 6/28/21 9:53 AM, John Crispin wrote:
>>> On 28.06.21 21:14, Paul Spooren wrote:
I'm in favor of this too but if it's a core feature (i.e. SIM card
support) we should provide the
Hello Ontje,
On Mon, Jun 28, 2021 at 3:00 PM wrote:
> The rut955 fails to activate its modem upon every second reboot otherwise.
What does it mean "fails to activate modem"? Could you be more
specific? A bit more detailed issue description will be helpful if
someone faces a similar case, even
On Thu, May 27, 2021 at 11:18 AM Denis Kalashnikov
wrote:
> From: Denis Kalashnikov
>
> This is a slighty modified version of ar71xx gpio-latch driver
> written by Gabor Juhos .
>
> Changes:
> * DTS support,
> * New gpio API (gpiod_*).
>
> Signed-off-by: Denis Kal
_*) support.
>
> Signed-off-by: Denis Kalashnikov
Reviewed-by: Sergey Ryazanov
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
On Mon, Jun 14, 2021 at 6:29 PM Koen Vandeputte
wrote:
> On 27.05.21 10:16, Denis Kalashnikov wrote:
> > From: Denis Kalashnikov
> >
> > RB912 needs two ad hoc drivers: gpio-latch and rb91x_nand. So I've ported
> > them
> > from ar71xx and added DTS.
> >
> > In RFC v1 I added a MFD driver that
t,
> boot kernel and initramfs and then perform sysupgrade.
> * From ar71xx OpenWrt firmware run:
> $ sysupgrade -F /tmp/
> For more info see: https://openwrt.org/toh/mikrotik/common.
>
> Co-Developed-by: Koen Vandeputte
> Signed-off-by: Denis Kalashnikov
Reviewed-by: Sergey Ryazan
On Mon, Jun 14, 2021 at 9:02 PM Adrian Schmutzler
wrote:
>
> Hi,
>
> a few remaining comments below.
>
>> + gpio-export {
>> + compatible = "gpio-export";
>> +
>> + usb_power {
>> + label = "power:usb";
>
> gpio-export nodes normally don't have a
with MikroTik RB411U board.
Signed-off-by: Sergey Ryazanov
---
Changes since v1:
* rebased on top of latest master
* rephrased the comment in the hook function, thanks to Bas for
noticing this
.../files/drivers/mtd/nand/raw/nand_rb4xx.c | 25 ---
1 file changed, 22 insertions
Hello Adrian,
On Mon, May 31, 2021 at 1:15 AM Adrian Schmutzler
wrote:
>
> Hi,
>
> > -Original Message-
> > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> > On Behalf Of Sergey Ryazanov
> > Sent: Montag, 24. Mai 2021 01:07
Hello Bas,
thank you for your review, please find my comments below.
On Fri, May 28, 2021 at 11:41 AM Bas Mevissen wrote:
> On 2021-05-28 00:27, Sergey Ryazanov wrote:
[skipped]
>> +static int rb4xx_nand_attach_chip(struct nand_chip *chip)
>> +{
>> + struct mtd_in
with MikroTik RB411U board.
Signed-off-by: Sergey Ryazanov
---
.../files/drivers/mtd/nand/raw/nand_rb4xx.c | 25 ---
1 file changed, 22 insertions(+), 3 deletions(-)
diff --git a/target/linux/ath79/files/drivers/mtd/nand/raw/nand_rb4xx.c
b/target/linux/ath79/files/drivers/mtd/nand
On Fri, May 21, 2021 at 2:05 PM Denis Kalashnikov wrote:
> Main part is copied from ar71xx original driver rb91x_nand
> written by Gabor Juhos .
>
> What is done:
> * Support of kernel 5.4 and 5.10,
> * DTS support,
> * New gpio API (gpiod_*) support.
>
> Signed-off-by: Denis Kalashnikov
> ---
>
On Fri, May 21, 2021 at 2:05 PM Denis Kalashnikov wrote:
> This is a slighty modified version of ar71xx gpio-latch driver
> written by Gabor Juhos .
>
> Changes:
> * DTS support,
> * New gpio API (gpiod_*).
>
> Signed-off-by: Denis Kalashnikov
> ---
>
> Changelog:
>
> v1-->v2:
> - Don't use MFD
On Fri, May 21, 2021 at 2:05 PM Denis Kalashnikov wrote:
> In the first vertion of these patches I've added a MFD driver that
> provides API for manipulating shared gpio lines to gpio-latch and nand
> drivers. Now I just port gpio-latch and rb91x_nand drivers from ar71xx
> to ath79 by adding DTS
On Fri, May 21, 2021 at 2:05 PM Denis Kalashnikov wrote:
>
> This board has been supported in the ar71xx.
>
> Links:
> * https://mikrotik.com/product/RB912UAG-2HPnD
> * https://mikrotik.com/product/RB912UAG-5HPnD
> * https://openwrt.org/toh/hwdata/mikrotik/mikrotik_rb912uag-2hpnd
> *
Hello Adrian and Denis,
sorry for interfering with your conversation, I would like to discuss
the best way to document not yet finished functionality. Please find
my question and proposal below.
On Sun, May 23, 2021 at 12:01 PM Adrian Schmutzler
wrote:
[skipped]
>> + beeper {
>> +
On Thu, May 6, 2021 at 7:31 PM Denis Kalashnikov wrote:
> rb91x-ngl (nand-gpio-latch) requests and controls SoC GPIO
> lines that are used for NAND control and data lines multiplexed
> with a latch. Lines of the latch that are not used for NAND
> control lines, are used for power LED and user LED
On Thu, May 6, 2021 at 7:32 PM Denis Kalashnikov wrote:
> + /*
> +* MFD: NAND plus GPIO-controller. They use/share SoC GPIO lines.
> Some of the
> +* GPIO lines are multiplexed by a 8-bit latch (LVC573).
> +* NAND is controlled by GPIO lines (bitbang), also some
On Thu, May 6, 2021 at 7:32 PM Denis Kalashnikov wrote:
[skipped]
> +#define DRIVER_NAME "rb91x-gpio-latch"
Maybe just "rb91x-gpio"? Looks like this board has no more crazy GPIO
controllers.
> +static int get(struct gpio_chip *gc, unsigned offset)
> +{
> + return -ENOSYS;
> +}
On Thu, May 6, 2021 at 7:31 PM Denis Kalashnikov wrote:
> rb91x-ngl (nand-gpio-latch)
I would like to suggest rename it to 'rb91x-latch'. This driver has no
NAND or GPIO functionality. Looks like it just multiplexes access to
subordinate HW, what is clearly indicated by the device tree, where
Hello Denis,
On Thu, May 6, 2021 at 7:31 PM Denis Kalashnikov wrote:
> When porting RB91xG ad hoc drivers (gpio-latch and rb91x-nand) from ar71xx
> to ath79, I made a decision to rework this to more clear design in my opinion:
> MFD driver that requests and controls the gpio lines, and separate
Hello Danijel,
On Tue, Mar 23, 2021 at 3:21 PM Sergey Ryazanov wrote:
> On Mon, Mar 22, 2021 at 11:54 PM Danijel wrote:
>> So now I'm looking for testers (and reviewers) who could test this change on
>> the affected devices (with bad blocks) and NOR Mikrotiks.
>
> I h
Hello Danijel!
On Mon, Mar 22, 2021 at 11:54 PM Danijel wrote:
> I'm working on restoring Mikrotik RB2011 support after ar71xx target was
> dropped after 19.07 release. While working on it, the problem with bad blocks
> and the issue of the current way of flashing kernel was also brought up.
>
>
On Wed, Sep 9, 2020 at 6:08 PM Adrian Schmutzler
wrote:
> > - vconfig add eth0 1
> > + ip link add dev eth0.1 link eth0 type vlan id
> > 1
>
> Are you sure this is correct?
Yes, I tested this command with an OpenWrt ip package :)
> I only
On Sun, Sep 6, 2020 at 6:32 PM Adrian Schmutzler
wrote:
> I have pushed my to-be-merged collection of patches here:
> https://git.openwrt.org/?p=openwrt/staging/adrian.git;a=shortlog;h=refs/heads/ath25merge
Thank you for this careful work! Commit that recovers 4.14 patches,
but within the 5.4
with a subject
switch IC, but this is still better then call an utility that is
unavailable in the firmware for years.
Signed-off-by: Sergey Ryazanov
---
.../base-files/lib/preinit/15_preinit_iface_atheros | 9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/target
On Sat, Sep 5, 2020 at 10:36 AM Adrian Schmutzler
wrote:
> > This series returns back ath25 target and switches it to 5.4 kernel.
>
> I will take care, but probably alter the patches so we directly start with
> kernel 5.4, and not add back 4.14 just to remove it again.
Sure. But specify the
This reverts commit 7d29a557140381ef1815329f6843b88b4126d490.
Discussion in the mailing list reveals that this target have active
users. Also we are able to uprgade this target to 5.4 kernel, so
resurect the target first by reverting the commit.
Signed-off-by: Sergey Ryazanov
---
package
Remove no more used 4.14 kernel support.
Signed-off-by: Sergey Ryazanov
---
target/linux/ath25/config-4.14| 170 --
.../ath25/patches-4.14/107-ar5312_gpio.patch | 212 --
.../ath25/patches-4.14/108-ar2315_gpio.patch | 363
.../patches-4.14/110-ar2313_ethernet.patch
Copy and refresh patches and config from 4.14. The only couple of fixes
required to make kernel buildable:
* rework ethernet supported link modes to linkmode bitmask;
* drop erase callback invocation from AR2315 MTD driver.
Signed-off-by: Sergey Ryazanov
---
target/linux/ath25/Makefile
sysupgrade (power issue?). But
Ethernet and Wi-Fi interfaces were tested and work as expected.
Sergey Ryazanov (5):
Revert "ath25: drop target"
ath25: add kernel 5.4 support
ath25: eth: fix crash on skb DMA (un-)map
ath25: switch to 5.4 kernel
ath25: drop 4.14 kernel support
pack
AR2315 Ethernet driver pass NULL instead of a real device pointer to DMA
(un-)map calls. With kernel version 5.4 such behaviour causes a kernel
panic. Fix this issue by preserving device pointer during the probe
procedure and pass it to each skb data DMA (un-)map call.
Signed-off-by: Sergey
Switch to actual kernel version.
Signed-off-by: Sergey Ryazanov
---
target/linux/ath25/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/ath25/Makefile b/target/linux/ath25/Makefile
index 0ed40bd54b..3edbaf19b6 100644
--- a/target/linux/ath25/Makefile
1 - 100 of 334 matches
Mail list logo
