12:14 <MaDMaLKaV> for compiling a dts , do I need to compile it against the kernel it will be runt with?

14:06 <chewitt> no, it can be compiled on any kernel

14:06 <chewitt> it can only be used with compatible kernels though

14:44 <MaDMaLKaV> I see

14:45 <MaDMaLKaV> anyway, I'm going to build from zero so I get a better picture of all the process, I think it will come handy in the near future

14:46 <MaDMaLKaV> I have tried several dtb files and most stuff seems to be supported on one or another, and the info on the devicetree filesystem matches the dts I got from another user -I wasn't able to dump a dts myself ...-

14:46 <MaDMaLKaV> so this will probably not a very dificult task, just I'm not very familiar with this process

14:46 <MaDMaLKaV> thanks for the info , by the way :)

14:48 <MaDMaLKaV> in example, now after cloning the files I see references to the box-trn9 or box-z28 devices , but can't find anything about those devices on the git files. I suppose the missing files are provided by some of the dependencies checked during first make

14:48 <MaDMaLKaV> so I will need to get those, and after that see how to add my dts, then compile again

14:55 <MaDMaLKaV> there is no tool to check if a dts and a kernel are a good match or not, right_

14:55 <MaDMaLKaV> ?

15:05 <chewitt> nope

15:05 <chewitt> but if you're working on RK devices; everything you find will be using their 4.4 kernel

15:05 <chewitt> so you shouldn't find too much diversity

15:07 <MaDMaLKaV> even so, the dts I got for the device won't boot once compiled to dtb. Perhaps I should take another approach, compiling the available dts, see the one that looks a better base to start, and add params from the dts to that one

15:08 <MaDMaLKaV> that dts was from android anyway so probably it is normal it won't boot

15:08 <chewitt> android dts won't boot linux

15:08 <MaDMaLKaV> I expected so, yeah

15:09 <chewitt> things are similar, but not the same

15:10 <MaDMaLKaV> but I have tried several different dtbs with librelec stable, nightly and balbes150 , with different dtbs, and got different combinations of working/not working stuff. the working ones always seemed to match pretty closely the info on this dts. So if I take one i.e. with working ethernet and modify the wifi and bt and ir part, I hope I would be able to get a fully working one

15:10 <chewitt> the android dts probably has references to things you need, but the syntax of bits may/will be different

15:11 <MaDMaLKaV> I'm 90 percent sure I must have all or almost all info I need, I just need to practice and learn a little to be able to process that info correctly

15:12 <MaDMaLKaV> sintax? like in those alias it seems to be used by dts / dtsi files? or you refer to different endianess or something like that?

15:13 <MaDMaLKaV> lemme show you what I mean , doing a pastebin...

15:14 <MaDMaLKaV> https://pastebin.com/KtMKFiHN

15:17 <chewitt> kernel has extensive documentation on device-tree and what's allowed

15:18 <chewitt> i.e. mandatory and optional content

15:18 <MaDMaLKaV> OK, will look for that

15:19 <chewitt> the important thing is to look at the documentation at the version you're using .. as device-tree is always kernel version specific

15:19 <chewitt> for fixing wifit/bt it should be a copy/paste job tho

15:21 <MaDMaLKaV> yeah, my plan was more or less getting that working in a "dirt" way , and after that trying to get the dts file worked into a nice, standards compliant dts so it can be included in the build process. But as I said, there are so many uncertainties for me right now so I'm trying to get a better idea of the whole process at the moment without going much deep into any of the parts

15:21 <zzlatev> Stefan Saraev?

15:23 <MaDMaLKaV> I could really use the mx10 dts source file , as this one seems to be the one better working with the device, gonna try to locate it

15:24 <zzlatev> Hi all

15:24 <MaDMaLKaV> hi

15:25 <zzlatev> I have a problem with subtitles on Kodi 18.1

15:25 <zzlatev> When I play a DVD my subtitles are unreadable because the subtitle box shows as all white.

15:26 <zzlatev> I use Kodi 18.1 on Mint Mate 19

15:26 <MaDMaLKaV> so, you don't use LibreElec?

15:41 <chewitt> use #kodi-linux for issues with Kodi on other platforms

15:43 <zzlatev> Hi guys

15:43 <MaDMaLKaV> lol, I can compile the android-extracted dts but I try to do it with one of the libreelec ones I get a parse error. This seems like a good sign I need to go to get some fresh air

15:44 <zzlatev> When I play a DVD my subtitles are unreadable because the subtitle box shows as all white. Any ideas what to do?

15:44 <zzlatev> I use kodi 18.1 on Mint Mate 19 and Libreelec

15:45 <zzlatev> https://imgur.com/a/fai9vod

15:45 <MaDMaLKaV> if you have that problem in both Mint and Libreelec, it seems a Kodi problem. as chewitt said, it will be better to ask in #kodi-linux

15:46 <chewitt> ^ as he said

15:46 <zzlatev> Thanx guys!

15:46 <MaDMaLKaV> yw

15:47 <MaDMaLKaV> I'm going to take some fresh air, I will try to understand why dtc complains about the #include "rk3328.dtsi" when I get back

19:29 <MaDMaLKaV> OK, so seems I need the kernel to build the dts in the end, the dts calls some dtsi that call some includes...

19:29 <MaDMaLKaV> ls

19:29 <MaDMaLKaV> ouch , wrong window

19:49 <MaDMaLKaV> ummm, trying to figure out which CROSS_COMPILE option is set for rk3328 , that way I can build the dtbs only and save some time