Banana Pi BPI-R4 Wifi 7 Module design

I know the BPI-R4 board has a combined connector for 2 mPCIe interfaces, but I thought a single mPCIe connector would be a standard pinout and size.

In this thread https://forum.banana-pi.org/t/bpi-r4-building-with-asiarf-7916-need-help/17389/21 people are reporting the AsiaRF card will fit in the mPCIe slot and are recognized.

I have not tested an AsiaRF card myself.

i guess they talking about the wifi6e cards (single pcie), no dual connector like the bpi wifi7 card…the bpi board is mt7996 with 2 frontends

i know that asiarf also had a mt7996 wifi7 card, this is what i’m talking about, but did not know if it has also an mpcie variant and if the space between connectors will fit r4

Yeah I thought it was the WiFi 7 board since we are in the WiFi 7 module thread. The 7916 works at least the official docs says so.

Of course, I understand that the BE19000 module is being developed, but I would like to know the details. This silence is just killing me. It’s as if everyone forgot about this module

Hi, Is there any news about the OpenWrt mainline support for the BPI-BE14 for the R4? Any idea about when shall we expect it?

The firmware is currently testing state and cannot be added to openwrt due to missing license. But you can fork the main project and add it by yourself

May I ask which license are you referring?

I try to explain, but I’m a laiman:

Banana Pi has their own special openwrt Version (I think this is what frank means with “main project”) The driver should be developed by Mediatek & Banana Pi.

But people like frank-w and Dangowrt working on the official Openwrt. Because this is open source, you can not add a driver from someone else and publish it without permission. As I understand it right the wifi 7 driver has to be integrated in linux (OpenWrt is based on Linux). This is the “problem”!

It is a bit confusing, because we are on the banana Pi forum. But it makes sense, because the Banana PI openwrt version is limited in other ways … .

→ hoping this is correct? :slightly_smiling_face:

Yes, understandeble → you have to see this from a “popcorn perspective” :upside_down_face:.

If you followed the information about the BE14 board → the silence about BE19 makes sense.

For BE14 the pictures are out like for BE19. But than they had to redesign the BE14 board. I assume this will also happend for BE19.

There are even people who can not joke about their mistakes in a private context. Because they don’t want make fun about themselves … .

Anyway, we have a private perspective on this topic. But for Banana PI it is about their business reputation. They don’t want to embarrass your company!

I also would like to have more information about the NIC’s and drivers. And I want more people from banana PI in the chat rooms and … but it seems like we have to live with that what we get, so waiting go’s on :slightly_smiling_face:

So it turns out that the R4 snapshots posted on the openwrt website do not have a wifi 7 driver? Then how do people use BE14? Where do they get the openwrt firmware with the proprietary wifi 7 driver from mediatek?

It’s also a little confusing that the BE14 is now being more actively developed, it’s already on sale, despite the fact that the vote showed that people are more interested in the BE19

This is the OpenWrt version from banana PI:

OpenWrt firmware download:

https://firmware-selector.openwrt.org/?version=SNAPSHOT&target=mediatek%2Ffilogic&id=bananapi_bpi-r4

Yes, but this is no democracy and it is history (because they decided for BE14 first).

For me it looks like a good chance for a BE19 board … future will show

Thanks, In general, in this case, how important is it for wifi 7 for R4 to have an open driver? I mean, is there any advantage from an open driver in Linux over a proprietary one from Mediatek, besides the openness of the code itself?

Sorry if I’m bothering you with my amateurish questions, I saw in the list of R4 firmwares a version with RJ 2.5Gb, i.e. In this firmware, SFP is disabled and one of the RJ ports becomes 2.5Gb? Can it be installed on a standard R4 without any manual modifications? It’s strange that it is listed below the oldest firmware versions, is this version ever updated?

ok, I was just expecting a version of MT76 driver with MT7995AV(chipset of BE14) support. Usually such a case that it is a generic opensource driver and not unique to BPI BE14. Such like generic MT76, athX based mac80211 drivers. But looks like Mediatek is supplying(or co-developing for BE-14) the stack of MT7995AV for BPI-R4 custom OpenWrt repo - and this where the license issue kicks-in I guess.

The method @frank-w mentions (fork main project - add the driver of be14 from the BPI-R4 custom OpenWrt repo - If I didnt misunderstand) sounds scary to me. If this is legal, and if someone would like to guide/work, I can also spare time for this. regards

Proprietary driver allows more control on parameters and promises more performance. If you can get stable version which does everything you need, can be considered really a good option. And if you can get updates, it is best thing you can get. This is not something you get easily. However, opensource drivers provide generic functionality common across different vendors and usually provides updates, if it gets popularity in the community. So, when choosing a board, I personally prefer a one supported at upstream OpenWrt which have the daily snapshots, makes me feel quite comfortable.

Hi, 1-)Do we expect MLO and 320MHz bandwidth functionality with BPI-BE14? 2-)Can we learn max TX power per MCS? also RX Sensivity per MCS info also can help.

regards,

This is a question for another chat!:

May be this:

The second picture is what you looking for.

But the answer is no! → You have to desolder the SFP Cage and solder in a RJ-45 … but I have not done this. And additionally POE modul if you need it!

May be you find a better chat that still exist. For that use the search function:

grafik

Or open an new chat!

So if sinovoip won’t free up full drivers and firmware package for wlan module we will have similar situation to qualcomm nss offload firmware, then with openwrt policy this will be limited and afterall useless… Or i am wrong? Or we will have to use “openwrt” from sinovoip with non free firmware etc?