Uboot have official support BPI-M2


(bpi team) #1

Uboot have official support BPI-M2

Hans de Goede - Oct. 15, 2015, 2:33 p.m. The Sinovoip BPI-M2 is a SBC board based on the A31s SoC it features 1G RAM, a microsd slot, Gbit ethernet, 4 usb-a USB-2 ports, ir receiver, stereo headphone jack and hdmi video output.

The dts changes are identical to the dts files submitted upstream.

A few notes on the use if dldo and aldo regulators. DLDO1 is used for Vdd for the ethernet phy, ALDO2 is used for AVdd for the ethernet phy. ALDO1 is used to power the sdio wifi module.

Signed-off-by: Hans de Goede hdegoede@redhat.com

arch/arm/dts/Makefile | 3 ± arch/arm/dts/sun6i-a31.dtsi | 18 +++ arch/arm/dts/sun6i-a31s-sinovoip-bpi-m2.dts | 194 ++++++++++++++++++++++++++++ board/sunxi/MAINTAINERS | 1 + configs/Sinovoip_BPI_M2_defconfig | 18 +++ 5 files changed, 233 insertions(+), 1 deletion(-) create mode 100644 arch/arm/dts/sun6i-a31s-sinovoip-bpi-m2.dts create mode 100644 configs/Sinovoip_BPI_M2_defconfig Ian Campbell - Oct. 15, 2015, 6:40 p.m. On Thu, 2015-10-15 at 16:33 +0200, Hans de Goede wrote:

The Sinovoip BPI-M2 is a SBC board based on the A31s SoC it features 1G RAM, a microsd slot, Gbit ethernet, 4 usb-a USB-2 ports, ir receiver, stereo headphone jack and hdmi video output.

The dts changes are identical to the dts files submitted upstream.

A few notes on the use if dldo and aldo regulators. DLDO1 is used for Vdd for the ethernet phy, ALDO2 is used for AVdd for the ethernet phy. ALDO1 is used to power the sdio wifi module.

Signed-off-by: Hans de Goede hdegoede@redhat.com

Acked-by: Ian Campbell ijc@hellion.org.uk

and for the 1/2 as well, which hardly needs an ack IMHO.

more message: http://patchwork.ozlabs.org/patch/530737/


#2

This patch has been applied on u-boot mainline. More information: http://git.denx.de/?p=u-boot.git;a=commit;h=fc01daee8b8dc1ea486fcbea887224c8d1aca33b


[M1]Build and Boot v4.2 kernel (just for record and use by myself)
#3

It’s important to note that the manufacturer of the device has nothing to do with the community work mentioned here. A member of the linux-sunxi community bought an M2 and donated it to Hans to get the Banana Pi M2 supported in mainline u-boot and linux kernel. This took some time but now it’s done.

https://groups.google.com/forum/#!searchin/linux-sunxi/A31s/linux-sunxi/sMMqCjUfoLE/RXYJwz0U_C4J http://forum.armbian.com/index.php/topic/126-fyi-armbian-running-on-a31s-based-banana-pi-m2/?p=2157

SinoVoip didn’t support the community and did not contribute to the process of getting mainline support for the M2. Their whole ‘development style’ is a real mess. They clone the linux kernel, don’t do proper commits and hide somewhere in the kernel sources (over 50.000 files) the only change that matters: the device tree file describing their own hardware. And they still do not change this crappy style, they still not contribute, they still don’t send their patches upstream.

And while they mention that the M2 is supported in the official kernel at the same time they’re not able to exchange the crappy .dts they use in ‘their’ kernel with the community’s referenced here in this thread: https://github.com/BPI-SINOVOIP/BPI-Mainline-kernel

This whole thread/post is just marketing bullsh*t as usual. They don’t learn a single lesson. It seems they’re not able to understand how ‘open source’ development works.


BPI M1+ UART3 (TTYS2) not Working
Banana PI M3 V.S. ODROID-XU4
(bpi team) #4

dear tkaiser, we have do many working on BPI-M2, you can note ,we have do mainline kernel 4.2 support on BPI-M2, and also do allwinner SDK 3.4 kernel to github. uboot and kernel we have do many work ,and we are first team let A31S support mainline uboot and kernel. we hope you can support us .


#5

Please stop this marketing bullsh*t! You did NOTHING! The linux mainline kernel is the work of many people from around the globe. All you as a hardware manufacturer has to do nowadays is to describe your hardware with a device tree file (for older kernels you need to encode the same informations in a fex file).

What did you do? You didn’t release the fex file and you didn’t create a correct .dts file. All you did was cloning the linux mainline kernel a few times (which is simply insane and dumb) to hide the only single file that is interesting – sun6i-a31s-bananapi-m2-plus.dts – in the 50.000 files the linux kernel sources now contain).

If you would be able to understand how ‘open source development’ works then you would stop cloning kernel sources and claim they were ‘yours’ but would instead join the linux-sunxi community and contribute. Then you would’ve donated a few M2 to the developers who do the real work (these are not your employees but people from around the world), then you would’ve provided correct hardware informations and then you would’ve send patches that you now hide somewhere inside cloned kernel sources upstream to get your hardware supported by the mainline kernel.

This does not happen. You use the term ‘open source’ everywhere but you simply have no clue what it means. :frowning:


Mainline linux kernel 4.4-rc1 have support BPI-M2
(bpi team) #6

i only to say , we have try let mainline kernel working on BPI-M2, not mean others .