[OpenWrt-Devel] OpenWrt on RISC-V
Hi all, I'm happy to announce a port of RISC-V for OpenWrt. For those who haven't heard about it, RISC-V is a new CPU architecture coming from Berkeley, and is a free, open, extensible ISA, maintained by a non-profit foundation, included in the Linux kernel since 4.15. Current status is: - based on 4.19 - pull requests and patches for trunk will be sent once support for 4.19 is merged into mainline and core package changes are worked out. Until then, the port is in a staging tree [1] - mainline musl support is expected for musl 1.21, patches are included in the tree [2] for the current 1.20 for testing - currently builds with glibc as default - OpenWrt packages are built regularly on an external buildbot - documentation is added to the wiki [3] Currently you have three ways to run RISC-V: - Virtex7-based FPGA implementation of the core (most expensive) - HiFive Unleashed (official Linux devboard, less expensive) [4] - QEMU (free, support for riscv merged into qemu-2.12) [5] The target supports the last two. There are further development boards expected in the next few months. For further reading on the architecture and its state, please refer to this site [6]. The staging tree includes various fixes for the core package changes appeared with 4.19. Given the state of 4.19 currently, please consider this an experimental port - you won't be able to run quake on it yet, sorry. [7] [1] https://git.openwrt.org/?p=openwrt/staging/wigyori.git;a=shortlog;h=refs/heads/riscv-201810 [2] https://git.openwrt.org/?p=openwrt/staging/wigyori.git;a=commit;h=f5fe060b9ccc7d64d3b1764852b6e2b9273d5cad [3] https://openwrt.org/docs/techref/hardware/soc/soc.sifive [4] https://openwrt.org/toh/hifive/unleashed [5] https://openwrt.org/docs/guide-user/virtualization/qemu#openwrt_in_qemu_risc-v [6] https://riscv.org/ [7] https://archive.fosdem.org/2018/schedule/event/riscv/ Regards, Zoltan Herpai ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] TP-Link Archer C20 v4 and MediaTek MT7628AN and MT7610E
Hello folks I have been trying to make TP-Link Archer C20 v4 to work with OpenWrt. It has already a build however both 2.4Ghz and 5Ghz wifi don't work properly at present. For the 2.4 Ghz although it has support it is very unstable and unusable as for the MT76 driver used. Has anyone used a different wifi driver ? I have seen some Githubs with MT7628AN stuff. Is it somehow different and more stable than MT76 ? For the MT7610E it is said there is not open-source driver available, but I have also seen some Githubs with it [1]. Has MediaTek opened its code already ? It it stable or usable ? If so can it be added to the snapshot ? I believe this is the main Forum Thread for this router [2], but there is no extra information other than some people seem to have made MT7610E to work but not with much details about stability. Thanks Fernando [1] - https://github.com/presisco/openwrt-mt7610e [1] - https://github.com/mqmaker/witi-openwrt/tree/master/package/ramips/drivers/mt7610e [2] - https://forum.openwrt.org/t/tp-link-archer-c20-v4-build/8945 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Custom cases for Netgear r7800?
On 02/11/18 21:20, Ben Greear wrote: This is a bit off topic, but I'm curious if anyone has developed or knows of someone selling customized cases for the Netgear r7800 (or similar AP with similar radios and 128+MB of storage and 512+MB of RAM). In particular, I'd like to get access to the serial port in a nice way, and probably have either more generic branding or maybe my own custom branding. Thanks, Ben I can't help with custom cases, but I can share how I make easy serial access port on my devices. I use an audio jack. Female panel-mounted audio jack on the device, and male jack on the USB-TTL dongle. You need to know how you soldered the cables as they need to match electrically (duh!). If you don't have a drill to make a decent hole in the case you can just use the soldering iron as a drill and some pliers to remove the blob of plastic. Do it outside of the house of course. After the second or third time the job is pretty clean and unconspicuous, it does not look like a mod. -Alberto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ramips: fix leds on GL.iNet GL-MT300N-V2
Hi hexa, thanks for your patch. Best, lynxis pgp1unm40nrM4.pgp Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Custom cases for Netgear r7800?
This is a bit off topic, but I'm curious if anyone has developed or knows of someone selling customized cases for the Netgear r7800 (or similar AP with similar radios and 128+MB of storage and 512+MB of RAM). In particular, I'd like to get access to the serial port in a nice way, and probably have either more generic branding or maybe my own custom branding. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] ramips: fix leds on GL.iNet GL-MT300N-V2
From: Martin Weinelt
The WAN LED now shows the link state. It's color is green,
not blue.
Use the physical radio for the WiFi-LED to be resilient
against changing interface names
Signed-off-by: Martin Weinelt
---
target/linux/ramips/base-files/etc/board.d/01_leds | 3 ++-
target/linux/ramips/dts/GL-MT300N-V2.dts | 2 +-
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/target/linux/ramips/base-files/etc/board.d/01_leds
b/target/linux/ramips/base-files/etc/board.d/01_leds
index 5f5e5630fd..6a1729f34d 100755
--- a/target/linux/ramips/base-files/etc/board.d/01_leds
+++ b/target/linux/ramips/base-files/etc/board.d/01_leds
@@ -149,7 +149,8 @@ gl-mt750)
set_wifi_led "$boardname:wlan"
;;
gl-mt300n-v2)
- set_wifi_led "$boardname:red:wlan"
+ ucidef_set_led_switch "wan" "wan" "$boardname:green:wan" "switch0" "0x1"
+ ucidef_set_led_switch "wlan2g" "wlan2g" "$boardname:red:wlan" "phy0tpt"
;;
hc5661|\
hc5661a)
diff --git a/target/linux/ramips/dts/GL-MT300N-V2.dts
b/target/linux/ramips/dts/GL-MT300N-V2.dts
index 48c43baeff..ba5a595b10 100644
--- a/target/linux/ramips/dts/GL-MT300N-V2.dts
+++ b/target/linux/ramips/dts/GL-MT300N-V2.dts
@@ -35,7 +35,7 @@
};
wan {
- label = "gl-mt300n-v2:blue:wan";
+ label = "gl-mt300n-v2:green:wan";
gpios = < 11 GPIO_ACTIVE_LOW>;
};
--
2.19.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ath79: add support for GL-iNet GL-X750
On Fri, 2 Nov 2018 at 02:22, Luochongjun wrote: > this patch adds supports for GL-X750. Please specify license in your DTS files. Ideally GPL 2.0(+) and MIT if you are OK with that. Just a line like: // SPDX-License-Identifier: GPL-2.0-or-later OR MIT and the beginning of the .dts files. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
