09:04 <Ely> narmstrong: for sure :)

09:07 <Ely> Quick question, I've been using https://github.com/akuster/meta-odroid to build poky for my C1, but I just realized it's not the ""official"" meta-meson. It is however very up to date and working quite well (at leastfor odroids). What's the reasoning for not using this as a base ?

09:08 <narmstrong> Because it’s odroid centric

09:08 <narmstrong> Meta-meson is amlogic centric for mainline only

09:09 <Ely> fair enough

09:11 <narmstrong> iin the fact we share some recipes !

09:44 <gab> Hi, I have a question about DDR detection in the amlogic s912's bootloader: I got a box advertised as having 3GB DDR (beelink GT1 ultimate), but on serial console BL2 says "DDR3 chl: Rank0+1 @ 912Mhz - PASS" followed by "Rank0: 1024MB(auto)-2T-13 / Rank1: 1024MB(auto)-2T-13", while Rank0 should have 2048MB

09:45 <gab> I checked the DDR chip references on the board and they look like proper DDR4 chips with correct sizes

09:45 <gab> could there be something wrong on the box's flash, or did I just buy a box with fake DDR chips ?

09:46 <gab> from looking at freaktab.com forums, it appears this issue is quite common with this board model

09:48 <gab> also, when I load a 3GB device tree, it resets immediately, same thing if I try to access addresses above 0x80000000 with md.b in uboot

09:50 <gab> another strange thing is that the kernel's /proc/meminfo shows 2840744 MemTotal, but zoneinfo says 524032 spanned pages

09:50 <gab> (and dmesg "Memory:" line shows only 2GB)

09:56 <narmstrong> the DDR init initialized bby the FIP fw loaded before u-boot, and is dependant on the board config

09:56 <narmstrong> check on the PCB you have 3GB !

09:59 <gab> I checked the DDR chips on the PCB, and they look like legit DDR4 chips: 2x K4A4G16 5WE BCRC + 2x K4A8G16 5WB BCRC

10:01 <gab> someone else seems to have the same issue with a similar serial number to mine: http://freaktab.com/forum/tv-player-support/beelink-aa/687630-can-t-locate-f-w-for-beelink-gt1-ultimate-with-questionable-serial-number

10:03 <gab> so if I understand well, this may just be a software config mistake made by the OEM ?

10:05 <gab> the MemTotal value looks fake though, that makes it very suspicious

10:11 <Elpaulo_m> gab: There may be a manufacturer error. Can be an individual flashing for the defect of components. In addition, the kernel is often fixed to display the correct size.

10:11 <gab> okay

10:12 <gab> so is there any way to fix that through flashing ?

10:12 <gab> and if possible without bricking the box while trying do to it ;)

10:14 <gab> I checked the stock firmware's DDR.USB file, and it matches the one on my board's emmc

10:15 <gab> even uboot says "DRAM: 3GiB", appears to select the 3G dtb, but when I check in /proc/device-tree after the android image has booted, linux,usable-memory is 0x7ff00000 (ie. the one from the 2g dtb)

10:15 <gab> so I doubt this is individual flashing

10:21 <Elpaulo_m> if you remove the power from emmc or another signal, you can experiment with booting with sd. The firmware can always be filled with USB. I have s905, but in your case I think, too, there is no problem with recovery and firmware. IMHO

10:25 <Elpaulo_m> gab.I'm not an expert on this platform, but it would be convenient for everyone to see a link to the full log of your system's boot.

10:31 <gab> sure

10:33 <gab> here it is

10:33 <gab> https://pastebin.com/6tHq12V4

10:34 <gab> also /proc/meminfo and /proc/zoneinfo: https://pastebin.com/SdrGeFz6

10:37 <gab> and /proc/iomem: https://pastebin.com/u6E3Kt2E

10:39 <narmstrong> "DRAM: 3 GiB"

10:39 <narmstrong> dtb 2 soc: gxm plat: q201 vari: 3g

10:39 <narmstrong> Find match dtb: 2

10:40 <gab> that's right, uboot appears to display fake info

10:40 <narmstrong> You have 3GiB but a bunch of memory zones are reserved

10:41 <gab> it's just 3GiB in uboot

10:41 <gab> the dtb actually selected is 2GB

10:41 <gab> q201:/ # hexdump -C /proc/device-tree/memory@00000000/linux,usable-memory

10:41 <gab> 00000000 00 00 00 00 00 10 00 00 00 00 00 00 7f f0 00 00 |................|

10:41 <gab> 00000010

10:42 <narmstrong> 2840744 kB is 2,7GiB

10:42 <narmstrong> the ~300MiB missing is reserved for decoders, ...

10:42 <gab> available memory on line 205 says 2092032

10:42 <gab> that's just not consistent

10:42 <narmstrong> ?

10:42 <gab> also I loaded a dtb without reserved memory, that extra 1GB is just not there to be found

10:44 <gab> I cross-checked in /proc/zoneinfo as well, and it just doesn't add up

10:45 <gab> everything tells me there's just 2GB and that the kernel's been patched to display a fake value in MemTotal

10:45 <gab> and uboot lies about the dtb being loaded as well

10:49 <gab> there's also this: https://pastebin.com/cfvmTgFA

10:49 <gab> that dtb_read_shortcut line looks suspicious

14:11 <dlan> jbrunet: do you prefer I send the aoclk series along with the patch - drop the CLK_IGNORE_UNUSED flag? but queue the patch for another cycle (or whatever make it goes in *after* the DT patch which change UART_AO clk)

14:48 <jbrunet> dlan: yes, please do