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
luka177 has joined #linux-amlogic
jacobk has joined #linux-amlogic
montjoie has quit [Ping timeout: 264 seconds]
montjoie has joined #linux-amlogic
vagrantc has joined #linux-amlogic
vagrantc has quit [Quit: leaving]
hexdump0815 has quit [Ping timeout: 276 seconds]
hexdump0815 has joined #linux-amlogic
buzzmarshall has quit [Quit: Konversation terminated!]
<f_> So..despite still having DRAM issues, writing to refr_ctrl1 actually did make the thing more stable.
<f_> I went from "crashes after boot" to "crashes when heavily making use of the RAM".
<f_> Once again, regression D:
<f_> b294bfb5aaed28e26f9f450a18dcc0f65593872d doesn't have any of that
<f_> (as I've said before)
<f_> But that means I can still boot to i3wm or MATE and run neofetch :D
<f_> contrary to what I said before, the issue is *not* channel-related, sort-of.
<f_> It is related to the last few bits of init code to finish bringing up DRAM, and the reason why I couldn't reproduce on GXL is..
<f_> well..
<f_> that code is different on GXL!
* f_ facepalms.
<f_> Anyway it's still less severe than before :P
<f_> so it's actually slightly usable.
<f_> just make sure to not use all of the RAM :P
psydroid has joined #linux-amlogic
<f_> mmm...
<f_> yay
<f_> Second regression introduced!
<f_> Issues I'm having now are coming from a different source..
Consolatis has quit [Ping timeout: 260 seconds]
Consolatis has joined #linux-amlogic
linkmauve has joined #linux-amlogic
camus has quit [Quit: camus]
vagrantc has joined #linux-amlogic
zsoltiv_ has joined #linux-amlogic
buzzmarshall has joined #linux-amlogic
psydroid has quit [Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/]