**** BEGIN LOGGING AT Tue Aug 29 03:00:01 2017
Aug 29 10:19:29 <jithu> hi
Aug 29 10:27:31 <jithu> i am working on beaglebone black. so by mistake i changed something in the uEnv.txt in boot directory. (##BeagleBone Black: ##Disable HDMI/eMMC cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G). so after doing this after reboot when i am trying to connect it to my PC with usb cable, the beaglebone is not getting detected and not showing under COM ports in the device manager.
Aug 29 10:31:54 <jithu> Hi sir
Aug 29 10:32:11 <jithu> hello
Aug 29 10:38:17 <sriram> hi devicetree overlay can be used for beagleboard-x15
Aug 29 12:06:37 <moondeck> hi
Aug 29 12:06:46 <moondeck> so, is BBB JTAG 3.3V or 1.8V?
Aug 29 12:07:00 <moondeck> cant seem to find info on that anywhere
Aug 29 12:09:20 <moondeck> oh nvm, the schematic says 3v3
Aug 29 12:09:57 <moondeck> at least the it has the Vref at that
Aug 29 12:23:30 <cyberguy> hi all , is there any way to get BBB GPIO interrupt at user space?
Aug 29 12:23:59 <cyberguy> (i need 40ms response time to signal at some GPIO when rising from 0 to 1)
Aug 29 13:31:19 <alan_o> cyberguy: Have a look at https://www.kernel.org/doc/Documentation/gpio/sysfs.txt
Aug 29 13:31:25 <alan_o> cyberguy: specifically "edge"
Aug 29 14:01:33 <bfederau> hi. I have a Chalkboard HDMI display with a resolution of 1366x768. I'm running Qt 5.9.2 and I have the following issues. First of all the QML App is always started in1280x720 and with wrong colors. I already set the DefaultPixelFormat=RGB565  with no effect. Any hints what I can try to get the right colors and resolution?
Aug 29 14:02:44 <bfederau> btw. fbset prints the correct resolution 1366x768 but the QML app uses 1280x720
Aug 29 14:03:56 <bfederau> oh I forgot to say that I use a Beaglebone Black
Aug 29 14:54:49 <bfederau> I think I have found the answer to my issue: http://processors.wiki.ti.com/index.php/Processor_Linux_SDK_Graphics_and_Display#AM3_Beagle_Bone_Black_Board_Configuration
Aug 29 16:16:49 <Babak> in am335x_pru_package/pru_sw/app_loader/interface/prussdrv.c
Aug 29 16:18:51 <Babak>  prussdrv_pru_write_memory() function scope : *(pruramarea + i + wordoffset) = *(memarea + i);
Aug 29 16:19:08 <Babak> why wordoffset is added to pruramarea which holds the the address of the instruction memory.but according to this guide
Aug 29 16:19:31 <Babak> http://processors.wiki.ti.com/index.php/PRU_Linux_Application_Loader_API_Guide
Aug 29 16:19:50 <Babak> wordoffset is the offset from *memarea and I think wordoffset is to be added to memarea instead , otherwise we are missing some parts of the instruction memory.
Aug 29 16:58:52 <zmatt> bfederau: maybe the hdmi display is misreporting the resolution or something? try using the video= kernel parameter to force resolution
Aug 29 16:59:04 <zmatt> as for colors, I resorted to patching qt for that
Aug 29 17:01:16 <zmatt> oh, in my case that was for the eglfs_kms backend though
Aug 29 17:01:24 <zmatt> maybe the linuxfb backend has the same issue
Aug 29 17:03:47 <zmatt> in case it's of any use, this is what I did -> https://github.com/mvduin/qtbase/commit/49868289a731
Aug 29 17:03:54 <zmatt> roughly
Aug 29 17:06:50 <zmatt> I was actually too lazy to recompile it so I patched the binary... and I ended up dropping some parts of that patch (the color depth of offscreen buffers can be left alone)
**** ENDING LOGGING AT Wed Aug 30 03:00:00 2017