f11f12 has quit [Remote host closed the connection]
f11f12 has joined #linux-sunxi
random_yanek has joined #linux-sunxi
random_yanek has quit [Max SendQ exceeded]
afaerber has joined #linux-sunxi
fdcx has quit [Ping timeout: 252 seconds]
random_yanek has joined #linux-sunxi
imcsk8__ has quit [Read error: Connection reset by peer]
imcsk8_ has joined #linux-sunxi
fdcx has joined #linux-sunxi
TEKrantz has quit [Quit: First shalt thou take out the Holy Pin. Then, shalt thou count to three. No more. No less.]
<plaes>
ok, seems like I was able to write the 'system' partition
<plaes>
but how should I approach the loader1 and loader2 partitions?
<plaes>
and what's 'esp' for?
victhor has joined #linux-sunxi
<plaes>
sunxi-spl.bin goes to loader1?
<mripard>
yep
<plaes>
and loader2 is for?
<mripard>
and u-boot.img for loader2
<plaes>
and esp?
<mripard>
that's mostly for arm64
<plaes>
ah.. cool
<mripard>
and that's where the u-boot environment is supposed to be stored
<mripard>
so you can just flash an empty fat filesystem there if you want
<plaes>
esp == environment storage partition?
<ElBarto>
efi system partition
<plaes>
:)
<plaes>
whoa.. almost worked :)
jaganteki has quit [Quit: Page closed]
selfbg has quit [Remote host closed the connection]
tnovotny has joined #linux-sunxi
jaganteki has joined #linux-sunxi
reinforce1 has quit [Quit: Leaving.]
<plaes>
ok, need to figure out the uuid mismatches :S
<plaes>
debian initrd wants to load different root device
sunshavi has quit [Read error: Connection reset by peer]
sunshavi has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
koty0f has joined #linux-sunxi
enrico_ has quit [Ping timeout: 252 seconds]
foxx_ has quit [Ping timeout: 246 seconds]
lurchi__ has quit [Ping timeout: 268 seconds]
megi has quit [Quit: WeeChat 2.2]
lurchi__ has joined #linux-sunxi
koty0f has quit [Quit: Leaving]
koty0f has joined #linux-sunxi
<koty0f>
jerenej: thanks for response. I would like to connect my bridge to A64 HDMI peripheral. The bridge is Toshiba TC358870 HDMI->DSI bridge. tcon0 is used by second display directly connected to A64 DSI peripheral. Thats why I connected my bridge to hdmi_out
afaerber has quit [Quit: Leaving]
afaerber has joined #linux-sunxi
enrico__ has joined #linux-sunxi
kaspter1 has joined #linux-sunxi
kaspter has quit [Ping timeout: 252 seconds]
kaspter1 is now known as kaspter
megi has joined #linux-sunxi
<jernej>
ok, that changes things a bit
<anarsoul>
MoeIcenowy: thanks, I'll test it tonight
<jernej>
wait, why don't you use native DSI? It's true that driver is in the works, but it would be easier nevertheless
tllim has joined #linux-sunxi
hipboi_ has joined #linux-sunxi
hipboi has quit [Ping timeout: 252 seconds]
netlynx has joined #linux-sunxi
netlynx has joined #linux-sunxi
netlynx has quit [Changing host]
<koty0f>
I need two displays attached. One via native DSI (it is working OK) and the second connected via HDMI->TC358870->panel
<jaganteki>
the only change b/w us is panel, yours in burst and I'm using video stream
<jaganteki>
and panel clock
jbrown has quit [Ping timeout: 252 seconds]
<anarsoul>
jaganteki: did you add burst support to dsi driver?
koty0f has quit [Ping timeout: 260 seconds]
<jaganteki>
no, since the panel I have used didn't use it
tnovotny has quit [Quit: Leaving]
<anarsoul>
jaganteki: that's another major difference
jbrown has joined #linux-sunxi
<jaganteki>
don't know if it works, how about checking your panel to use 30 clock?
curlybracket has joined #linux-sunxi
<anarsoul>
jaganteki: I don't have enough spare time to check it
<curlybracket>
this series got us working DSI in video mode: https://gist.github.com/zavorka/8c8ce200fdbb2e1783e105eecaa01d07 ; I didn't track if each and every of my changes to the sun4i-drm or clk-sunxi-ng was essential unfortunately, there's only a few of them though
<vagrantc>
so, very excited to see u-boot getting upstreamed for pinebook!
florianH has quit [Ping timeout: 264 seconds]
florianH has joined #linux-sunxi
<vagrantc>
still seem to have issues with the clock jumping far into the future occasionally (and maybe sometimes into the distant past?)
<vagrantc>
i seem to recall some patches posted about that, but either they were ineffective or didn't make it into linux 4.19
<anarsoul|2>
vagrantc: I think the patch for workaround a64 timer erratum hasn't been upstreamed yet
<anarsoul|2>
s/for/to
<vagrantc>
yeah, that was my fear
<vagrantc>
although the bigger fear is that the patches don't work :)
<anarsoul|2>
I've never experienced it myself on my pinebook
<anarsoul|2>
but I added the patch to my 4.18 tree
<vagrantc>
i've seen it both on pine64+ and pinebook
<anarsoul|2>
MoeIcenowy: btw, you may want to disable glamor for your AOSC build if you haven't done it yet. On archlinux it uses llvmpipe and it makes X very slow
clemens3_ has quit [Ping timeout: 244 seconds]
<vagrantc>
last patch i have was from samuel holland in mid-may
lurchi__ has quit [Read error: Connection reset by peer]