| 04:41 | jnettlet | flips, there is no virtualization extension on the iMX6, sorry. Your best bet is to run openelec in a docker container if you want it separated from the CoreOS |
| 04:45 | jnettlet | As for booting from USB, well you can but not a USB disk. If the sdhc card isn't present then the Chip will go into recovery mode and you can boot it via the USB otg port. This is the linux version of one of the tools you can use https://github.com/eewiki/imx_usb_loader |
| 04:46 | jnettlet | the HummingBoard Edge will have a jumper so you can select booting directly from the various methods, USB OTG, SDHC, EMMC, SATA |
| 12:09 | flips | jnettlet: Ah, makes sense. Thanks :) |
| 14:11 | jnettlet | vpeter, were you having problems with a pcie card? I just pushed a fix for some pcie cards not being detected properly |
| 14:20 | flips | is it just me, or did lots of the solid-run wiki pages just disappear? |
| 14:22 | malte | a new wiki went online |
| 14:39 | vpeter | jnettlet: no pcie for me. It is available on tbs matrix but don't have any mini card and also not any adapter for "normal" ones. |
| 14:41 | flips | new wiki looks nice, but I seem to have to search to find most stuff, expected more links to stuff from the fp (I just barely used the old wiki for one day, so I don't really know it) :) |
| 16:39 | jnettlet | vpeter, okay must have been someone else. |
| 16:40 | jnettlet | Whoever complained the new 3.14.yy kernel was not working with certain pcie cards. It should not be fixed. |
| 18:53 | vpeter | my lvds problem: http://sprunge.us/KiRD |
| 18:53 | vpeter | ldb ldb.14: LVDS channel1 is not online |
| 18:53 | vpeter | mxc_sdc_fb fb.17: NO mxc display driver found! |
| 18:54 | jnettlet | vpeter, what chip is this? |
| 18:55 | vpeter | current device tree http://pastebin.com/KsH4Q6GQ |
| 18:55 | jnettlet | oh a quad |
| 18:55 | vpeter | Yes. |
| 18:55 | vpeter | Seems some mixup with fb device. |
| 18:57 | vpeter | If I use video=mxcfb1 there are no more this 2 errors but no image also. |
| 18:58 | jnettlet | vpeter, yeah you are only aliasing one framebuffer, and I think you may have them overlapping |
| 18:58 | jnettlet | remember that whatever is aliases as fb0 you must alias the next as fb2 unless you are mirroring displays |
| 18:59 | vpeter | Like this I have with current kernel and it works. |
| 18:59 | vpeter | No mirroring - just one output I need. |
| 18:59 | vpeter | Don't understand the relationship with fb, ipu, ... |
| 19:00 | jnettlet | a framebuffer is the memory that holds the scan out buffers and a device to wireup output from it. |
| 19:01 | jnettlet | the reads to and from that, including passing it along to whatever signaling you are doing, hdmi, lvds etc. |
| 19:06 | flips | hm, running via hdmi on my large monitor, the console and X ends up half and inch outside the monitor edge ... in Kodi I can adjust it, but is there a way in regular console/fb/X setup? |
| 19:14 | flips | docker works nicely in armhf? (I haven't used other containers than zones in opensolaris, jails in bsd and chroot and in Linux, oh and UML, user mode linux years ago) |
| 19:16 | jnettlet | flips, it isn't supported, but you can get it to run. It doesn't use anything hardware specific so their is really no limitation. |
| 19:16 | jnettlet | It basically does all its segmentation via platform agnostic kernel layers. |
| 19:16 | jnettlet | vpeter, okay your dts looks a bit out of whack. You have a lot of framebuffers turned on and overlapping that you don't need. |
| 19:19 | jnettlet | vpeter, you only have a single a channel lvds display hooked up correct? |
| 19:23 | flips | jnettlet: Ok, thanks. :) |
| 19:24 | flips | Are there overscan settings or what it's called for fb? Xorg? |
| 19:24 | jnettlet | flips, if you are looking for a web management gui then check out the work fedora has done with project atomic. It is a pretty straightforward compile and has some decent functionality |
| 19:24 | jnettlet | flips, we only have digital outputs so there shouldn't be much overscan problems. |
| 19:25 | jnettlet | what is the native resolution of your display? |
| 19:25 | flips | It's 1900x1200 native, but I think always 1900x1080 on hdmi |
| 19:26 | flips | and on that monitor the text is half an inch off the screen to the left, so I don't see the prompt ... :) |
| 19:26 | flips | After I get it configured, only Kodi will run in the front, I guess, so it shouldn't matter |
| 19:27 | jnettlet | can you pastebin the output of fbset -i ? |
| 19:29 | flips | Ah, I will, when I get it back to that monitor. I had to switch to the office monitor to see the screen and use ethernet until I got wlan up |
| 19:31 | jnettlet | sure no problem |
| 19:41 | vpeter | jnettlet: Yes, single channel lvds. |
| 19:43 | jnettlet | vpeter, okay so trim it down to a single fbdev device by setting status="disabled" for all the others, and then alias the fbdev to be fb0 |
| 19:43 | jnettlet | then you have two &ldb0 entries. remove the first one completely. |
| 19:43 | jnettlet | and then lets see where that gets you |
| 19:50 | flips | jnettlet: http://pastebin.com/4AJKtq9i |
| 19:51 | vpeter | jnettlet: for alias you mean only mxcfb0 = &mxcfb1; |
| 20:13 | vpeter | jnettlet: ok, no change. Seems those parameters are old and not used anymore. How to convert to new format? |
| 20:13 | vpeter | ipu_id = <1>; |
| 20:13 | vpeter | disp_id = <0>; |
| 20:13 | vpeter | ext_ref = <1>; |
| 20:13 | vpeter | mode = "sep0"; |
| 20:13 | vpeter | sec_ipu_id = <1>; |
| 20:13 | vpeter | sec_disp_id = <1>; |
| 20:14 | vpeter | first two are this? crtc = "ipu1-di0"; |
| 20:14 | vpeter | and last two crtcs ? |
| 20:14 | vpeter | How about mode? |
| 20:24 | flips | jnettlet: that pastebin was the fbset -i (and also xdpyinfo in X) |