01:07 <bashintosh> one thing I really don't get - why would the parameter file (RK3288, U-Boot) need to change between Android 4.4 and 5.x? I am referring particularly to the partitions addresses - with Lollipop (5.1) on the Firefly I am having issues as the "internal storage" does not get mounted/seen. It's driving me insane.. :)

03:26 <bashintosh> solved internal storage issue - /mnt/internal_sd wasn't getting mounted due to a wrong partition parameter in fstab.rk30board.bootmode.emmc (voldmanaged=internal_sd:15,noemulatedsd must be voldmanaged=internal_sd:14,noemulatedsd).

07:53 <rperier> hi, I was wondering something. the "loadaddr" parameter for an uboot image format, is it platform dependent or independent? (that's called UIMAGE_LOADDR in the kernel build system) or you might use the same address between two platforms ?

07:54 <rperier> the way that uboot handles addresses is still a complicated part for me

08:02 <sjoerd> uImage

08:02 <sjoerd> boo

08:02 <sjoerd> anyway

08:03 <sjoerd> The loadaddr is where u-boot sticks the kernel

08:03 <sjoerd> In physical memory

08:03 <sjoerd> Which for linux needs to be within the first 128mb of memory

08:04 <sjoerd> So it depends on the SoC (tyipcally) where that is as your physical memory doesn't have to start at address 0

08:05 <sjoerd> https://www.kernel.org/doc/Documentation/arm/Booting is useful as a background here especially section 6

08:41 <rperier> sjoerd: yeah this is what I thought, it depends on the topology of your DDR. Oh, thanks for the doc, it seems to be what I was looking for :)

08:41 <sjoerd> well more the memory controller rather then the DDR

14:56 <philhug> https://github.com/linux-rockchip/rkflashtool/pull/4

20:25 <BorgCuba> naobsd, have you ever tried mali fb drivers?

20:25 <BorgCuba> I am asking since I get unexpected low performance (like a score of 39 in glmark2).