ftg has quit [Read error: Connection reset by peer]
apritzel has quit [Ping timeout: 480 seconds]
szemzoa has joined #linux-sunxi
szemzoa has quit [Ping timeout: 480 seconds]
cnxsoft has joined #linux-sunxi
szemzoa has joined #linux-sunxi
szemzoa has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has joined #linux-sunxi
junari_ has joined #linux-sunxi
junari__ has joined #linux-sunxi
junari_ has quit [Ping timeout: 480 seconds]
junari__ is now known as junari
<junari>
apritzel: I checked with osciloscope, 1200 mv (70 step) set working
Danct12 has joined #linux-sunxi
szemzoa has joined #linux-sunxi
szemzoa has quit [Ping timeout: 480 seconds]
szemzoa has joined #linux-sunxi
szemzoa has quit [Remote host closed the connection]
cnxsoft1 has joined #linux-sunxi
cnxsoft has quit [Ping timeout: 480 seconds]
montjoie_ is now known as montjoie
junari has quit [Ping timeout: 480 seconds]
gosha has joined #linux-sunxi
gosha has quit []
apritzel has joined #linux-sunxi
szemzoa has joined #linux-sunxi
szemzoa has quit [Ping timeout: 480 seconds]
bauen1 has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has quit []
apritzel has quit [Ping timeout: 480 seconds]
szemzoa has joined #linux-sunxi
szemzoa has quit [Ping timeout: 480 seconds]
junari has joined #linux-sunxi
junari_ has joined #linux-sunxi
junari has quit [Ping timeout: 480 seconds]
apritzel has joined #linux-sunxi
pabs has quit [Remote host closed the connection]
<apritzel>
junari_: very nice, thanks! I will email Martin about it
junari has joined #linux-sunxi
junari_ has quit [Ping timeout: 480 seconds]
junari_ has joined #linux-sunxi
junari has quit [Read error: No route to host]
ftg has joined #linux-sunxi
junari_ has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has joined #linux-sunxi
szemzoa has joined #linux-sunxi
szemzoa has quit [Ping timeout: 480 seconds]
cnxsoft1 has quit []
cnxsoft has joined #linux-sunxi
grming has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
JohnDoe7 has joined #linux-sunxi
junari has joined #linux-sunxi
JohnDoe_71Rus has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has joined #linux-sunxi
JohnDoe6 has joined #linux-sunxi
JohnDoe7 has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has quit [Ping timeout: 480 seconds]
grming has quit [Quit: Konversation terminated!]
JohnDoe_71Rus has joined #linux-sunxi
sunshavi has joined #linux-sunxi
JohnDoe6 has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has joined #linux-sunxi
JohnDoe3 has joined #linux-sunxi
cnxsoft has quit []
JohnDoe3 has quit [Read error: Connection reset by peer]
JohnDoe_71Rus has quit [Ping timeout: 480 seconds]
szemzoa has joined #linux-sunxi
cnxsoft has joined #linux-sunxi
szemzoa has quit [Ping timeout: 480 seconds]
<junari>
Trying to run LPDDR3 on H616. Faced with a situation that the memory does not pass the functions mctl_auto_detect_rank_width() and mctl_auto_detect_dram_size()
apritzel has joined #linux-sunxi
<junari>
In this case in vendor's SPL actions that are not entirely clear to me
<junari>
Registers 0x70000000, 0x80000000 0xa0000000 are written.
<apritzel>
what "registers" do you mean, exactly? The last two addresses are in DRAM. There are algorithms that write into DRAM to look for aliasing, but 0x70000000 does not fit in there
<junari>
Yes, that's right, it's RAM
<junari>
from 0x40000000 to 0x13FFFFFFF
<junari>
tangled up in zeros
ftg has quit [Ping timeout: 480 seconds]
<junari>
Looks like vendor SPL simply writes to certain areas of memory to find out its size
<MoeIcenowy>
junari: in fact we are also just writing to certain address to detect the size
<MoeIcenowy>
because we're detecting the wrapping up
digetx has joined #linux-sunxi
<MoeIcenowy>
my computer principle lesson knowledge tells me DRAMs has rows and columns
<MoeIcenowy>
(and modern DRAMs has banks / bankgroups (bankgroups are so modern that they come at (LP)DDR4)
<MoeIcenowy>
the principle of size auto detect is to set 1 of the 3 parameters to the maximum, and others to the minimum
<MoeIcenowy>
and detect wrapping up
<MoeIcenowy>
and decrease the testing parameter (which is set to the maximum) unless no wrapping up happens
<junari>
MoeIcenowy: Yes, I saw it in the driver code