14:53 <vakkov_> Hello, guys! Is there a TO DO list somewhere

15:11 <chewitt> item #1 on the to-do list is .. create a to-do list :)

18:19 <vakkov_> chewitt: cool, what's left to be done :D i see someone is working on a kernel driver?

18:27 <urjaman> hanetzer: you happen to know off-hand how the 2GB vs 4GB stuff is supposed to work on the C201 kernel?

18:28 <urjaman> asking because i just booted my card on the 4GB machine and it found 2GB of ram :P

19:44 <mmind00> urjaman: the original coreboot would supposedly update the devicetree with the correct amount of ram ... are you on u-boot or such?

19:47 <urjaman> stock coreboot+depthcharge ...

19:48 <urjaman> (but the kernel i booted was my "old" 4.19.0, maybe something in the devicetree confused it or ... hmm...)

19:48 <mmind00> urjaman: maybe check proc/devicetree/foobar for memory node(s)

20:20 <urjaman> hmm there's a "memory" and a "memory@0"

20:22 <urjaman> "memory" being 4GB and "memory@0" being 2GB (if i read hexdump of "reg" right in them)

20:24 <mmind00> urjaman: I did expect that somehow :-) ... see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=672e60b72bbe7aace88721db55b380b6a51fb8f9

20:26 <mmind00> urjaman: so you seem to have selected the kernel version from that small timeframe where we had the memory@0 node in the devicetree ... (the fix should be in later 4.19.x releases)

20:27 <urjaman> yeah i was just checking that the fix is in 4.20 (it is) so i can just upgrade the kernel (as i was planning to anyways)

20:29 <urjaman> i didnt notice this when i was making that kernel because i was using my 2GB C201 for dev