Hi,
On 11.04.2024 10:52, Bjørn Mork wrote:
Ivan Ivanov writes:
SOC: MediaTek MT7981B , Wi-Fi: MediaTek MT7976C
Are these Mediateks capable of working without any binary blobs, at
least in theory?
A simple question back to you: Could you please list the wifi chips you
know of which ether
ady existing core and community packages use
slash in 'SUBMENU' variables. As this is more a RFC/PoC, final change
might use different character or approach for defining menu path.
Signed-off-by: Piotr Dymacz
---
scripts/metadata.pm | 6 ++-
scripts/package-meta
Hi,
On 30.01.2024 19:15, Christian Marangi (Ansuel) wrote:
Robert is active in OpenWrt since 2017 and with some recent stats, he
has more than 310 commits merged in OpenWrt.
He also have uncounted Reviewed-by tag on various PR and merged commits
and generally helps in everything related to IPQ
Hi Forest,
On 10.01.2024 15:18, Forest Crossman wrote:
On Tue, Jan 9, 2024 at 4:52 AM John Crispin wrote:
---SNIP---
* Why is there no USB 3.x host port on the device?
- the USB 3.x and PCIe buses are shared in the selected SoC silicon,
hence only a single High-Speed USB port is available
Hi Daniel, Bjørn,
On 10.01.2024 12:14, Daniel Golle wrote:
Hi!
On Wed, Jan 10, 2024 at 11:47:08AM +0100, Bjørn Mork wrote:
John Crispin writes:
> At the beginning we focused on the most powerful (and
> expensive) configurations possible but finally ended up with something
> rather simple
Hi Chuanhong,
On 9.01.2024 14:51, Chuanhong Guo wrote:
Hi!
On Tue, Jan 9, 2024 at 6:52 PM John Crispin wrote:
[...]
FAQ
* Why are there are 2 different flash chips?
- the idea is to make the device (almost!) unbrickable and very easy to
recover
What about a built-in JTAG probe instead of
Hi Janusz,
On 9.01.2024 19:14, Janusz Dziedzic wrote:
wt., 9 sty 2024 o 18:59 Daniel Golle napisał(a):
On Tue, Jan 09, 2024 at 06:49:04PM +0100, Janusz Dziedzic wrote:
> wt., 9 sty 2024 o 18:02 Robert Marko napisał(a):
> >
> > On Tue, 9 Jan 2024 at 17:53, Rafał Miłecki wrote:
> > >
> > >
Hi Enrico,
On 9.01.2024 13:55, Enrico Mioso wrote:
Hello!!
First of all, let me thank You all for this great project.
I wll do my best to buy some units - even tough I am not contributing by any
mean to OpenWrt in terms of code, or very little, I am very passionate about
this project and the
Hi Robert,
Adding John's correct e-mail to the loop.
On 8.12.2023 11:02, Robert Marko wrote:
On Fri, 8 Dec 2023 at 11:01, Piotr Dymacz wrote:
Hi Robert,
On 7.12.2023 12:52, Robert Marko wrote:
>
> On 07. 12. 2023. 12:20, Varadarajan Narayanan wrote:
>> On Thu, Dec 07, 2023 a
Hi Robert,
On 7.12.2023 12:52, Robert Marko wrote:
On 07. 12. 2023. 12:20, Varadarajan Narayanan wrote:
On Thu, Dec 07, 2023 at 11:11:03AM +0100, Robert Marko wrote:
On 07. 12. 2023. 10:59, Varadarajan Narayanan wrote:
SoC : QCOM IPQ9574
RAM : 2GB DDR4
Flash
Hi Rafał,
I'm trying to use the new NVMEM cells with mt76 EEPROM bindings on an
mt7621 (SPI NOR flash) with mt79x5 (PCIe) based device, same way as you
did in 03b3284805 [1] and daaa0c1b25 [2] (ath79 target).
If I keep 'eeprom' within 'nvmem-layout', wifi doesn't work due to:
Hi Koen,
On 24.01.2023 22:08, Koen Vandeputte wrote:
[...]
Piotr,
Would you have any idea here?
Not really, very strange.
What makes me wondering is that it doesn't look like a h/w related thing
(e.g. watchdog fire or some sudden current consumption spike resulting
in reset) and more
Hi Andy,
On 20.09.2022 08:47, Andy Tang wrote:
Hi Piotr,
Please look at my response about your concerns below.
See my reply below.
-Original Message-
From: Piotr Dymacz
Sent: 2022年8月23日 19:23
To: Andy Tang
Cc: openwrt-devel@lists.openwrt.org; Rafał Miłecki ;
Petr Štetiar
Subject
Hi Andy,
On 17.08.2022 09:36, Andy Tang wrote:
Hi Piotr,
Thanks for your valuable suggestions.
I will address most of your concern.
Some responses are inline.
-Original Message-
From: Piotr Dymacz
Sent: 2022年8月16日 19:16
To: Andy Tang
Cc: openwrt-devel@lists.openwrt.org; Rafał
Hi Andy,
Sorry for late reply. Please, see my comments inline below.
Rafał, Petr, it would be great if you could give your thoughts regarding
my concerns about the 'firmware-imx' package.
On 04.07.2022 09:24, Yuantian Tang wrote:
Imx8mplus_evk device is built to meet the needs of Smart
Hi Hauke,
On 17.04.2022 16:40, Hauke Mehrtens wrote:
On 4/8/22 00:29, Marcin Gordziejewski wrote:
TP-Link RE650 v2 is largely similar to v1 that
is already supported by OpenWrt. Notable differences
is differnt SPI Flash - 8 MB instead of 16 MB
(from cFeon instead of Winbond) and a different
=bcm2710` etc.
Keep support for obsolete `platform` and `subtarget_platform` targets
with deprecation notice so this compat stuff could be removed in the
future.
Signed-off-by: Petr Štetiar
Acked-by: Piotr Dymacz
Thanks!
--
Cheers,
Piotr
___
openwrt
[pep...@gmail.com: backported to 21.02]
Fixes: #9655, #9636, #9547
Signed-off-by: Piotr Dymacz
(backported from commit 74516f4357d281f093f0daac01c4c5c239acc443)
---
target/linux/ramips/dts/mt7620a_zbtlink_zbt-we1026-h-32m.dts | 4
target/linux/ramips/dts/mt7620a_zbtlink_zbt-we1026.dtsi |
f-by: Petr Štetiar
[pep...@gmail.com: updated commit title for 2022.01]
Signed-off-by: Piotr Dymacz
---
target/linux/imx/image/bootscript-toradex_apalis | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/target/linux/imx/image/bootscript-toradex_apalis
b/target/linux
boot.patch
The 'CONFIG_SPL_FORCE_MMC_BOOT' was removed in 15aec318ef03 ("Revert
"imx: Introduce CONFIG_SPL_FORCE_MMC_BOOT to force MMC boot on falcon
mode").
Signed-off-by: Piotr Dymacz
---
package/boot/uboot-imx/Makefile | 4 ++--
...efconfig-enable-some-useful-commands.patch | 21 -
Signed-off-by: Piotr Dymacz
---
package/boot/uboot-imx/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/boot/uboot-imx/Makefile b/package/boot/uboot-imx/Makefile
index d5f595..63f145798d 100644
--- a/package/boot/uboot-imx/Makefile
+++ b/package/boot
' in
mainline U-Boot sources.
Signed-off-by: Piotr Dymacz
---
target/linux/imx/image/cortexa9.mk | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/target/linux/imx/image/cortexa9.mk
b/target/linux/imx/image/cortexa9.mk
index 75e19dc694..17a507b8da 100644
--- a/target
Hi Petr,
On 29.03.2022 12:55, Petr Štetiar wrote:
Piotr Dymacz [2022-03-29 10:10:00]:
Hi,
It seems I've been misusing 'target' for a long time and now I'm trying to
understand how this leads to the same behavior as 'platform' :)
comments right above that code states following
Hi Petr,
On 29.03.2022 08:34, Petr Štetiar wrote:
Make it clear, that for `make kernel_{menu,old}config` it's possible to
use only following values for CONFIG_TARGET variable:
* env
* platform
* subtarget
* subtarget_platform
It seems I've been misusing 'target' for a long time and
Hi Stijn,
On 26.02.2022 11:11, Stijn Tintel wrote:
57d0e31 tplink-safeloader: TP-Link EAP615-Wall v1 support
There were more changes:
eea4ee7 tplink-safeloader: add TP-Link Archer A9 v6 support
8a8da19 tplink-safeloader: add TL-WPA8631P v3 support
57d0e31 tplink-safeloader: TP-Link
Hi Joe,
On 23.02.2022 00:59, jwmulla...@gmail.com wrote:
From: Joe Mullally
Enable creating images compatible with TP-Link's WPA8631P powerline router.
This matches all current firmwares for all revisions and regions.
Users with older EU "Build 20200314 Rel.3608" & EU "Build 20200508
Hi Rafał,
On 30.11.2021 14:00, Rafał Miłecki wrote:
From: Rafał Miłecki
Those tools can be useful for targets that use ITB firmware format. They
may need them to extract firmware images to flash them.
Truly a cosmetic thing but all other U-Boot related packages we
currently carry in the
/openwrt/list/?series=266900
--
Cheers,
Piotr
On 2021/10/06 0:55, Tim Harvey wrote:
On Tue, Oct 5, 2021 at 8:42 AM Piotr Dymacz wrote:
Hi Tim,
On 04.10.2021 00:22, Tim Harvey wrote:
Piotr,
How is your progress regarding submitting patches to OpenWrt to split
the imx target into multiple
Signed-off-by: Piotr Dymacz
---
target/linux/imx/config-5.4 | 420 -
...ARM-dts-imx-Add-GW5907-board-support.patch | 481 ---
...ARM-dts-imx-Add-GW5910-board-support.patch | 581 --
...ARM-dts-imx-Add-GW5913-board-support.patch | 434
Signed-off-by: Piotr Dymacz
---
target/linux/imx/cortexa7/config-default | 5 -
target/linux/imx/cortexa9/config-default | 7 ++-
2 files changed, 10 insertions(+), 2 deletions(-)
diff --git a/target/linux/imx/cortexa7/config-default
b/target/linux/imx/cortexa7/config-default
index
by the original 'imx6' target.
Signed-off-by: Piotr Dymacz
---
target/linux/imx/Makefile | 3 +-
target/linux/imx/config-5.10 | 65 +-
target/linux/imx/config-5.4 | 60 +
.../base-files/etc/board.d/02_network | 0
.../imx
Signed-off-by: Piotr Dymacz
---
target/linux/imx/Makefile | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/target/linux/imx/Makefile b/target/linux/imx/Makefile
index 17f634a7bf..b293655a9a 100644
--- a/target/linux/imx/Makefile
+++ b/target/linux/imx/Makefile
@@ -10,8 +10,7
. i.MX 7) might be enabled later, while adding
more devices.
Signed-off-by: Piotr Dymacz
---
target/linux/imx/Makefile | 2 +-
.../base-files/etc/board.d/02_network | 15
.../base-files/lib/upgrade/platform.sh| 16 +
target/linux/imx
All currently supported devices belong to the imx/cortexa9 subtarget.
Signed-off-by: Piotr Dymacz
---
package/boot/uboot-imx/Makefile | 3 +++
1 file changed, 3 insertions(+)
diff --git a/package/boot/uboot-imx/Makefile b/package/boot/uboot-imx/Makefile
index 9ca4d55a1c..2faa48bd73 100644
Subtarget-specific files under 'uboot-envtools' package are supported
since 6f3a05ebb0 ("uboot-envtools: support uci-default config also per
subtargets").
Signed-off-by: Piotr Dymacz
---
package/boot/uboot-envtools/files/{imx => imx_cortexa9} | 0
1 file changed, 0 insertions(+)
Signed-off-by: Piotr Dymacz
---
package/boot/{uboot-imx6 => uboot-imx}/Makefile | 2 +-
...0001-apalis_imx6_defconfig-enable-some-useful-commands.patch | 0
.../patches/110-mx6cuboxi-mmc-fallback.patch| 0
.../patches/111-mx6cuboxi_defconfig-force-
Signed-off-by: Piotr Dymacz
---
package/boot/uboot-envtools/files/{imx6 => imx} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename package/boot/uboot-envtools/files/{imx6 => imx} (98%)
diff --git a/package/boot/uboot-envtools/files/imx6
b/package/boot/uboot-envtools/fil
i.MX 9.
Signed-off-by: Piotr Dymacz
---
target/linux/{imx6 => imx}/Makefile | 4 ++--
.../{imx6 => imx}/base-files/etc/board.d/02_network | 0
target/linux/{imx6 => imx}/base-files/etc/inittab | 0
.../lib/imx6.sh => imx/base-files/lib/imx.sh} | 0
..
Signed-off-by: Piotr Dymacz
---
package/boot/kobs-ng/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/boot/kobs-ng/Makefile b/package/boot/kobs-ng/Makefile
index 3fa8302b8c..68e6ff170c 100644
--- a/package/boot/kobs-ng/Makefile
+++ b/package/boot/kobs-ng
Signed-off-by: Piotr Dymacz
---
package/kernel/hwmon-gsc/Makefile | 2 +-
package/kernel/linux/modules/can.mk| 2 +-
package/kernel/linux/modules/crypto.mk | 6 +++---
package/kernel/linux/modules/input.mk | 2 +-
package/kernel/linux/modules/sound.mk | 8
package/kernel
;imx6: image: drop BOOT_SCRIPT and fix DEVICE_NAME")
Reported-by: Koen Vandeputte
Signed-off-by: Piotr Dymacz
---
target/linux/imx6/image/Makefile| 2 +-
.../image/{bootscript-gateworks_ventana => bootscript-ventana} | 0
2 files changed, 1 insertion(+
This is a minor extension of the commit 26ae69fd03 ("imx6: refresh
kernel config with 5.10 symbols"), with correct and full disable of
the Arm Cortex-A7 based i.MX 6UL and 6UL{L,Z} families support and
re-enable of the Cortex-A9 based i.MX 6L{S,X}.
Signed-off-by: Piotr Dymacz
---
ta
for devices will follow).
Some examples of work-in-progress devices support in 'imx/cortexa7'
subtarget are available in my and Petr's staging trees [1], [2].
Additionally, the new target is switched to kernel 5.10, support for
the 5.4 is dropped and Gateworks Ventana related bug is fixed.
Piotr
Hi Tim,
On 04.10.2021 00:22, Tim Harvey wrote:
Piotr,
How is your progress regarding submitting patches to OpenWrt to split
the imx target into multiple arch related subtargets (like cortexa7,
cortexa9)?
I'm planning to clean it up and send patches this week.
I finally got final revision of
Hi Arjun,
On 01.07.2021 21:50, Arjun AK wrote:
Signed-off-by: Arjun AK
There are many devices with uqmi dependency (more than 10?).
Personally, I would prefer to keep this one in the core packages set.
--
Cheers,
Piotr
---
package/network/utils/uqmi/Makefile | 48 --
Hi Arjun, Lech,
On 29.06.2021 17:57, Arjun AK wrote:
On 29/06/21 2:21 am, Lech Perczak wrote:
[...]
OTOH, this differs a bit from such packages, by being needed to connect
to WAN on such devices. This is the same way as uqmi does on some -
removing it would require other Internet
Hi John,
On 28.06.2021 20:32, John Crispin wrote:
On 28.06.21 19:26, Piotr Dymacz wrote:
I might be wrong here but I think we don't include packages from
external feeds inside 'DEVICE_PACKAGES' (not sure/don't remember why).
I am in favour of moving all none-core packages to the feeds
Hi Arjun,
On 28.06.2021 19:43, Arjun AK wrote:
On 28/06/21 10:56 pm, Piotr Dymacz wrote:
Hi Arjun,
On 28.06.2021 18:52, Arjun AK wrote:
Signed-off-by: Arjun AK
The only problem here is a D-Link DWR-512B device (ramips/rt305x target)
which has 'comgt-ncm' package listed under
Hi Arjun,
On 28.06.2021 18:52, Arjun AK wrote:
Signed-off-by: Arjun AK
The only problem here is a D-Link DWR-512B device (ramips/rt305x target)
which has 'comgt-ncm' package listed under 'DEVICE_PACKAGES', see [1].
I might be wrong here but I think we don't include packages from
external
Hi Ontje,
On 28.06.2021 13:56, ontje.luensd...@dlr.de wrote:
From: Ontje Lünsdorf
The rut955 fails to activate its modem upon every second reboot otherwise.
This will issue reset every time the qmi connection is (re-)initialized,
making the whole (re-)connection process much longer. Does
Hi Koen,
On 25.06.2021 11:04, Koen Vandeputte wrote:
Hi Piotr,
It seems imx6 Gateworks Ventana target got broken.
I suspect it's due to following commit:
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=8dba71dd33c8e35e7f363ffdb2ba42259ab43ce2
After this commit, the bootfile
Hi Daniel,
On 27.05.2021 12:37, Daniel Golle wrote:
Don't bail out from init script in case the GPS device is missing.
Some modems take time to come up, and some people may use things like
'kplex' to feed ugpsd. Hence it is better to always start ugpsd
unconditionally and let procd's respawn
one.
Signed-off-by: Piotr Dymacz
---
package/boot/uboot-envtools/Makefile | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/package/boot/uboot-envtools/Makefile
b/package/boot/uboot-envtools/Makefile
index a9eccec0ce..597a029bee 100644
--- a/package/boot/uboot
Hi,
I have two devices based on the NXP i.MX6 ULL I would like to get
officially supported by OpenWrt.
The UL, ULL and ULZ series, in contrast to the rest of i.MX6 family
(Cortex-A9), are based on the Cortex-A7.
I'm wondering what would be the most acceptable way to handle this?
Is
These devices never got officially supported in the tree thus it doesn't
make much sense to waste our infrastructure resources and keep building
dedicated U-Boot images for them.
CC: Petr Štetiar
CC: Luka Perkov
Signed-off-by: Piotr Dymacz
---
package/boot/uboot-imx6/Makefile | 35
Hi Adrian,
On 06.02.2021 17:42, Adrian Schmutzler wrote:
Hi,
when reviewing device-support PRs, I frequently encounter the case that initial
flashing means sysupgrading from an OEM-modified OpenWrt.
This obviously means that the config of this OEM-OpenWrt should be wiped to
prevent
Signed-off-by: Piotr Dymacz
---
package/base-files/Makefile | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/package/base-files/Makefile b/package/base-files/Makefile
index e13578860f..a08bcce733 100644
--- a/package/base-files/Makefile
+++ b/package/base-files/Makefile
Hi Felix, Adrian,
On 30.09.2020 13:53, Felix Fietkau wrote:
On 2020-09-30 13:43, Adrian Schmutzler wrote:
-Original Message-
From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
On Behalf Of Adrian Schmutzler
Sent: Sonntag, 27. September 2020 23:55
To:
Hi Scott,
On 19.08.2020 23:57, Heppler, J. Scott wrote:
Too much effort to say "No interest at this time?"
I agree, we do have problem answering e-mails from contact@ inbox.
But I hope we will soon sort it out and get better at it.
--
Cheers,
Piotr
On Aug 19, 2020: 23:25, Pi
Hi Scott,
On 18.08.2020 23:27, Heppler, J. Scott wrote:
request.
Reply-To:
Organization:
I sent an email to cont...@openwrt.org, subject line Trademark Use
Request, inquiring about crowd funding an OpenWrt router. I never
received a reply. The email gave the background, links to forum
Hi,
On 27.07.2020 03:30, Heppler, J. Scott wrote:
I came onto a Trendnet TEW-827DRU Version 2 that is MT7621an with
MT7615E x 2 wifi chips. I was able to get UART output and stock has
these partitions:
[2.512000] 0x-0x0100 : "ALL"
[2.52]
Hi Adrian,
On 14.05.2020 16:02, Adrian Schmutzler wrote:
The property "ralink,port-map" never existed, and the device is a
one-port anyway. Just remove it.
Never? Did you check d57223259b?
--
Cheers,
Piotr
Fixes: 5ef79af4f80f ("ramips: add support for Ravpower WD03")
Signed-off-by:
Hi Tomasz, Li,
On 14.04.2020 20:53, Tomasz Maciej Nowak wrote:
W dniu 14.04.2020 o 06:20, Li.zhang pisze:
Hi Tomasz,
Thank you very much for you correction.
+};
+
+ {
+status = "okay";
+
+flash@0 {
+reg = <0>;
+compatible = "jedec,spi-nor";
+
Hi Tomasz, Paul,
On 01.04.2020 14:03, Tomasz Maciej Nowak wrote:
W dniu 01.04.2020 o 08:55, Piotr Dymacz pisze:
Hi Paul,
On 01.04.2020 01:20, Paul Spooren wrote:
The PROFILE names of mvebu/cortexa9/Linksys devices are based on the
consumer names (like linksys_wrt1200ac) instead of the vendor
Hi Paul,
On 01.04.2020 01:20, Paul Spooren wrote:
The PROFILE names of mvebu/cortexa9/Linksys devices are based on the
consumer names (like linksys_wrt1200ac) instead of the vendor codenames
(like linksys_caiman) which are however used in the rest of the build
system (plathform.sh, bootcount,
Hi Adrian,
On 25.03.2020 16:53, m...@adrianschmutzler.de wrote:
-Original Message-
From: Piotr Dymacz [mailto:pep...@gmail.com]
Sent: Mittwoch, 25. März 2020 15:08
To: m...@adrianschmutzler.de; openwrt-devel@lists.openwrt.org
Cc: Felix Fietkau ; Jo-Philipp Wich
Subject: Re: [OpenWrt
Hi Adrian,
On 25.03.2020 12:21, m...@adrianschmutzler.de wrote:
Hi Piotr,
-Original Message-
From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
On Behalf Of Piotr Dymacz
Sent: Mittwoch, 25. März 2020 00:34
To: openwrt-devel@lists.openwrt.org
Subject: [OpenWrt-Devel
There are currently 7 variants of 'wpad' package but 'iwinfo' is
included by default only if 'wpad', 'wpad-{basic,mini}' or 'nas'
packages are included in {DEVICE,DEFAULT}_PACKAGES. Use 'wpad-*'
pattern to include 'iwinfo' with any 'wpad' variant.
Signed-off-by: Piotr Dymacz
---
include
, that it is solely a community doing the maintenance
tasks.
Acked-by: Piotr Dymacz
--
Cheers,
Piotr
Signed-off-by: Petr Štetiar
---
target/linux/apm821xx/Makefile | 2 --
target/linux/arc770/Makefile | 1 -
target/linux/archs38/Makefile| 1 -
target/linux/armvirt/Makefile| 1
Hi Petr, Rafał,
On 02.03.2020 13:58, Petr Štetiar wrote:
This reverts commit 15a0701cdde8eeae2a54880b813cdb8cdc09a384.
Seems like this patch has introduced some regressions on the ramips
target which is still on 4.14 kernel as this commit touches only 4.14
kernel patches.
jffs2: Erase at
Hi Adrian,
On 23.02.2020 20:51, m...@adrianschmutzler.de wrote:
Hi,
when defining gpio-export nodes, I'm never really sure about how the
values for "gpio-export,output" and GPIO_ACTIVE_HIGH/LOW in gpios
have to be set up correctly in relation to each other.
I also was not able to retrieve a
Hi Adrian,
On 20.02.2020 19:00, Adrian Schmutzler wrote:
-Original Message-
From: Piotr Dymacz [mailto:pep...@gmail.com]
Sent: Donnerstag, 20. Februar 2020 18:58
To: Adrian Schmutzler ; openwrt-
de...@lists.openwrt.org
Subject: Re: [OpenWrt-Devel] [PATCH 2/2] rssileds: restrict package
Hi Adrian,
On 20.02.2020 18:52, Adrian Schmutzler wrote:
It does not seem very sensible to provide the rssileds package
on targets without corresponding LEDs, so restrict it to the
targets where it is used at the moment.
This package isn't hardware related and shouldn't be limited to targets
Hi Adrian,
On 10.02.2020 12:25, Adrian Schmutzler wrote:
Hi,
while reviewing the PR for the TL-WA830REv1 [1], I was wondered about the
unusually high
spi-max-frequency = <10400>;
The author states it's running stable, the datasheet tells
Normal READ (Serial): 40-MHz clock rate
FAST_READ
Hi Chuanhong,
On 06.02.2020 17:01, Chuanhong Guo wrote:
Hi!
On Thu, Feb 6, 2020 at 11:29 PM Piotr Dymacz wrote:
Don't you think that ~24h for review this kind of patch wasn't enough?
I've sent the patch upstream and got positive review there.[0] two
minor comments there are already
Hi Chuanhong,
On 05.02.2020 15:44, Chuanhong Guo wrote:
A new shift mode was introduced since ar934x which has a way better
performance than current bitbang driver and can handle higher spi
clock properly. This commit adds a new driver to make use of this
new feature.
This new driver has
Hi Adrian,
On 04.02.2020 13:32, Adrian Schmutzler wrote:
Hi,
-Original Message-
From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
Behalf Of Piotr Dymacz
Sent: Freitag, 31. Januar 2020 15:23
To: openwrt-devel@lists.openwrt.org
Subject: [OpenWrt-Devel] [PATCH] base
Hi Daniel, Adrian,
See my comments inline.
On 02.02.2020 17:41, Daniel Golle wrote:
The Teltonika RUT955 is an industrial 2G/3G/4G WiFi router with
various additional inputs and outputs.
Specification:
- 550/400/200 MHz (CPU/DDR/AHB)
- 128 MB of RAM (DDR2)
- 16 MB of FLASH (SPI NOR)
- 4x
/openwrt/blob/master/target/linux/ath79/config-4.19#L216
https://github.com/openwrt/openwrt/blob/master/target/linux/ath79/config-4.14#L223
'make kernel_menuconfig CONFIG_TARGET=subtarget' will solve that.
Signed-off-by: Daniel Golle
Acked-by: Piotr Dymacz
--
Cheers,
Piotr
---
target/linux
Hi Adrian,
On 02.02.2020 18:20, m...@adrianschmutzler.de wrote:
Hi Piotr,
-Original Message-
From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
On Behalf Of Piotr Dymacz
Sent: Sonntag, 2. Februar 2020 18:02
To: Adrian Schmutzler ; openwrt-
de...@lists.openwrt.org
Hi Adrian,
On 02.02.2020 13:48, Adrian Schmutzler wrote:
This introduce a variable KERNEL_LZMA to replace the frequently
used sequence "kernel-bin | append-dtb | lzma", similar to the
KERNEL_DTB variable in ramips target.
So in results we will have:
ramips: KERNEL_DTB = kernel-bin |
isn't used for
indicating 'running' stage.
Signed-off-by: Piotr Dymacz
---
package/base-files/Makefile | 2 +-
package/base-files/files/etc/diag.sh | 2 ++
.../base-files/files/lib/functions/leds.sh| 27 ---
3 files changed, 26 insertions(+), 5 deletion
Hi David,
On 30.01.2020 12:36, David Bauer wrote:
Hello again,
[...]
So I'm waiting on feedback from other owners of these boards and using this
(more or less) strange fix in the meantime.
Robert complained in the meantime, that my fix broke his R6260. He also sent me
the partition map of
Hi Adrian,
On 28.01.2020 16:59, Adrian Schmutzler wrote:
Hi,
There is easy way to check GMACx <> ethX assignment order in mach-*.c
files. Just check order of ath79_register_eth() calls:
ath79_register_eth(0);
ath79_register_eth(1);
Will register GMAC0 as eth0, GMAC1 as eth1
Hi Adrian,
On 28.01.2020 16:48, Adrian Schmutzler wrote:
Hi Piotr,
-Original Message-
From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
Behalf Of Piotr Dymacz
Sent: Montag, 27. Januar 2020 21:45
To: Adrian Schmutzler
Cc: openwrt-devel@lists.openwrt.org; gch981
Hi Peter,
On 27.01.2020 22:05, Peter Geis wrote:
On Mon, Jan 27, 2020 at 4:00 PM Piotr Dymacz wrote:
[...]
But it's not a general rule and, at least in case of generic/basic
settings, user shouldn't be worried about upgrading between major
versions with preserving settings. Otherwise
Hi Peter,
On 27.01.2020 19:57, Peter Geis wrote:
On Mon, Jan 27, 2020 at 1:35 PM Adrian Schmutzler
wrote:
Just a quick one:
> > So, no matter what we do, there is no easy way forward.
>
> We could remove all ar71xx -> ath79 migration helper scripts, ar71xx
> board names from supported
Hi Adrian,
On 27.01.2020 19:35, Adrian Schmutzler wrote:
Just a quick one:
> So, no matter what we do, there is no easy way forward.
We could remove all ar71xx -> ath79 migration helper scripts, ar71xx
board names from supported devices lists in ath79 images and make the
target a brand new,
Hi Adrian,
On 21.01.2020 15:10, Adrian Schmutzler wrote:
[...]
I'm in the middle of migrating some devices from soon-to-be-obsolete
ar71xx to ath79 target and was wondering about status of the eth0/eth1
vs. LAN/WAN assignment issue.
To start with the end: I've decided to stop working on
Hi Petr,
On 20.01.2020 20:40, Petr Štetiar wrote:
Currently it's not possible to downgrade from master:
Device ubiquiti,edgerouterx not supported by this image
Supported devices: ubnt-erx
So fix it by adding a DTS based device name from master into
SUPPORTED_DEVICES list.
Signed-off-by:
Hi Adrian, David, Chuanhong,
On 07.09.2019 12:15, m...@adrianschmutzler.de wrote:
Hi,
> However, this will obviously swap eth0/eth1 on EVERY upgrade, not just
when coming from ar71xx.
> So, does anyone have an idea how to limit this to run only when updated
from ar71xx?
I was thinking about
ot;) and makes procd manage daemons for any wiphy device
found in '/sys/class/ieee80211'.
CC: Felix Fietkau
CC: Daniel Golle
Signed-off-by: Piotr Dymacz
---
package/network/services/hostapd/Makefile | 2 +-
package/network/services/hostapd/files/hostapd.hotplug | 2 +-
2 files c
Hi Adrian, Tom,
On 05.01.2020 16:57, m...@adrianschmutzler.de wrote:
-Original Message-
From: Tom Psyborg [mailto:pozega.tomis...@gmail.com]
Sent: Sonntag, 5. Januar 2020 16:33
To: m...@adrianschmutzler.de
Cc: Hauke Mehrtens ; OpenWrt Development List
; Koen Vandeputte
Subject: Re:
Hi David, Jo,
On 30.12.2019 14:22, David Bauer wrote:
Hello,
On 12/30/19 12:42 PM, Jo-Philipp Wich wrote:
Hi,
given that (binary release) support for 4MB devices will end with 19.07,
I'd vote for reverting the 4K sector change in ath79 and stick with 64K
ones as common denominator across the
On 11.12.2019 15:22, Daniel Golle wrote:
As a community, we decided to give our self a set of minimal rules[1].
And even though it is in the last position, rule #12 "Be nice to each
other." is meant just as serious as all the other rules.
So here, not for the first time, you are using language
Hi Hauke,
On 28.11.2019 19:41, Hauke Mehrtens wrote:
On 11/28/19 7:11 PM, Adrian Schmutzler wrote:
Hi Hauke,
The following are still on kernel 4.9:
* ar7
* ixp4xx
* orion
There are patches (actually from you, May 2019) on the list which claim to bump
ar7 and orion to 4.14:
Hi,
On 25.11.2019 22:28, e9hack wrote:
Hi,
this commit:
Commit: b7c58a1eeba5be2e1f77ec05b417be9d87e26916 [b7c58a1]
kernel: nf_conntrack_rtcache: fix cleanup on netns delete and rmmod
See FS#2624:
https://bugs.openwrt.org/index.php?do=details_id=2624
--
Cheers,
Piotr
floods my log every
'uqmi' was moved to 'WWAN' submenu in 9abdeee0b7.
Let's be consistent and do the same with 'umbim'.
Signed-off-by: Piotr Dymacz
---
package/network/utils/umbim/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/package/network/utils/umbim/Makefile
b/package/network/utils/umbim
24e92fc116)
Signed-off-by: Piotr Dymacz
---
target/linux/ramips/image/Makefile| 11 +---
target/linux/ramips/image/mt7621.mk | 2 +-
target/linux/ramips/image/rt3883.mk | 2 +-
target/linux/ramips/mt7620/config-4.14| 4 +-
target/linux/ramips/mt7621/c
de duplication and limit
copy mistakes in future. I don't think this is the first time we
change manufacturer partition naming scheme.
So:
Acked-by: Piotr Dymacz
--
Cheers,
Piotr
Best wishes
David
Signed-off-by: Adrian Schmutzler
---
.../linux/ath79/dts/ar9342_ubnt_lap-12
1 - 100 of 216 matches
Mail list logo
