Re: ui.waitReconnect() may load over HTTP instead of HTTPS
Hi, ui.awaitReconnect() tries both http:// and https:// access simultaneously and redirects to whatever URL loads successfully. HTTPS access might be unavailable, e.g. when flashing an image without SSL support built in. This used to be the norm before OpenWrt enabled HTTPS by default in 22.03. So this probing of an http:// URL from within a page that was loaded via https:// is intentional. ~ Jo signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH] octeontx: add sqaushfs and ramdisk to features
Add squashfs and ramdisk to features as these are commonly used images for the octeontx. Signed-off-by: Tim Harvey --- target/linux/octeontx/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/octeontx/Makefile b/target/linux/octeontx/Makefile index 9b29e567589e..50c5cd6d217d 100644 --- a/target/linux/octeontx/Makefile +++ b/target/linux/octeontx/Makefile @@ -7,7 +7,7 @@ include $(TOPDIR)/rules.mk ARCH:=aarch64 BOARD:=octeontx BOARDNAME:=Octeon-TX -FEATURES:=targz pcie gpio rtc usb fpu +FEATURES:=squashfs ramdisk targz pcie gpio rtc usb fpu SUBTARGETS:=generic KERNEL_PATCHVER:=5.10 -- 2.25.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Updating env/kernel-config after rebasing/kernel version bump
> On Dec 28, 2022, at 1:14 PM, Robert Marko wrote:
>
> On Wed, 28 Dec 2022 at 01:01, Philip Prindeville
> wrote:
>>
>>
>>
>>> On Dec 27, 2022, at 4:50 PM, Robert Marko wrote:
>>>
>>> On Wed, 28 Dec 2022 at 00:48, Philip Prindeville
>>> wrote:
Hi,
I originally set up my env/kernel-config a long time ago (like 2018) by
hand, and since then the kernel has gone through several bumps. How do I
easily refresh it to pick up new stuff from
target/linux/x86/64/config-${KVER} (where KVER=5.15 currently)? Is there
a handy script or make target to do this?
>>>
>>> There is make kernel_menuconfig that will essentially give you the
>>> kernel menuconfig and refresh the config after saving.
>>
>>
>> Right, but what does that involve? Will it pick up new symbols from the new
>> kernel target? If there's a new default in 5.15 that wasn't in 5.10, how
>> does it find its way into my config?
>>
>> I tried diffing target/linux/x86/64/config-5.15 and env/kernel-config and
>> there's a whole lot of changes.
>>
>> Or is env/kernel-config the delta from the defaults for any given kernel
>> version in config-${KVER}?
>
> I have to admit that I have not used the env script so far, so I dont
> know how it works.
>
> Regards,
> Robert
I'd like to see something like scripts/diffconfig.sh done for the kernel-config
...
How are the files in target/linux/ combined to generate default state in the
absence of kernel-config, anyway?
Thanks
>>
>>
>>>
>>> Regards,
>>> Robert
Thanks,
-Philip
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Updating env/kernel-config after rebasing/kernel version bump
On Wed, 28 Dec 2022 at 01:01, Philip Prindeville
wrote:
>
>
>
> > On Dec 27, 2022, at 4:50 PM, Robert Marko wrote:
> >
> > On Wed, 28 Dec 2022 at 00:48, Philip Prindeville
> > wrote:
> >>
> >> Hi,
> >>
> >> I originally set up my env/kernel-config a long time ago (like 2018) by
> >> hand, and since then the kernel has gone through several bumps. How do I
> >> easily refresh it to pick up new stuff from
> >> target/linux/x86/64/config-${KVER} (where KVER=5.15 currently)? Is there
> >> a handy script or make target to do this?
> >
> > There is make kernel_menuconfig that will essentially give you the
> > kernel menuconfig and refresh the config after saving.
>
>
> Right, but what does that involve? Will it pick up new symbols from the new
> kernel target? If there's a new default in 5.15 that wasn't in 5.10, how
> does it find its way into my config?
>
> I tried diffing target/linux/x86/64/config-5.15 and env/kernel-config and
> there's a whole lot of changes.
>
> Or is env/kernel-config the delta from the defaults for any given kernel
> version in config-${KVER}?
I have to admit that I have not used the env script so far, so I dont
know how it works.
Regards,
Robert
>
>
> >
> > Regards,
> > Robert
> >>
> >> Thanks,
> >>
> >> -Philip
> >>
> >>
> >> ___
> >> openwrt-devel mailing list
> >> openwrt-devel@lists.openwrt.org
> >> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH v2 2/2] ramips: mt7621-dts: we420223-99: mux phy0->gmac1
This gives each port an individual link to the CPU, like in f1c9afd801 (ramips: mt7621-dts: mux phy0/4 to gmac1, 2022-07-06). The advantage of this is that it can now route packets faster between the ports (before the CPU only had a single 1Gb link to the switch that has to be shared between both ports. Another advantage is that in Linux 5.10 you can now bridge a VLAN to a non-vlan port. Without this patch, you're not getting any data across the bridge. That is fixed in Linux 5.15 but is still handled by the CPU in any case. So therefore this patch is advantageous in all cases except for when you need the device as a simple switch without VLANs. For that case it's better to revert this and the switch hardware will forward traffic without bothering the CPU. Signed-off-by: Harm Berntsen You don't need to split this to another patch. Arınç ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH 1/2] ramips: mt7621: Add Arcadyan WE420223-99 support
The Arcadyan WE420223-99 is a WiFi AC simultaneous dual-band access
point distributed as Experia WiFi by KPN in the Netherlands. It features
two ethernet ports and 2 internal antennas.
Specifications
--
SOC : Mediatek MT7621AT
ETH : Two 1 gigabit ports, built into the SOC
WIFI : MT7615DN
BUTTON: Reset
BUTTON: WPS
LED : Power (green+red)
LED : WiFi (green+blue)
LED : WPS (green+red)
LED : Followme (green+red)
Power : 12 VDC, 1A barrel plug
Winbond variant:
RAM : Winbond W631GG6MB12J, 1GBIT DDR3 SDRAM
Flash : Winbond W25Q256JVFQ, 256Mb SPI
U-Boot: 1.1.3 (Nov 23 2017 - 16:40:17), Ralink 5.0.0.1
Macronix variant:
RAM : Nanya NT5CC64M16GP-DI, 1GBIT DDR3 SDRAM
Flash : MX25l25635FMI-10G, 256Mb SPI
U-Boot: 1.1.3 (Dec 4 2017 - 11:37:57), Ralink 5.0.0.1
Serial
--
The serial port needs a TTL/RS-232 3V3 level converter! The Serial
setting is 57600-8-N-1. The board has an unpopulated 2.54mm straight pin
header.
The pinout is: VCC (the square), RX, TX, GND.
Installation
1. Open the device, take off the heat sink
2. Connect the SPI flash chip to a flasher, e.g. a Raspberry Pi. Also
connect the RESET pin for stability (thanks @FPSUsername for reporting)
3. Make a backup in case you want to revert to stock later
4. Flash the squashfs-factory.trx file to offset 0x5 of the flash
5. Ensure the bootpartition variable is set to 0 in the U-Boot
environment located at 0x3
Note that the U-Boot is password protected, this can optionally be
removed. See the forum for more details [1]
MAC Addresses(stock)
+--+--+---+
| use | address | example |
+--+--+---+
| Device | label| 00:00:00:11:00:00 |
| Ethernet | + 3 | 00:00:00:11:00:03 |
| 2g | + 0x02f1 | 02:00:00:01:00:01 |
| 5g | + 1 | 00:00:00:11:00:01 |
+--+--+---+
The label address is stored in ASCII in the board_data partition
Known issues
- 2g MAC address does not match stock due to missing support for that in
macaddr_add
- Only the power LED is configured by default
References
--
[1]
https://forum.openwrt.org/t/adding-openwrt-support-for-arcadyan-we420223-99-kpn-experia-wifi/132653?u=harm
Signed-off-by: Harm Berntsen
---
package/boot/uboot-envtools/files/ramips | 3 +
.../dts/mt7621_arcadyan_we420223-99.dts | 210 ++
target/linux/ramips/image/mt7621.mk | 25 +++
.../mt7621/base-files/etc/board.d/02_network | 8 +
.../etc/hotplug.d/ieee80211/10_fix_wifi_mac | 9 +
.../mt7621/base-files/lib/upgrade/platform.sh | 1 +
6 files changed, 256 insertions(+)
create mode 100644 target/linux/ramips/dts/mt7621_arcadyan_we420223-99.dts
diff --git a/package/boot/uboot-envtools/files/ramips
b/package/boot/uboot-envtools/files/ramips
index f7f4821cef..8d4960e7a3 100644
--- a/package/boot/uboot-envtools/files/ramips
+++ b/package/boot/uboot-envtools/files/ramips
@@ -17,6 +17,9 @@ alfa-network,awusfree1|\
alfa-network,quad-e4g|\
alfa-network,r36m-e4g|\
alfa-network,tube-e4g|\
+arcadyan,we420223-99)
+ ubootenv_add_uci_config "/dev/mtd2" "0x0" "0x1000" "0x1000"
+ ;;
engenius,esr600h|\
sitecom,wlr-4100-v1-002)
ubootenv_add_uci_config "/dev/mtd1" "0x0" "0x1000" "0x1000"
diff --git a/target/linux/ramips/dts/mt7621_arcadyan_we420223-99.dts
b/target/linux/ramips/dts/mt7621_arcadyan_we420223-99.dts
new file mode 100644
index 00..f68d79af15
--- /dev/null
+++ b/target/linux/ramips/dts/mt7621_arcadyan_we420223-99.dts
@@ -0,0 +1,210 @@
+// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
+
+#include "mt7621.dtsi"
+
+#include
+#include
+#include
+
+/ {
+ model = "Arcadyan WE420223-99";
+ compatible = "arcadyan,we420223-99", "mediatek,mt7621-soc";
+
+ aliases {
+ led-boot = _power_green;
+ led-failsafe = _power_red;
+ led-running = _power_green;
+ led-upgrade = _wps_green;
+ led-wifi = _wifi_green;
+ };
+
+ chosen {
+ bootargs = "console=ttyS0,57600 ubi.mtd=5
root=/dev/ubiblock0_0";
+ };
+
+ keys {
+ compatible = "gpio-keys";
+
+ reset {
+ label = "reset";
+ gpios = < 3 GPIO_ACTIVE_LOW>;
+ linux,code = ;
+ };
+
+ wps {
+ label = "wps";
+ gpios = < 18 GPIO_ACTIVE_LOW>;
+ linux,code = ;
+ };
+ };
+
+ leds {
+ compatible = "gpio-leds";
+
+ led_power_green: power_green {
+ label = "green:power";
+ gpios = < 42 GPIO_ACTIVE_LOW>;
+ color = ;
+ function =
ui.waitReconnect() may load over HTTP instead of HTTPS
I see this warning in Firefox (OpenWrt 22.03):
Loading mixed (insecure) display content
“http://192.168.113.1/luci-static/resources/icons/loading.gif?0.046104145623280135”
on a secure page
This happens when the sysupgrade dialog is processing on an https luci. It
doesn't cause any real harm, but it would be good to fix.
The problem is that pingDevice falls back to http only when no protocol
is specified:
pingDevice: function(proto, ipaddr) {
var target = '%s://%s%s?%s'.format(proto || 'http', ipaddr ||
window.location.host, L.resource('icons/loading.gif'), Math.random());
For some of the calls to ui.awaitReconnect, window.location.protocol could be
prefixed, but I think pingDevice is the correct place for a fix.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH 1/2] ramips: mt7621: Add Arcadyan WE420223-99 support
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 --- On Wed, 2022-12-28 at 00:11 +0100, Rafał Miłecki wrote: > On 15.08.2022 12:30, Harm Berntsen 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 > > automatically by the mailing list software. > > (...) > > > 5. Ensure the bootpartition variable is set to 0 in the U-Boot > > environment located at 0x3 > > There should be really a Linux parser picking the correct set of > partitions. Such limitations make behaviour too much unpredictable if > not making it possible to brick a device. Thanks for your feedback! The fw_setenv tool from U-Boot can parse this format. My patch includes a uboot-envtools addition to make this change easy to do from OpenWrt initramfs. On the Wiki I also described the flashing process using a Raspberry Pi [1], also using fw_setenv. Although the bootloader supports A/B partitioning, my patch reduces to a single big A setup (for more storage space), so the only valid setting is bootpartition=0. Note that bootpartition=1 can be made to work, that would require changing the partition layout in the .dts and kernel boot parameters. I think there is little risk in bricking as the steps currently require you to directly connect to the flash chip. Once you can do that, creating/restoring back-ups is trivial. [1] https://openwrt.org/inbox/toh/arcadyan/astoria/we420223-99#flashing_openwrt --- End Message --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
