00:11
luka177 has joined #linux-amlogic
00:13
luka177 has quit [Read error: Connection reset by peer]
00:13
luka177 has joined #linux-amlogic
00:31
djrscally has quit [Ping timeout: 245 seconds]
00:45
Lyude has quit [Quit: Bouncer restarting]
00:45
Lyude has joined #linux-amlogic
00:53
hexaheximal has joined #linux-amlogic
00:54
hexaheximal has quit [Remote host closed the connection]
01:02
GNUtoo has quit [Ping timeout: 240 seconds]
01:15
GNUtoo has joined #linux-amlogic
01:19
montjoie has quit [Ping timeout: 264 seconds]
01:20
montjoie has joined #linux-amlogic
01:36
jkl has quit [Quit: Gone.]
01:37
jkl has joined #linux-amlogic
01:55
luka177 has quit [Ping timeout: 264 seconds]
02:00
luka177 has joined #linux-amlogic
02:02
Consolatis has quit [Ping timeout: 245 seconds]
02:02
kbingham has quit [Remote host closed the connection]
02:04
kbingham has joined #linux-amlogic
02:04
Consolatis has joined #linux-amlogic
02:11
GNUtoo has quit [Remote host closed the connection]
02:12
GNUtoo has joined #linux-amlogic
02:17
GNUtoo has quit [Remote host closed the connection]
02:17
GNUtoo has joined #linux-amlogic
03:03
vagrantc has joined #linux-amlogic
03:23
vagrantc has quit [Quit: leaving]
03:59
f_[xmpp] has quit [Ping timeout: 264 seconds]
04:00
exkc has quit [Ping timeout: 264 seconds]
04:37
hexdump0815 has quit [Ping timeout: 260 seconds]
04:38
hexdump0815 has joined #linux-amlogic
05:04
buzzmarshall has quit [Quit: Konversation terminated!]
05:40
camus has joined #linux-amlogic
06:10
vagrantc has joined #linux-amlogic
08:18
vagrantc has quit [Quit: leaving]
09:02
f_[xmpp] has joined #linux-amlogic
11:16
psydroid has joined #linux-amlogic
13:02
Consolatis has quit [Ping timeout: 245 seconds]
13:03
Consolatis has joined #linux-amlogic
13:24
ungeskriptet has joined #linux-amlogic
13:41
zsoltiv__ has quit [Ping timeout: 264 seconds]
13:52
buzzmarshall has joined #linux-amlogic
14:16
luka177 has quit [Ping timeout: 255 seconds]
15:38
jacobk has quit [Ping timeout: 240 seconds]
15:52
hexaheximal_ has joined #linux-amlogic
17:26
<
f_ >
Alright, so let me reiterate.
17:27
<
f_ >
* GXBB boots, but due to a regression it kernel panics after a while (last known-working commit: b294bfb5aaed28e26f9f450a18dcc0f65593872d)
17:28
<
f_ >
* GXL boots, works perfectly fine AFAICT
17:28
<
f_ >
* On both eMMC support doesn't work
17:28
<
f_ >
* USB support is on TODO
17:28
<
f_ >
* NAND will most likely not work
17:28
<
f_ >
* SPI is untested
17:28
<
f_ >
* DDR4 support in GXL is inexistant
17:29
<
f_ >
Primary issue I'd like to solve is that GXBB panic issue
17:30
<
f_ >
then eMMC (will probably remove bits and pieces of the MMC driver for SPL as bl2.bin doesn't do MMC init anyway)
17:30
<
f_ >
Rest can be worked on after upstreaming.
18:32
<
f_ >
I was a bit sceptical about b294bfb5aaed28e26f9f450a18dcc0f65593872d actually working fine, but running `stress-ng` so that it stress tests RAM doesn't b0rk the whole thing.
18:44
kenny has quit [Quit: WeeChat 4.1.2]
18:49
jacobk has joined #linux-amlogic
19:03
hexaheximal_ has quit [Read error: Connection reset by peer]
19:04
jacobk has quit [Ping timeout: 268 seconds]
19:40
kenny has joined #linux-amlogic
19:45
<
f_ >
Ran it for a while, it uses ~80% of the RAM, so ~1.4 GB
19:45
<
f_ >
I should try the same on lepotato perhaps.
19:56
psydroid has joined #linux-amlogic
20:31
hexdump0815 has quit [Quit: WeeChat 3.8]
20:31
hexdump0815 has joined #linux-amlogic
20:36
<
f_ >
What a funny mistake.
20:37
<
f_ >
writel(0x880019d, DMC_REFR_CTRL2);
20:37
<
f_ >
^ while using DDR0
20:37
<
f_ >
This is wrong. For DDR0 it should be:
20:37
<
f_ >
writel(0x880019d, DMC_REFR_CTRL1);
20:40
<
f_ >
Let's see if it works now.
20:45
<
f_ >
I guess that was it.
21:05
<
f_ >
Just need to reinstall postmarketOS to my SD card because..things became corrupt because I kept not cleanly shut it down :P
21:05
<
f_ >
it's fine. I don't care about the data on it.
21:06
<
f_ >
Still something weird happening on boot though, upon booting linux..output becomes distorted for a second.
21:24
<
f_ >
mmh..doesn't seem to be much of an issue
21:27
<
f_ >
I'll connect Wi-Fi and run stress-ng again
22:01
<
f_ >
I think I reacted too soon
22:02
<
f_ >
stress-ng makes the whole thing kernel panic
22:09
<
f_ >
So yeah memory corruption is still going..
22:26
<
f_ >
It's just less severe
22:26
<
f_ >
I'm still able to run neofetch