o-authored-by: David Bauer
Signed-off-by: Jan-Niklas Burfeind
(cherry picked from commit c7d3bbb909bdcccd4f26f18b18cc1cb00500a874)
---
.../base-files/files/lib/functions/system.sh | 8 ++
.../armv8/base-files/etc/board.d/02_network | 13 ++
.../sunxi/base-files/etc/board.d/02_netw
his method has been proven to work fine for a64, let's just
change the default u-boot env file to do the same.
Fixes: #10080
Fixes: e6d9f6fdff ("sunxi: add support for FriendlyARM NanoPi R1")
Co-authored-by: Karl Palsson
Signed-off-by: Jan-Niklas Burfeind
[use UUID in default u-boot
hw_mac_addr="$(mtd_get_mac_binary factory 0x4)"
+ [ "$PHYNBR" = "0" ] && \
+ macaddr_add $hw_mac_addr 1 > /sys${DEVPATH}/macaddress
+ [ "
device
fixes #7757 (and FS#2987)
Signed-off-by: Florian Maurer
(cherry picked from commit 0820d620123a03b6db6642acb6e950d22ffb030f)
Signed-off-by: Jan-Niklas Burfeind
---
target/linux/lantiq/xrx200/base-files/etc/board.d/01_leds | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff
in both the stable and the testing kernel
h2+/h3/h5 devices have a Secure ID that can be read from
`/sys/bus/nvmem/devices/sunxi-sid0/nvmem`.
Enabling CONFIG_NVMEM_SYSFS grants sysfs access from userspace.
Signed-off-by: Jan-Niklas Burfeind
---
Hauke suggested enabling it for the whole sunxi
o-authored-by: David Bauer
Signed-off-by: Jan-Niklas Burfeind
---
.../base-files/files/lib/functions/system.sh | 8 ++
.../armv8/base-files/etc/board.d/02_network | 13 ++
.../sunxi/base-files/etc/board.d/02_network | 25 +++
3 files changed, 35 insertions(+), 11
o-authored-by: David Bauer
Signed-off-by: Jan-Niklas Burfeind
---
.../sunxi/base-files/etc/board.d/02_network | 34 +++
1 file changed, 34 insertions(+)
diff --git a/target/linux/sunxi/base-files/etc/board.d/02_network
b/target/linux/sunxi/base-files/etc/board.d/02_network
index
for the NanoPi R1 instead of the hardcoded `mmcblk0p2` to support its
multiple mmcs.
Fixes: e6d9f6fdff ("sunxi: add support for FriendlyARM NanoPi R1")
Co-authored-by: Karl Palsson
Signed-off-by: Jan-Niklas Burfeind
---
package/boot/uboot-sunxi/Makefile| 1 +
package/boot/u
On 12/15/22 15:18, Jan-Niklas Burfeind wrote:
instead of the hardcoded `mmcblk0p2` to support devices with multiple
mmcs, like the NanoPi R1.
Fixes: e6d9f6fdff ("sunxi: add support for FriendlyARM NanoPi R1")
Signed-off-by: Jan-Niklas Burfeind
---
Good afternoon.
I just had a
instead of the hardcoded `mmcblk0p2` to support devices with multiple
mmcs, like the NanoPi R1.
Fixes: e6d9f6fdff ("sunxi: add support for FriendlyARM NanoPi R1")
Signed-off-by: Jan-Niklas Burfeind
---
Good afternoon.
I just had a discussion with karlp in openwrt-devel, where we ta
The frequency appears as unlisted initial frequency.
Removed it as Hauke suggested.
Signed-off-by: Jan-Niklas Burfeind
---
This resolves part of the problem in #11104 on GitHub [1].
The "Waiting for root device /dev/mmcblk0p2..."-issue still remains and
leaves the device unbootable
context_type is an integer mapping of pdptype:
1: IPV4
2: IPV6
3: IPV4V6
Signed-off-by: Jan-Niklas Burfeind
(cherry picked from commit 13f82ce264ed2d02c66cb2cae8f013c8f64a979f)
---
I sent the patch a few hours eatlier, but missed the development list.
Commit-ID changed as I wrongly changed
-off-by: Jan-Niklas Burfeind
Acked-by: Arınç ÜNAL
(cherry picked from commit dce66899bf243d78689afcc693340b891bbf4c2d)
---
.../dts/mt7621_wavlink_ws-wn572hp3-4g.dts | 184 ++
target/linux/ramips/image/mt7621.mk | 17 ++
.../mt7621/base-files/etc/board.d/02_network
On 12/5/22 00:02, Jan-Niklas Burfeind wrote:
On 12/4/22 20:45, Sander Vanheule wrote:
Hi Jan-Niklas,
On Fri, 2022-12-02 at 14:55 +0100, Jan-Niklas Burfeind wrote:
add three missing LEDs
- PoE-Max
- Link/Act
- PoE
Do the latter two LEDs indicate which LED mode is currently selected
On 12/4/22 20:45, Sander Vanheule wrote:
Hi Jan-Niklas,
On Fri, 2022-12-02 at 14:55 +0100, Jan-Niklas Burfeind wrote:
add three missing LEDs
- PoE-Max
- Link/Act
- PoE
Do the latter two LEDs indicate which LED mode is currently selected (on stock
FW)? Users can do with these LEDs what
add three missing LEDs
- PoE-Max
- Link/Act
- PoE
add two missing buttons
- mode
- reset
The last was dropped in
commit 61a3d0075b15 ("realtek: update GPIO bindings in the dts files in
dts-5.10")
Signed-off-by: Jan-Niklas Burfeind
---
Hello everyone,
I just tested the mi
On 12/1/22 09:25, Arınç ÜNAL wrote:
On 30.11.2022 23:35, Jan-Niklas Burfeind wrote:
Wavlink WS-WN572HP3 4G is an 802.11ac
dual-band outdoor router with LTE support.
Specifications;
* Soc: MT7621DAT
* RAM: 128MiB
* Flash: NOR 16MiB GD-25Q128ESIG3
* Wi-Fi:
* MT7613BEN: 5GHz
* MT7603EN
context_type is an integer mapping of pdptype:
1: IPV4
2: IPV6
3: IPV4V6
Signed-off-by: Jan-Niklas Burfeind
---
package/network/utils/comgt/files/ncm.json | 16
package/network/utils/comgt/files/ncm.sh | 6 ++
2 files changed, 22 insertions(+)
diff --git a/package
-off-by: Jan-Niklas Burfeind
---
Huge thanks to Znevna, he suggested using gpio adresses modulo banksize.
No clue where the system get's the info that bank three is the
"LED-gpio-bank" but it works.
Other than that I added the missing label-mac-alias to the 5GHz wifi
device.
Thanks agai
On 11/30/22 19:54, Jan-Niklas Burfeind wrote:
On 11/30/22 18:27, Arınç ÜNAL wrote:
On 30.11.2022 19:44, Jan-Niklas Burfeind wrote:
Wavlink WS-WN572HP3 4G is an 802.11ac
dual-band outdoor router with LTE support.
Specifications;
* Soc: MT7621DAT
* RAM: 128MiB
* Flash: NOR 16MiB GD
On 11/30/22 18:27, Arınç ÜNAL wrote:
On 30.11.2022 19:44, Jan-Niklas Burfeind wrote:
Wavlink WS-WN572HP3 4G is an 802.11ac
dual-band outdoor router with LTE support.
Specifications;
* Soc: MT7621DAT
* RAM: 128MiB
* Flash: NOR 16MiB GD-25Q128ESIG3
* Wi-Fi:
* MT7613BEN: 5GHz
* MT7603EN
s-2 made me aware of an LED rssi issue; this is not ready to merge yet.
On 11/30/22 17:44, Jan-Niklas Burfeind wrote:
Wavlink WS-WN572HP3 4G is an 802.11ac
dual-band outdoor router with LTE support.
Specifications;
* Soc: MT7621DAT
* RAM: 128MiB
* Flash: NOR 16MiB GD-25Q128ESIG3
* Wi-Fi
context_type is an integer mapping of pdptype:
1: IPV4
2: IPV6
3: IPV4V6
Signed-off-by: Jan-Niklas Burfeind
---
package/network/utils/comgt/files/ncm.json | 16
package/network/utils/comgt/files/ncm.sh | 6 ++
2 files changed, 22 insertions(+)
diff --git a/package
-off-by: Jan-Niklas Burfeind
---
.../dts/mt7621_wavlink_ws-wn572hp3-4g.dts | 183 ++
target/linux/ramips/image/mt7621.mk | 17 ++
.../mt7621/base-files/etc/board.d/02_network | 1 +
3 files changed, 201 insertions(+)
create mode 100644 target/linux/ramips/dts
On 11/30/22 10:41, Arınç ÜNAL wrote:
On 30.11.2022 12:33, Jan-Niklas Burfeind wrote:
Wavlink WS-WN572HP3 4G is an 802.11ac
dual-band outdoor router with LTE support.
Specifications;
* Soc: MT7621DAT
* RAM: 128MiB
* Flash: NOR 16MiB GD-25Q128ESIG3
* Wi-Fi:
* MT7613BEN: 5GHz
* MT7603EN
-off-by: Jan-Niklas Burfeind
---
.../dts/mt7621_wavlink_ws-wn572hp3-4g.dts | 183 ++
target/linux/ramips/image/mt7621.mk | 17 ++
.../mt7621/base-files/etc/board.d/02_network | 1 +
3 files changed, 201 insertions(+)
create mode 100644 target/linux/ramips/dts
context_type is an integer mapping of pdptype:
1: IPV4
2: IPV6
3: IPV4V6
Signed-off-by: Jan-Niklas Burfeind
---
package/network/utils/comgt/files/ncm.json | 16
package/network/utils/comgt/files/ncm.sh | 6 ++
2 files changed, 22 insertions(+)
diff --git a/package
-off-by: Jan-Niklas Burfeind
---
.../dts/mt7621_wavlink_ws-wn572hp3-4g.dts | 186 ++
target/linux/ramips/image/mt7621.mk | 17 ++
2 files changed, 203 insertions(+)
create mode 100644 target/linux/ramips/dts/mt7621_wavlink_ws-wn572hp3-4g.dts
diff --git a/target/linux
context_type is an integer mapping of pdptype:
1: IPV4
2: IPV6
3: IPV4V6
Signed-off-by: Jan-Niklas Burfeind
---
package/network/utils/comgt/files/ncm.json | 16
package/network/utils/comgt/files/ncm.sh | 6 ++
2 files changed, 22 insertions(+)
diff --git a/package
should be add/delete or abbreviated add/del
Signed-off-by: Jan-Niklas Burfeind
---
.../realtek/files-5.10/drivers/net/dsa/rtl83xx/common.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/target/linux/realtek/files-5.10/drivers/net/dsa/rtl83xx/common.c
b/target
extract the compatible and model to make room for other variants
follow-up of
commit dc23df8a8ca7 ("ath79: change Ubiquiti UniFi AP model name to include
"AP"")
Signed-off-by: Jan-Niklas Burfeind
---
target/linux/ath79/dts/ar7241_ubnt_unifi-
The hardware difference is the antenna which has a higher gain compared
to the original UniFi AP.
The variant was supported before in ar71xx.
Signed-off-by: Jan-Niklas Burfeind
---
target/linux/ath79/dts/ar7241_ubnt_unifi-ap-lr.dts | 8
target/linux/ath79/image/generic-ubnt.mk
d the firmware image file via TFTP:
tftp 192.168.1.20
tftp> bin
tftp> trace
Packet tracing on.
tftp> put firmware_image.bin
Signed-off-by: Jan-Niklas Burfeind
---
Sorry for messing up the versioning earlier,
this is v3 not v2.
.../ath79/dts/ar9342_ubnt_nanobeam-m5.dts | 26
The dmesg output you asked for is attached.
Thanks
Jan-Niklas
On 4/21/22 08:34, Jan-Niklas Burfeind wrote:
Ubiquiti NanoBeam M5 devices are CPE equipment for customer locations
with one Ethernet port and a 5 GHz 300Mbps wireless interface.
Specificatons:
- Atheros AR9342
- 535 MHz CPU
- 64
d the firmware image file via TFTP:
tftp 192.168.1.20
tftp> bin
tftp> trace
Packet tracing on.
tftp> put firmware_image.bin
Signed-off-by: Jan-Niklas Burfeind
---
.../ath79/dts/ar9342_ubnt_nanobeam-m5.dts | 26 +++
target/linux/ath79/image/generic-ubnt.mk |
uot;cell_id",res.data.wcdma_system_info_v2.cid%65536);
Henrik
Den mån 14 mars 2022 kl 17:00 skrev Jan-Niklas Burfeind :
Hey everyone,
I attached the current output of my patched uqmi.
Please let me know if you think the arrays should be named differently
or if you spot an error.
Thanks and
Hey everyone,
I attached the current output of my patched uqmi.
Please let me know if you think the arrays should be named differently
or if you spot an error.
Thanks and have a nice day
Aiyion
On 3/8/22 16:01, Jan-Niklas Burfeind wrote:
Output the cells from --get-cell-location-info
Output the cells from --get-cell-location-info in an array "cells",
"geran" entries as an array called alike,
and wrap output for different "frequencies" as such.
Reported-by: Cezary Jackiewicz
Suggested-by: Oskari Lemmelä
Signed-off-by: Jan-Niklas Burfeind
---
Correct order of rsrp and rsrq parameters for print_lte_info.
Signed-off-by: Jan-Niklas Burfeind
---
commands-nas.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/commands-nas.c b/commands-nas.c
index 01ca3b8..275c53f 100644
--- a/commands-nas.c
+++ b/commands-nas.c
.
Jan-Niklas
On 3/7/22 18:59, Oskari Lemmelä wrote:
Hi Jan-Niklas,
On 7.3.2022 14.14, Jan-Niklas Burfeind wrote:
Output the cells from --get-cell-location-info in an array "cells".
Signed-off-by: Jan-Niklas Burfeind
---
Hey Oskari,
I think you original author would be you?
Have y
regarding json as well.
Thanks
Jan-Niklas
On 3/7/22 18:10, Oskari Lemmelä wrote:
Hi Jan-Niklas,
On 7.3.2022 14.14, Jan-Niklas Burfeind wrote:
Correct order of rsrp and rsrq parameters for print_lte_info.
Good catch. I didn’t check those similar variable names carefully enough.
I think my typo
{
"physical_cell_id": 43,
"rsrq": -19.10,
"rsrp": -109.90,
"rssi": -81.700000
}
]
}
}
Let me know if thi
Disclaimer: This particular commit compiled, but has not been tested yet.
On 3/7/22 13:14, Jan-Niklas Burfeind wrote:
Output the cells from --get-cell-location-info in an array "cells".
Signed-off-by: Jan-Niklas Burfeind
---
Hey Oskari,
I think you original author would be you?
Ha
Output the cells from --get-cell-location-info in an array "cells".
Signed-off-by: Jan-Niklas Burfeind
---
Hey Oskari,
I think you original author would be you?
Have you got any suggestions how to name the cells array, or whether there's a
cleaner way to fix the json output thats mo
Correct order of rsrp and rsrq parameters for print_lte_info.
Signed-off-by: Jan-Niklas Burfeind
---
commands-nas.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/commands-nas.c b/commands-nas.c
index 01ca3b8..ff7a6c3 100644
--- a/commands-nas.c
+++ b/commands-nas.c
, that
might produce similar problems.
Without breaking existing codes, it might be worthwile to ask the
original author about his intention on this.
Until later
Aiyion
On 3/6/22 18:37, Cezary Jackiewicz wrote:
Dnia 2022-03-06, o godz. 18:25:57
Jan-Niklas Burfeind napisał(a):
Correct order
Correct order of rsrp and rsrq parameters for print_lte_info.
Signed-off-by: Jan-Niklas Burfeind
---
This was introduced in
d647f8d89f68 uqmi: add more diagnostics commands
Currently --get-cell-location-info prints the rsrq and rsrp values
swapped.
I ignored the checkpatch.pl warning for line
Tested-by: Jan-Niklas Burfeind
This has been running on at least 80 devices in the past months in our
ff-community.
Let me know if and what you need more
Aiyion
On 9/15/21 03:09, Leonardo Mörlein wrote:
When the uci configuration is created automatically during a very early
stage, where
Hello ynezz,
[1] says you are reviewing this?
It might be outdated? It's been three and a half months now; any chance
one could help you with this?
Thanks so far
Aiyion
On 1/24/22 11:43, Aiyion.Prime wrote:
Hey ynezz,
I tried to bump this in #openwrt-devel yesterday; as your last
concludes:
commit e7bc8984d9ca ("scripts: make eva_ramboot.py offset configurable")
Signed-off-by: Jan-Niklas Burfeind
---
scripts/flashing/eva_ramboot.py | 1 -
1 file changed, 1 deletion(-)
diff --git a/scripts/flashing/eva_ramboot.py b/scripts/flashing/eva_ramboot.py
index
;)
Partly reverts:
commit fc553c7e4c8e ("ath79: drop unused/incomplete dts")
Signed-off-by: Jan-Niklas Burfeind
---
I adressed Adrians comments on v3 and built and deployed the image.
Everything seems to work as well as before.
Thanks!
Aiyion
target/linux/ath79/dts/ar9331_o
On 8/22/21 2:18 PM, Adrian Schmutzler wrote:
> It's common practice at the moment to put a separate block for defining the
> MAC addresses at the end of the file.
> Please do so, just look at any other DTS file in recent master.
I was under the impression that the separate block was part of a
On 8/14/21 7:08 PM, Lech Perczak wrote:
> [...]
>>>
>>> The six bytes at 001fd00 spell OMEGA.
>> Is this the only data in 0x1-0x2? What's in 0x1-0x11000?
>>
> + read-only;
> + compatible = "nvmem-cells";
> + #address-cells =
On 8/14/21 5:43 PM, Tomasz Maciej Nowak wrote:
> [..]
>> uboot knows it is 64KiB, printenv yields uboot_size=0x1
>
> That should be reflected in partitions list and the space between
> 0x1-0x2 partition name should reflect what's inside. If the
> vendor firmware had a name for this
Hey there; answer is inline too.
Thanks for picking this up!
On 8/14/21 3:54 PM, Tomasz Maciej Nowak wrote:
> Hi,
> one comment inline.
>
> W dniu 14.08.2021 o 14:33, Jan-Niklas Burfeind pisze:
>> [...]
>> +partitions {
>> +
;)
Partly reverts:
commit fc553c7e4c8e ("ath79: drop unused/incomplete dts")
Signed-off-by: Jan-Niklas Burfeind
---
kmod-usb-chipidea2 is now included as well as tested; usb devices are
now recognized.
I added the usb vbus section, like the pisen wmm003n has it and verified
the gpio l
;)
Partly reverts:
commit fc553c7e4c8e ("ath79: drop unused/incomplete dts")
Signed-off-by: Jan-Niklas Burfeind
---
Hello David,
thanks for the review.
I think I got both you as well as Sebastians suggestion patched.
This revision contains them both, compiled without errors this morn
;)
Partly reverts:
commit fc553c7e4c8e ("ath79: drop unused/incomplete dts")
Signed-off-by: Jan-Niklas Burfeind
---
target/linux/ath79/dts/ar9331_onion_omega.dts | 138 ++
.../generic/base-files/etc/board.d/02_network | 1 +
target/linux/ath79/image/generic.mk
58 matches
Mail list logo
