09:09 <Dodger78> hi guys , does hansg uboot repo have support for cubieboard 4 yet ?

09:10 <Dodger78> and another question, i want to have SPDIF running at hansg kernel repo on cubietruck. i got a alsa sounddevice, but no SPDIF output yet. did i miss a config option ?

09:11 <Dodger78> cubietruck / 4.1rc xx , hansg sunxi-wip branch

12:49 <mripard> wens: around?

12:49 <mripard> do you have an A10/A10s/A13 board at hand ?

15:05 <dbeulen> Is there anybody who had any luck getting disp_mode = 3 working (two screens, one big framebuffer) in the fex file? When i choose this mode I get the top of the screen my HDMI output, and the bottom of the screen on my LCD output. But only the top half of each screen is used instead of the full screen. Any idea how i can get a bigger framebuffer? Im using the A20 Soc.

15:16 <TheLinuxBug> mripard: O have a few A10 cubieboard here is you need one to test something?

15:17 <TheLinuxBug> I*

17:05 <leowt> what is the status of vdpau on gstreamer?

17:06 <leowt> who is deving it?

19:00 <pstef> Hello. I own an Optimus Board. I've tried to re-flash it with Ubuntu server, as per this article: http://www.mininodes.com/installing-ubuntu-server-14-04-on-the-arm-allwinner-a80-optimusboard-or-pcduino8-arches/ I was able to follow the article successfully until the "Place the micro SD card in the slot, and the board will recognize that it contains an update.sh file" part; the "recognition" is based on another script named ...

19:01 <pstef> ... update.sh that in case of no valid rootfs, tries to mount a udisk and an sdcard to look for the update.sh there. It does so improperly: it looks at three consecutive partitions /dev/mmcblk0* and then gives up. In my case, the card I plugged in is under /dev/mmcblk1... When I realized that, I was able to mount the ext2 system on my SD card and attempt to manually do the steps that the update.sh script was supposed to do. So ...

19:01 <pstef> ... when I look there, I see that it boils down to: "dd if=ubuntu-trusty-arm-mininodes-20141227.img of=/dev/nandd bs=4M". That doesn't work, however, because I get this message "No space left on device" - as do two other people who made comments on the article's page. So I thought that maybe I should choose another device instead of /dev/nandd, but I have no idea which and at this point I'm stuck. Any kind of help will be ...

19:01 <pstef> ... appreciated. Here's "df -h" and "fdisk -l" output: http://codepad.org/acLNTrED