I am not quite certain how others feel about it but I feel quite disappointed seing a hardware upgrade of a device which hasn’t already received official software support. Namely the BPI-R3.
I do understand that there is a proprietary OpwnWRT but that is not really a solution given the lack of software updates and, quite frankly, very old OpenWRT version the BPR-R3 is shipped with.
The Arm a57 also offers a serious performance increase making the R4 the more future proof choice. Future proofness and open source were my main motivators opting for the BPI-R3.
Edit: There is already a great article out there which partially compared the R3 to the R4
Whilst the R3 is not obsolete per se since it still offers one of the most compelling and performant hardware specs compared to off the shelf products, the R4 looks hell of a lot more compelling given the plethora of storage options, doubled RAM, better overall design with the antenna ports moved to the bottom of the PCB.
In particular moving the antenna ports show how much brain power was invested. The LEDs are also better placed enabling properly light carriers instead of the flimsy 1mm at most spacing on the R3. Not to speak of the (presumably) much improved BootStrap switches which, quite frankly, still give me some headache.
@simon I noticed that wifi card is not recognized by pcie driver on cold boot,but after reboot. Maybe we need a delay in pcie driver. Have you seen this too?
Maybe this is fixed by v1.0? Imho change wifi-enable into wifi disable may brick pcie devices except the wifi-module,am i right? Of course i can set the regulator in dts,but before (atf,uboot) 12v are always enabled.
Because MTK’s pcie does not have a hotplug function, the 12V power supply of the NIC must be powered on before initializes pcie, and the power-on sequence of the NIC cannot be controlled by software like the V00.
There are still problems with the current wi-fi driver and DDR driver. When using 4GB DDR, it will always reboot after detecting wi-fi, but it can be used stably after limiting the DDR to 2GB.
Isn’t this a problem for other mPCIe cards? As far as i see,12v it put on pins 6, 28 and 48 of the mPCIe slots (cn12+cn14). Afair there were discussions for r64 where users had bricked mPCI cards because of 5v on pin 48,so these slots are for wifi-module only (or at least 12V tolerant cards).
My 1.0 schematic still says WiFi_12V_EN connected to GPIO4_GPIO_A,but yes - switching it off in linux does not makes sense if it is on from poweron till linux-boot (atf+uboot on sw level).