here you can see it boot success.:), i am not a R&D , and we development all driver now , when we ready ,will public our github source code .
1 Like
Few questions
-
When will this device available for purchase?
-
Approximate cost?
-
Do you have source code for hardware NAT and Crypto chip?
“Charles” doesn’t seem very happy, and he’s certainly impatient. However, while I am excited by your announcement of this new device, I appreciate the work you’re doing. Take your time. I would rather have a good product than one that was rushed out the door before it’s ready.
1 Like
Onboard wifi/bluetooth chip support FM, can i use it on Openwrt?
i wanna buy this board (2 sata ports, 64GB eMMC) just when OpenWrt firmware is ready at https://downloads.openwrt.org/
why do you think we not do any work?, BPI-R2 will support kernel 4.4 . it is OK???
- show us a github repo with source code for this kernel,
- show us boot logs,
- show us SATA performance numbers,
- show us Gigabit Ethernet performance numbers,
- show us how the switch can be configured,
- show us NAT throughput with simple and complex firewall settings
- show us OpenVPN and IPSec encryption throughput numbers
That would be e proof of work and that you think about what this specific device should be used for. Showing instead only some small pictures with a Raspbian Pixel desktop is clearly a sign of stupidity (yeah, it’s easy to exchange the rootfs on SD cards but that doesn’t tell how smooth things work) 
Ok, to keep it simple for you: show us just the kernel sources for this ‘Open Source smart router’. You can’t since you don’t have the sources since you aren’t able to pay MTK for the necessary NDA and even then I doubt you would be able/allowed to release the sources. Please don’t lie to customers about ‘Open Source’ when it’s as closed as possible 
Charles, I understand wanting the BPI-R2. I want it, too. But it hasn’t been released yet, so there’s nothing to complain about. Besides, sinovoip doesn’t owe you anything.
Patience is required and expected.
Agreed SinoVoIP does not owe us anything.
It would be really nice if they set expectations right. If they can set release date, it will help everyone.
Something like End of April 2017 , will calm anxious people
1 Like
it support pcie interface ,so we can use it do many works . such as do a 7615 module ,so , it support AC function .
1 Like
Why? R2 has no ‘mini pci’ but mPCIe and anyone able to search for ASM1061 on eBay gets the same for less money than from you: http://www.ebay.com/itm/381525809274
http://i.ebayimg.com/images/g/9kYAAMXQDnpTYKDs/s-l1600.jpg
Well, you already heard the answer which should be a warning. Those guys don’t do software (correctly), just look through the forums. And the interesting question isn’t which distributions they provide (since that’s easy, they do this all the time, it’s just exchanging the rootfs on images), the important stuff is kernel/drivers and I doubt they will ever be able to provide sources (since they can’t afford paying the NDA to get sources from MTK and even if they had they’re not allowed to publish them, you’re dealing here with ‘closed source router’ all the time 
)
You are a very funny guy. , why not just waiting and see .
1 Like
I already own a BPI-M3 and the Hardware works well, but the Kernel is very outdated as you may know I see the BPI-M64 will be integrated to 4.11, are there any plans for BPI-M3 too?
You say the MT7623N is in the Mainline Kernel, are there chances to easily roll out other Distributions than the ones provided from you?
btw, BPI-R1 works great for Firewalling with ipfire, cant wait to setup a Firewall with the new one
C’mon, if you try to inform you now your disappointment will be not that huge later. @sinovoip does no software. They throw at you what they get from the chip manufacturer and that’s the reason the M3 is still at 3.4.39. With M64 all software development is driven by community: you can follow all the progress here, no need to trust in ‘just wait and see’ stuff board makers will tell you all the time: http://linux-sunxi.org/Linux_mainlining_effort#Status_Matrix
With MT7623N there’s NOTHING compared to that regarding mainline kernel: “As of next-20170106 still only serial is working, no MMC or network.” (this GeekForce never happened). They get closed source blobs for the R2 based on a vendor kernel drop from Mediatek… and around Mediatek there’s zero community. Wish you all good luck rejecting reality. The only MTK CPUs with good open source support are those from Ralkin (MTK aquired them).
And BPi R1 combined with firewalling seems like a great idea http://linux-sunxi.org/Lamobo_R1#Security_Implications
Thanks for the links, they are very interesting The Firewall is for testing proposes only but good to know this
Well Sinovoip, how will the new MT7530 react?
If you guys do proper software support it could be a nice piece of Hardware…
I still have a little bit hope 
Why? R2 has no ‘mini pci’ but mPCIe and anyone able to search for ASM1061 on eBay gets the same for less money than from you:
I wasn’t aware that sinovoip had published a price list for the BPI R2 yet. Have you seen it?
Wow, great news. Upstream support for DSA by Mediatek themselves: https://lkml.org/lkml/2017/3/13/738 so maybe in a few months it will be in official kernel. And there’s also something going on around 7623 upstream: https://lkml.org/lkml/2017/1/16/591 (seems MTK isn’t that much or at all involved here and the whole thing is progressing rather slowly )
No, and I guess that’s for a reason! The whole excitement might be gone once you know how much they will charge for this 
Anyway: if I would need two more SATA ports added to one already existing I would clearly choose Marvell’s EspressoBin instead (great device and great software support) and add a cheap ASM1061/1062 mPCIe card.
Sadly Marvell’s EspressoBin’s mPCIe only supports wifi & bluetooth. Actually ClearFog Pro is a more powerful but expensive SBC.
Why’s that? It’s mPCIe as per specifications according to released schematic: https://raw.githubusercontent.com/wiki/MarvellEmbeddedProcessors/main/files/arlp/Block-Diagram-Schematics.pdf
If it’s mPCIe you can attach any PCIe device, right?
Funnily it’s really easy to spot the difference between so called ‘Open Source’ blabla as it’s the case here and true open designs. Schematic and sources are released even before product launch, you find everything already below https://github.com/MarvellEmbeddedProcessors/
And now compare with this Banana joke here
Don’t know why.
source ( from http://espressobin.net/forums ): The PCIe slot on Espressobin is for WIFI and BT usage only. It doesn’t support mSATA.