| 00:01 | mk01_ | R0nd: lsusb -v tells what ? |
| 06:40 | R0nd | mk01_: lsusb shows Bus 001 Device 003: ID 14cd:125c Super Top SD card reader |
| 06:57 | R0nd | nvm, it works now. no idea what that was |
| 16:18 | topi`_ | any ideas why the HDMI output of my Hummingboard goes to a 640x480 resolution nowadays? using the debian/jessie image rabeeh posted last winter. It used to stay on the 1920x1080 resolution which is the native res of my HDMI monitor (a 1-year old Samsung 22") |
| 16:18 | topi`_ | it seems the resolution is correct at least while in U-BOOT, but then when the kernel runs... |
| 16:19 | topi`_ | is this something that can be caused by a casual apt-get update && apt-get upgrade |
| 16:41 | jnettlet | topi`_, which kernel/image are you using? |
| 17:29 | topi`_ | jnettlet: it's the 3.14.14+ kernel from your kernel-stable-imx6 |
| 17:29 | topi`_ | Sat Apr 25, so it's pretty old now, but back then was the HEAD :) |
| 17:30 | topi`_ | but, I haven't updated the kernel at all - and before I had no problems with 1920x1080 output to this very same monitor, so this behaviour strikes me odd |
| 17:30 | topi`_ | fbset reports 640x480 |
| 17:33 | jnettlet | if the kernel hasn't been updated then I would check the kernel commandline |
| 17:33 | topi`_ | if I try "fbset -xres 1920 -yres 1080", the monitor shows nothing. Yet, the monitor says "optimal resolution is 1920x1080" |
| 17:33 | jnettlet | check. cat /sys/class/graphics/fb0/modes |
| 17:34 | topi`_ | root=/dev/mmcblk0p2 console=ttymxc0,115200 console=tty0 ro rootwait |
| 17:34 | topi`_ | forgot consoleblank=0 |
| 17:35 | topi`_ | hmm, it might be that the cmdline is missing the "video=mxcfb0" or whatever it was |
| 17:35 | jnettlet | it should just pick that up from the devicetree |
| 17:36 | topi`_ | it seems I had fuddled with another framebuffer in my uEnv.txt, so that is probably the reason |
| 17:37 | topi`_ | I uncommented the old line now |
| 17:37 | topi`_ | and now, ho behold, it works and I have the 1920x1080 screen back! |
| 17:37 | topi`_ | sorry for bothering you with this mundane issue :( |
| 17:41 | jnettlet | no worries glad it got sorted. |
| 17:41 | topi`_ | it was just annoying, since I use the text console for running emacs on the device ;) |
| 17:42 | topi`_ | emacs is a lot more useful on a 1920x1080 screen than a 640x480 one :) |
| 17:48 | topi`_ | ooops, a black screen after reboot :/ |
| 17:48 | topi`_ | oh, maybe it was just that the watchdog took 60+ seconds to reboot the system (but the HDMI had already gone down) - now I got the solidrun logo |
| 20:09 | vpeter | jnettlet: Is is possible to move mmc3 to mmc0 somehow in kernel? |
| 20:09 | jnettlet | you can create aliases in the device-tree |
| 20:09 | vpeter | I also got response for vt1613 driver on udoo. There should be some changes in fsl_ssi.c but didn't look that yet. |
| 20:10 | vpeter | Yes, trying alias. Maybe I just missed correct number. Let's test once more. |
| 20:12 | vpeter | Alias working. Thanks. |
| 21:19 | vpeter | jnettlet: I'm trying to use snvs rtc power-off driver you add. But doesn't work (driver not probed). I add compatible lines after alias. Is this correct? Also enabled POWER_RESET_SNVS. |
| 21:26 | vpeter | False alarm - it is working. Was uploading wrong kernel. |
| 21:26 | vpeter | Can I assume that POWER_RESET_SNVS will be enabled in kernel config by default? |
| 21:36 | jnettlet | vpeter, i can add it for you. |
| 21:38 | vpeter | Yes please :) |
| 21:38 | vpeter | I'm using this for TBS Matrix. |
| 21:51 | jnettlet | Okay. |