Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

projects/imx6: final merge of all changes #3645

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
Contributor

vpeter4 commented Nov 26, 2014

tested on TBS Matrix v2.1 and CuBox-i4Pro

@fritsch fritsch commented on the diff Nov 26, 2014

...x6/patches/linux/linux-320-cuboxi_led_heartbeat.patch
@@ -0,0 +1,10 @@
+--- a/arch/arm/boot/dts/imx6qdl-cubox-i.dtsi 2014-11-25 19:23:06.332485391 +0100
++++ b/arch/arm/boot/dts/imx6qdl-cubox-i.dtsi 2014-11-25 19:23:24.675776865 +0100
+@@ -31,6 +31,7 @@
+ label = "imx6:red:front";
+ max-brightness = <248>;
+ pwms = <&pwm1 0 50000>;
++ linux,default-trigger = "heartbeat";
@fritsch

fritsch Nov 26, 2014

Contributor

be careful here, that only initialises default-trigger

@vpeter4

vpeter4 Nov 27, 2014

Contributor

What do you mean by that? Any problem I can have with this?
Default trigger is heartbeat so as soon kernel starts led starts blinking. Later from service it is set to default-on.

@fritsch

fritsch Nov 27, 2014

Contributor

First I think I have mixed that with c code :-)

in C:

int x, y = 5;

will only initialze y to 5, so afterwards calculating with x yields undefinied behaviour. Not sure what dtsi is though.

Edit: Oh, I see it's "linux,default-trigger" <- the complete thing is a var: http://www.cs.fsu.edu/~baker/devices/lxr/http/source/linux/Documentation/powerpc/dts-bindings/gpio/led.txt

Contributor

jenkins101 commented Dec 1, 2014

very good @vpeter4!

Contributor

vpeter4 commented Feb 2, 2015

No more interest for imx6 and openelec? I mean other systems beside cubox-i.
TBS Matrix working, Udoo working, Wandboard also working.

jpulz commented Feb 2, 2015

+1 for Wandboard (Quad Rev. B1 in my case)

xoddark commented Feb 3, 2015

Wandboard support is not integrated to this pull request.
What is the best ?

  • merge this and made a second pull request for the Wandboard (and Udoo)
  • or create a new pull request with the support for all the additional imx6 support.
Contributor

vpeter4 commented Feb 3, 2015

I don't have Wandboard so I would prefer second PR for it.

Contributor

jenkins101 commented Feb 6, 2015

+1

xoddark commented Feb 6, 2015

I wait for integration of this, and after I would do a Pull request for Wandboard management.

Thank you.
PS: Lakka project wait this to resurrect their Wandboard version.

Contributor

piotrasd commented Feb 6, 2015

+1

Contributor

vpeter4 commented Feb 10, 2015

So I see OpenELEC 5.0.2 and still no sign of merging this PR. And I though this will be done after 5.0.0.

@sraue: is there any interest of OpenELEC to support more devices based on i.MX6 SoC or not?
If yes then do it and if not then tell us so we can move on and stop waiting for official landing (like ignoring all other devices because I see no point of supporting them manually which I have no interest).

Contributor

piotrasd commented Feb 13, 2015

@vpeter4 could you rebase ? Thanks

Contributor

vpeter4 commented Feb 13, 2015

@piotrasd: why waste time if not merged anyway. So I should rebase again and again every few days....
When it will be clear that merge will happen then I will rebase.

Contributor

vpeter4 commented Feb 14, 2015

I'm giving up on this so closing PR. To bad.

Contributor

CvH commented Feb 14, 2015

At least a short statement from @sraue should be doable :-(

JoostK commented Mar 1, 2015

Please merge this so OpenELEC may benefit from the additionally support devices. @vpeter4 has done some awesome work here, I have been running his UDOO build for several months already without issues.

Contributor

fritsch commented Mar 2, 2015

@sraue A statement is needed if you want to have that integrated or not. Shipping and providing another 4 images is a completely different topic and from my POV unlikely to happen.

what to you mean by the "statement" term ? (french spoken here)
@vpeter4's work should not remained unused, it is not clean enough to be merged ?

Contributor

vpeter4 commented Apr 10, 2015

@xoddark took over my work here: https://github.com/xoddark/OpenELEC.tv/commits/imx6_multi_devices
I will help him as much I can. Hope his work will not decay as mine. Seems official OpenELEC cares only for official partners and sponsors.

I want to make OpenELEC run on the RIoTBoard.
I managed to compile and boot the version from @xoddark.
I used the mainline u-boot and dtb from mainline Kernel though. Boots up without problems and can get a picture in u-boot over HDMI.
But I can´t get a picture on when OpenELEC starts.

I´d like to integrate the needed code, but I´m no kernel/driver programmer and would need some help on what I have to change to make it run.
Only need the Info in what places I have to make changes.

Contributor

vpeter4 commented May 3, 2015

You need to use appropriate dtb for kernel 3.14 which is used for imx6 project - in general you can't mix dtb's between different kernel versions. So you have 2 options: use mainline kernel or port required changes to kernel used by openelec.

Ok then I´ll stick to the mainline kernel since all changes are in there.
Will only have to look on how to boot up the rootfs.
Thanks for the reply.

@RadiatorTwo Are you sure that the mainline kernel supports vpu and gpu?

s00500 commented May 13, 2015

Please merge this! @vpeter4's work is really cool and running Openelec on the i.mx6 is a really nice thing! I can't understand why this request hasn't been accepted yet

vpeter4 closed this May 20, 2015

vpeter4 deleted the unknown repository branch May 20, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment