[fritsch]

* fritsch -- I know what a device tree is. Dropping a new one in based on a cubox and trying to boot it will obviously work, that's how *device tree* is meant to work. It's meant to boot devices when given a flat file. If the Vero DTB doesn't boot on the CuBox, it's obviously different. Fractional modesetting is also possible you probably just do not know how. There is already support for fractional modesetting (1080i50) which I am sure you know uses fractional pixel clock 74.25/1.001

Ah, we have an expert here, that has no idea. Vero does not boot, cause it is locked down, by its creator (check the uboot commits on his github). Then let's make osmc available to all cubox owners out there and see if they like it:

9 Steps to install OSMC on Cubox-i/Hummingboard (tested on Hummingboard-i1)

what you need:
A. Hummingboard, Cubox-i...
B. OSMC image
from http://46.37.189.135/osmc/download/insta...322.img.gz
C. OpenELEC's bootloader for Cubox-i/ Hummingboard
from: http://sources.openelec.tv/devel/bootloa...x-i.tar.xz

Steps to install:
1. extract OSMC image:
gunzip OSMC_TGT_vero1_20150322.img.gz

2. write OSMC image to SD-Card: (DANGER: check the path to the SDCard carefully, any disk will be overwritten!!!)
sudo dd if=OSMC_TGT_vero1_20150322.img of=/dev/mmcblk0

3. extract OpenELECs bootloadfiles:
tar xJf bootloader-cubox-i.tar.xz

4. write SPL bootloader file to SD-Card: (DANGER: check the path to the SDCard carefully, any disk will be overwritten!!!)
sudo dd if=bootloader/SPL of=/dev/mmcblk0 bs=512 seek=2 conv=notrunc

5. mount SD-Card
sudo mount /dev/mmcblk0p1 /media

6. copy bootloaderfiles to SD-Card:
sudo cp bootloader/*.dtb /media
sudo cp bootloader/u-boot.img /media

7. unmount SD-Card:
sudo umount /media

8. Boot Cubox-i/ Hummingboard with this SD-Card, OSMC will start in the installer and is installing byself
After this is done, half of our work is destroyed, and we must repeat steps 5.-7.

9. Boot to OSMC