Jump to content

Armbian for OrangePi PC2, AllWinner H5


Christos

Recommended Posts

18 minutes ago, zador.blood.stained said:

Not on Armbian images since it is currently possible only on legacy kernels.

That's what I thought. Shame the legacy kernel's video is so badly broken it can't display anything on most monitors.

 

I did see libvdpau-sunxi1 in the apt repository and installed it but it doesn't seem to do anything useful. Thanks for the confirmation. I wasn't sure if my install had broken over time with all the updates or it wasn't supported.

 

Link to comment
Share on other sites

libvdpau-sunxi1 is an experimental vdpau backend that in conjunction with an kernel driver has demonstraded hardware decoding of MPEG2 MPEG4, see:

 

http://free-electrons.com/blog/support-for-the-allwinner-vpu-in-the-mainline-linux-kernel/

 

Unfortunately it seems that no one is actively working on it. Apart of the lack of support for H264/H265, the kernel driver is out of tree, so as usual, it doesn't compile anymore.

In summary we are far away from having a RPi OMX like VPU support

Link to comment
Share on other sites

I have filled a github issue and started a thread in development forum

I see that one mandatory patch is not applied to uboot and the DVFS and THS patch for H5 have been moved to "unresolved" directory

I think that user reported boot lockup due to the missing patch in uboot and Armbian devs removed the kernel patches...

But so far none of the devs replied, I guess it is vacation time

Link to comment
Share on other sites

On 30.06.2017 at 4:56 PM, hojnikb said:

Anything new on this ?

If not, anyone still has an image with older kernel, that has this working ?

 

Thank you.

DVFS works fine on a patched 4.12.0, but on OPi-Prime. If you need I may send patches.

Link to comment
Share on other sites

13 hours ago, Jieffe Laurent said:

Could you share the patches? Some users, like me, need to tweak the default armbian configuration, i.e. DVB and VLAN support

Link to comment
Share on other sites

Hi everyone!

 

My first post is for asking for some help... I'm still waiting for some Armbian testing for my Orange PI PC 2, because I'm using Android right now (XunLong custom) and It's perfect for do some Kodi stuff and something else...  but I'm missing some LTS software on this board to test multiple things to do. There's some interesting Armbian for this board today, I will set up some KODI and few things to test... ? (Not experimental & not by command-line)

 

Thank you very much

 

Kind Regards

Link to comment
Share on other sites

Hi
I am kind of newbie in uboot&kernel, so please forgive me if it's a rookie question

Is it possible to compile android (ether original or AOSP) with mainline kernel and uboot?
I have already compile armbian uboot&kernel for this device but the result is in .deb format, I have searched the net to convert it but couldn't find anything usefull.

in addition the original android source needs some module which produced (I guess) during the compile of legacy kernel, and I couldn't find them in output of armbian compile.

any kind of guidance appreciated.

 

Thanks in advance

 

Link to comment
Share on other sites

On 20. 7. 2017 at 1:26 AM, timet said:

I could not use my wireless keyboard


You mean it failed after update or it never worked on this board?
 

6 hours ago, mousavy_mh said:

Is it possible to compile android (ether original or AOSP) with mainline kernel and uboot?


Not possible.

Link to comment
Share on other sites

For those who think PC2's development is stalled, it's possible to build your own Arch Linux image with custom Linux 4.13rc (using armbian .conf and oldconfig) and u-boot 2017.7. You get a more stable ethernet connection and all of upstream goodness bu still lacking DVFS support.

Link to comment
Share on other sites

DVFS for H5 has been "lost" by the developers, even if it exist in various form. I think it is mainly due to confusion about the PLL divider bug, which was stalling the CPU during frequency transition. The problem has been fixed in uboot. 

If you check the http://linux-sunxi.org/Linux_mainlining_effort you can see that the DVFS and THS for H5 is not even scheduled

But I have posted on the sunxi newsgroup and if you check the post "DT based cpufreq scaling for H5" Icenowy Zheng (the principal sunxi dev) promised to give a look at it

But, as I have said, the code is there, and the main, all including, experimental, repo for H5:

https://github.com/megous/linux

includes it. In this repo, there is the latest and greatest stuff (with decent testing) for H5. I would suggest the Armbian devs to used this repo for building kernel for H5

Bye

Link to comment
Share on other sites

2 hours ago, Menion said:

DVFS for H5 has been "lost" by the developers, even if it exist in various form. I think it is mainly due to confusion about the PLL divider bug, which was stalling the CPU during frequency transition.

There is no confusion. There are known fixes for this instability, though H5 and A64 dev branch currently has a very low priority at least for me, and I don't expect any radical changes before kernel 4.13 and u-boot 2017.09 are both released.

 

2 hours ago, Menion said:

If you check the http://linux-sunxi.org/Linux_mainlining_effort you can see that the DVFS and THS for H5 is not even scheduled

But I have posted on the sunxi newsgroup and if you check the post "DT based cpufreq scaling for H5" Icenowy Zheng (the principal sunxi dev) promised to give a look at it

Still WIP and minor changes are required: https://groups.google.com/forum/#!topic/linux-sunxi/-xzEQnP57kI

Link to comment
Share on other sites

13 minutes ago, Menion said:

But would not be better to use this repo:

https://github.com/megous/linux

For the H5 (and possibly H3) build?

We are using this for H3 already (4.11 branch), and since H5 shares the same mainline kernel with A64 switching now will break things if we don't port or adjust a lot of patches. And 4.12 branch there still contains the old Ethernet driver and legacy clock bindings for DVFS/THS, so I wouldn't call it "the latest and greatest"

Link to comment
Share on other sites

Well

Actually also the branch used by Armbian so far use the old sun8i-emac and it does not have the DVFS THS at all.

Anyhow I am too far from having a full understanding of all the Armbian internals and dependencies, so I cannot really tell you more than just a suggestion :)

Bye

Link to comment
Share on other sites

Hi, I have just updated uboot and kernel from Armbian build. Kernel is now 4.11.10-sun50iw2 on my OrangePiPC2

I see DVFS+THS patch added to kernel, but no dts bindings, so no cpufreq support and no throttling

Also, the USB OTG does not work, even if the WIP code already exist

Just as a point of discussion: I think that H3 and H5 shall share the same WIP branch, rather then use the same for H5 and A64.

H5 and A64 have a completely different target products and very different architecture, they just share the CPU core. 

Instead H3 and H5 are much more similar, only cores differs

Using https://github.com/megous/linux for H3 and H5 should get rid of most, if not all, the patches currently applied for H5 on Kernel, delivering at the same time a good level of WIP features for proper testing (and the fork itself is tested...)

I would be happy to do it on my own to contribute, but I am very bad in bash and I am lost in the Armbian build scripts :(

Link to comment
Share on other sites

54 minutes ago, Menion said:

Just as a point of discussion: I think that H3 and H5 shall share the same WIP branch, rather then use the same for H5 and A64.

And my point is that 3rd party WIP branches will not be needed at all pretty soon, mainline 4.13 with some patches on top will be enough for headless usage.

 

1 hour ago, Menion said:

I would be happy to do it on my own to contribute, but I am very bad in bash and I am lost in the Armbian build scripts :(

Just FYI, as I said earlier, switching branches may break stuff including support for some newer H5 devices, and I'm pretty sure that some people would be unhappy about that. If DVFS is essential for you, feel free to fix it, I don't think you need any bash knowledge to do that.

Link to comment
Share on other sites

Is someone able to provide Information about the GPIO Interface? There is zero documentation about it on the Orange Pi PC2. How are the port numbers calculated, how are internal pullups activated? As someone has implemented the gpio stuff, it should be usable, I just haven't figured out how to talk to it.

Link to comment
Share on other sites

With a little search, you would have found that : http://linux-sunxi.org/GPIO

 

In summary, all SoC from AllWinner use the same formula :

(position of letter in alphabet - 1) * 32 + pin number

For OpiPC2 specific, look at the schematic :

http://linux-sunxi.org/File:ORANGE_PI-PC2-V1_2_schematic.pdf

 

For Python library, use https://github.com/duxingkei33/orangepi_PC_gpio_pyH3

But for any 64 bits, you need to fix a small issue : change all references to SUNXI_PIO_BASE in gpio_lib.h/gpio_lib.c from "unsigned int" to "unsigned long" to have a 64 bits pointer.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines