| 07:54 | jnettlet | vpeter, where are we with the audio patches? |
| 08:56 | vpeter | jnettlet: same as few days back. Waiting for answer from original author. This is way to much for me to understand how it works. |
| 08:56 | vpeter | I'm preparing dts for one other system. |
| 08:58 | jnettlet | vpeter, okay I will try and get it merged. |
| 09:02 | vpeter | I assume there are some fundamental changes regarding ac97 or something similar. Because all other commits are applied without a problem to your kernel. |
| 09:02 | vpeter | Just doesn't work. |
| 09:03 | jnettlet | it might just be some small api change. Usually it can just take a bit of massaging. |
| 09:03 | vpeter | If you know where and how :-) |
| 09:03 | vpeter | I also have to fix LVDS part for two my screens. |
| 09:04 | vpeter | You have any newer image build? |
| 09:05 | jnettlet | no, I am stuck fixing yocto builds right now. |
| 09:05 | vpeter | Because with mine Kodi doesn't start. |
| 09:05 | jnettlet | I am going to try and make some time tonight to get back to OE. |
| 09:05 | jnettlet | basically every distro decided they were going to break stuff at the same time. |
| 09:05 | vpeter | Could you zip/tar your whole openelec folder (without sources and build folder)? With all other changes you did in. |
| 09:07 | jnettlet | I will be making publishing my repo soon. I have access to upload my source tarballs to OE's servers now so I can do proper pull requests |
| 09:07 | vpeter | Great. |
| 09:16 | warped-rudi | vpeter: Which udoo model are you using? |
| 09:17 | vpeter | Both. And both displays. |
| 09:17 | vpeter | I mean I have them :) |
| 09:18 | warped-rudi | I wondering if the audio driver not loading issue happens on both the imx6dl and the imx6q |
| 09:19 | vpeter | I would say both. But was testing only on quad. |
| 09:19 | vpeter | From what I understand the codec vt1613 is loaded. But machine driver is not. |
| 09:20 | vpeter | Over weekend will try again. |
| 09:22 | vpeter | There has been issues when I was porting driver from udoo kernel to current solidrun's. |
| 09:22 | jnettlet | vpeter, is lvds working on the udoo with the new kernel? |
| 09:23 | vpeter | Not tested yet. Because I don't have kodi visible. That's why I'm waiting for whole openelec package. |
| 09:23 | jnettlet | but you should have console output. |
| 09:24 | jnettlet | does their u-boot output to lvds or only serial? |
| 09:25 | vpeter | u-boot only serial. There is some code but not sure if work. |
| 09:44 | warped-rudi | vpeter: Line 101/102 in the machine driver look suspicous. Maybe something to investigate at the weekend... |
| 09:50 | vpeter | You mean of_machine_is_compatible()? This is fixed. |
| 09:51 | jnettlet | vpeter, do you use your usb devices very much on the Udoo? We have been experiencing disconnects on both the SolidRun and Novena board. |
| 09:53 | vpeter | Actually I don't use udoo that much. That's why I didn't see this issue. |
| 09:54 | vpeter | This happpens regulary? |
| 09:54 | vpeter | Could I make some test to reproduce? |
| 09:55 | jnettlet | yeah pretty regularly. I think it is mostly fixed by disabling the new TT scheduler, and then also tweaking the phy to increase the tolerance of the signal voltage drop before detecting a disconnect |
| 10:14 | warped-rudi | Yes, I meant this of_machine_is_compatible() thing. IMHO, a strange construct anyway... |
| 10:19 | vpeter | Why strange? It checkes the system to run only on udoo. |
| 10:46 | warped-rudi_ | Why does it have to check? If a device tree pulls it in, it should load. No matter if the hardware is called udoo or not. |
| 10:54 | vpeter | Can kernel dynamically load it if there is reference in device tree? |
| 10:56 | vpeter | Anyway, some of things are way of my head (not on same level as you guys). |
| 22:34 | ngochai | Hi guys, is there a way to get hardware info (like board/hw serial number...) of my hummingboard i2ex? dmidecode does not work and lshw just give me basic info |
| 22:50 | vpeter | ngochai: cat /sys/fsl_otp/HW_OCOTP_CFG0/1 for serial hi/lo part. |
| 22:50 | vpeter | also there is /sys/bus/soc/devices/soc0/ |
| 23:04 | ngochai | vpeter, I cat all files in /sys/fsl_otp/HW_OCOTP_* and there's nothing |
| 23:06 | ngochai | I build my kernel though, did I miss something? |
| 23:09 | ngochai | I do have CONFIG_FSL_OTP=y in my kernel though |
| 23:13 | vpeter | You have file /sys/fsl_otp/HW_OCOTP_CFG0? |
| 23:17 | ngochai | vpeter, yes |
| 23:18 | ngochai | cat /sys/fsl_otp/HW_OCOTP_CFG0 gives me nothing |
| 23:21 | vpeter | this is higher part of serial |
| 23:21 | vpeter | HW_OCOTP_CFG1 is lower part |
| 23:22 | ngochai | vpeter, but it does not show anything when I do 'cat /sys/fsl_otp/HW_OCOTP_CFG0' |
| 23:24 | vpeter | I see. I think it should show something. No idea why doesn't. |
| 23:26 | ngochai | oh I tried it on my dualcore hummingboard and it's showing something |
| 23:26 | ngochai | the one shows nothing is quadcore hummingboard |
| 23:27 | ngochai | sorry about the confusion |
| 23:27 | ngochai | so /sys/fsl_otp/HW_OCOTP_CFG0 and /sys/fsl_otp/HW_OCOTP_CFG1 is CPU id? |
| 23:27 | ngochai | or board id? |