narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - official channel moved from Freenode - publicly logged on https://libera.irclog.whitequark.org/linux-amlogic
camus has quit [Remote host closed the connection]
camus has joined #linux-amlogic
camus has quit [Ping timeout: 268 seconds]
camus has joined #linux-amlogic
jacobk has quit [Ping timeout: 240 seconds]
Daanct12 has joined #linux-amlogic
buzzmarshall has quit [Quit: Konversation terminated!]
Daanct12 has quit [Ping timeout: 268 seconds]
Daanct12 has joined #linux-amlogic
Daanct12 has quit [Ping timeout: 246 seconds]
Daanct12 has joined #linux-amlogic
vagrantc has quit [Quit: leaving]
camus has quit [Quit: camus]
elastic_dog has quit [Ping timeout: 246 seconds]
elastic_dog has joined #linux-amlogic
Daanct12 has quit [Quit: WeeChat 3.8]
f_ has joined #linux-amlogic
<f_> Hey all.
<f_> About the RAM init..how should I implement it? Should I try to parse an acs.bin in the build process or try RAM timings that work on the most boards?
<f_> I know some RAM timings from some boards work on others (The RAM timings for the NanoPi-K2 and the WeTek Hub all work for me), but others don't seem to work at all on my set-top box (those for the p201, for example)
<narmstrong> f_: no idea, how this is done on other platforms ? Perhaps add some DT files per boards with all the ram timings and use that ?
<f_> Possibly?
<f_> This is something I need to work on after I get BL2 to work. But now, for kicks and giggles let's just hardcode all that.
<f_> Still. Would be nice to have TF-A's BL2 working on the most boards possible.
<f_> Maybe we could also have a tool that generates a header file containing timings and use it?
<f_> At this point I think I'll just port Amlogic's RAM init code and be done with it.
jacobk has joined #linux-amlogic
jacobk has quit [Ping timeout: 240 seconds]
exkcmoeAdmin[m] is now known as exkcnoe[m]
<f_> Ok
<f_> Amlogic's ddr.c is basically...a bazillion wr_reg()
<f_> And wanna know what wr_reg does?
<f_> wr_reg(address, data) is equivalent to..... (*((volatile unsigned *)address))=(data)
<f_> I mean...why did they feel like wanting to have a macro for this?
jacobk has joined #linux-amlogic
jacobk has quit [Client Quit]
f__ has joined #linux-amlogic
f_ has quit [Killed (NickServ (GHOST command used by f__))]
f__ is now known as f_
jacobk has joined #linux-amlogic
<f_> https://git.vitali64.duckdns.org/misc/trustedfirmware-a.git/commit/?h=wip/gxbb&id=4fb92f3648307c1ffd1c24a8e5f6d73cd09ae6fa
<f_> I imported Amlogic's RAM init code into TF-A. Doesn't compile yet even after my modifications (which are supposed to make it independent from their U-Boot tree)
<f_> I'll investigate tomorrow, most likely.
<f_> At least I know better how Amlogic's RAM init code works.
<f_> It mostly just writes at specific addresses stuff.
<f_> I imported them at drivers/amlogic/ddr
<f_> https://git.vitali64.duckdns.org/misc/trustedfirmware-a.git/tree/drivers/amlogic/ddr/defunctions.h?h=wip/gxbb&id=4fb92f3648307c1ffd1c24a8e5f6d73cd09ae6fa I made a header file
<f_> Anyways, have to go. Cya.
f_ has quit [Quit: disconnect..]
jacobk has quit [Ping timeout: 240 seconds]