On Mon, May 24, 2021 at 2:51 AM Vincent Wiemann
wrote:
>
> Hi Russel,
>
> On 5/24/21 1:06 AM, Russell Senior wrote:
> > On the PowerBeam M2 (PBE-M2-400) I see "e2 c2" in the same locations, not
> > "e6 c2".
>
> That's very interesting... I think the PowerBeam 400 was sold under the
> NanoBeam
> Subject: [PATCH v2] ath79: add support for Ubiquiti PowerBeam M (XW)
> Message-ID: <20210523115946.711907-1-russ...@personaltelco.net>
>
> This patch adds support for the Ubiquiti PowerBeam M (XW), e.g. PBE-M5-400,
> a 802.11n wireless with a feed+dish form factor. This device was previously
>
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
From: Rafał Miłecki
netifd has been recently patched to use "device" option instead of
"ifname" as more clear & accurate.
Signed-off-by: Rafał Miłecki
---
.../htdocs/luci-static/resources/network.js | 100 +-
.../resources/view/network/interfaces.js | 39 ---
2
From: Rafał Miłecki
Replace "ifname" with "device" as netifd has been recently patches to
used the later one. It's more clear and accurate.
Signed-off-by: Rafał Miłecki
---
This can be applied after updating netfid to include:
[PATCH V2 netifd] interface: rename "ifname" attribute to "device"
Hi Russel,
On 5/24/21 1:06 AM, Russell Senior wrote:
On the PowerBeam M2 (PBE-M2-400) I see "e2 c2" in the same locations, not "e6
c2".
That's very interesting... I think the PowerBeam 400 was sold under the
NanoBeam series at the beginning. So there might be an entry missing.
Is your
This is present on Roqos Core RC10 and needed to control LED matrix.
Signed-off-by: Tomasz Maciej Nowak
---
package/kernel/linux/modules/i2c.mk | 29 +
1 file changed, 29 insertions(+)
diff --git a/package/kernel/linux/modules/i2c.mk
The ZyXEL LTE3301-PLUS is an 4G indoor CPE with 2 external LTE antennas.
Specifications:
- SoC: MediaTek MT7621AT
- RAM: 256 MB
- Flash: 128 MB MB NAND (MX30LF1G18AC)
- WiFi: MediaTek MT7615E
- Switch: 4 LAN ports (Gigabit)
- LTE: Quectel EG506 connected by USB3 to SoC
- SIM: 1 micro-SIM
On 23.05.2021 23:06, Rafał Miłecki wrote:
I'm looking at existing code, at the commit be09c5a3cd65 ("base-files:
add board.d support for bridge device") and I have some problems
understanding those bridges.
If you can, please kindly answer me two questions:
Please also post your
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
Hi Rafał,
thank you for your reply.
On 2021/05/24 6:06, Rafał Miłecki wrote:
On 23.05.2021 13:30, INAGAKI Hiroshi wrote:
After the commit 43fc720657c6e3b30c6ed89d7227ee6e646c158b
("base-files: generate "device UCI type section for bridge"), the
wrong
network configuration is generated for
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
> *
eth0 -> single NIC (i211at)
eth1 -> single NIC (i211at) -> 4-port unmanaged switch (BCM53125U)
Notes
UART is exposed on J4 connector, pinout starting from pin marked 1:
1. GND, 2. NC?, 3. NC?, 4. RX, 5. TX, 6. NC?
baud: 115200, parity: none, flow control: none
The board is setup by coreboot with
On 23.05.2021 13:30, INAGAKI Hiroshi wrote:
After the commit 43fc720657c6e3b30c6ed89d7227ee6e646c158b
("base-files: generate "device UCI type section for bridge"), the wrong
network configuration is generated for the devices that already have the
bridge device section for VLAN, such as the
> "Vincent" == Vincent Wiemann writes:
Vincent> Just as a side-note: There are 5 different versions of the
Vincent> PowerBeam with different device IDs...
Vincent> Source:
Vincent>
https://github.com/freifunk-gluon/gluon/issues/94#issuecomment-510831878
Vincent> -- PowerBeam M5 -- ERP 26
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 {
>> +
> The 4-"byte"-address mode is used on 32 MiB flash chips.
> We had similar issues with other 32 MiB devices in the past
> which were fixed at some point by Felix Fietkau.
My device is 32MiB. I'll check with Felix if he can give me any clues.
@Everyone else reading this, do you know how one can
Instead of creating the temp file in "/etc/config" it should be created
where the config file actually exists (if the file is symlinked, it
might be in another mount point and "rename()" will fail)
Signed-off-by: Arjun AK
---
file.c | 14 --
1 file changed, 12 insertions(+), 2
Hi,
I believe I've made the required changes. Can this be merged in now?
-
Arjun
On May 8, 2021 12:02:57 AM UTC, Arjun AK wrote:
>From: Arjun
>
>This command will show whether a SIM card has been inserted and whether
>a pin is required.
>
>Signed-off-by: Arjun
>---
> commands-uim.c | 26
On 23.05.2021 13:30, INAGAKI Hiroshi wrote:
After the commit 43fc720657c6e3b30c6ed89d7227ee6e646c158b
("base-files: generate "device UCI type section for bridge"), the wrong
network configuration is generated for the devices that already have the
bridge device section for VLAN, such as the
From: Rafał Miłecki
Interfaces need to be assigned to devices. For that purpose a "device"
option should be more accurate than "ifname" one.
For backward compatibility add a temporary config translation.
Config example:
config device
option name 'br-lan'
option type 'bridge'
This adds a new device id to the image tools.
Signed-off-by: André Valentin
---
tools/firmware-utils/src/zytrx.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/firmware-utils/src/zytrx.c b/tools/firmware-utils/src/zytrx.c
index 302efc6010..b3bbbe3c69 100644
---
This set adds support for the ZyXEL LTE3301-PLUS, an indoor 3G/4G indoor LTE
router with Wifi.
Thanks to Bjørn Mork for the image tool implementation.
André Valentin (2):
firmware-utils: zytrx: Add support for ZyXEL LTE3301-PLUS
ramips: mt7621: Add support for ZyXEL LTE3301-PLUS
24 matches
Mail list logo
