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
vagrantc has quit [Quit: leaving]
luka177 has quit [Ping timeout: 246 seconds]
jacobk has quit [Ping timeout: 245 seconds]
luka177 has joined #linux-amlogic
luka177 has quit [Ping timeout: 252 seconds]
luka177 has joined #linux-amlogic
jacobk has joined #linux-amlogic
Daanct12 has joined #linux-amlogic
vagrantc has joined #linux-amlogic
vagrantc has quit [Quit: leaving]
hexdump0815 has quit [Ping timeout: 264 seconds]
hexdump0815 has joined #linux-amlogic
jacobk has quit [Ping timeout: 260 seconds]
<lvrp16> running desktop seems to run into the pll issue a lot. still haven't figured out a way to consistently make it happen. https://www.irccloud.com/pastebin/oUWAa1j3/
<lvrp16> I found a consistent trigger :D ssh to a server, open byobu, and open a large file in vim, and push the down arrow, can cause the SYS_PLL issue every 10 seconds or so :D
<lvrp16> now I can throw this over a wall and hope for the best
jacobk has joined #linux-amlogic
<f_> lvrp16: Vim :D
<lvrp16> I've been using A311D as the DD for the last week or so
<lvrp16> ran into repeated screen freezes on the board I'm using, doesn't happen on my s905d3 sample. I won't be able to mass replicate until next week.
<f_> screen freezes usually only happen to me when I enable the npu
<lvrp16> I'm wondering if it's an undercurrent thing
<lvrp16> hardware is such a PITA
<lvrp16> *shakes fist at physics*
<f_> no idea, but it could be because of..me usually using a microusb->usb-c dongle XD
<f_> (makes testing easier as I wouldn't have to use another cable..)
<lvrp16> A311D can use up 2A so it's easily conceivable that the issues might be related to voltage rails and vdroop
<f_> After upgrading u-boot I didn't notice much issues..in fact, I was pleased and impressed at how smooth gnome ran
<f_> I usually don't use desktop environments (I use standalone WMs), but it's nice to see it running this smooth!
<lvrp16> I just updated the spiflash file to 2024.01 a few moments ago
<lvrp16> I still have to figure out the CVBS detect situation
<f_> At some point I'll probably build u-boot myself :P
<narmstrong> lvrp16: it should be quite easy with a custom connector bridge doing the detect via saradc, I re-architectured the thing so it can be easy to add an intermediate bridge for the jack CVBS detect
djrscally has joined #linux-amlogic
<f_> aand I should rebase my tree!
<f_> (and hope nothing breaks)
<lvrp16> narmstrong: cool, btw, do you know a way to calculate or limit the framerate in u-boot? any display with refresh rates over 60 seems to bork.
<f_> lvrp16: I could try to reproduce if you wish.
<lvrp16> do I just do the reverse calculation from clock frequency divided by the h/v porch and res to figure the refresh rate out?
<f_> I have such display.
<lvrp16> f_: I have 75Hz displays and 144Hz displays, it seems anything over 60, I get nothing on u-boot
<f_> I think the monitor I usually use does do 75Hz and u-boot doesn't seem to b0rk
<lvrp16> i've already restricted resolutions > 1920
<f_> but it might be running in 60Hz..
<f_> Not sure how to check though.
<f_> hmm works fine
<f_> But for some reason resolution in linux is limited to 1080p 60Hz...
<f_> lvrp16: Unless you limited it yourself?
<lvrp16> it might be the preferred mode in edid
<f_> Highly doubt.
<lvrp16> i have a monitor with 4k 144hz monitor and it just displays nothing.
<f_> Monitor is 1440p 165Hz ultrawide.
<narmstrong> lvrp16: yep, divide the clock by all the timings added and you'll get the framerate
<narmstrong> pretty sure some helpers exists
<narmstrong> there's some in drm for sure
<f_> I still remember needing hacks to display in 3440x1440, on my laptop..
<lvrp16> cool I'll try to grep
<lvrp16> f_: did you get that to work? it's on my todo list
<f_> I was able to get 3440x1440 on my laptop with those hacks, but it ain't pretty.
<f_> In the meantime the issue I was experiencing got fixed in upstream nouveau and I could output 3440x1440 without issues.
<f_> Still limited to 60 Hz, but it might be a limitation of my nVidia gpu.
<f_> Anyway nothing to do with Amlogic :)
neoninteger has quit [Remote host closed the connection]
neoninteger has joined #linux-amlogic
jacobk has quit [Ping timeout: 245 seconds]
jacobk has joined #linux-amlogic
ldevulder has joined #linux-amlogic
zsoltiv__ has quit [Ping timeout: 256 seconds]
luka177 has quit [Ping timeout: 260 seconds]
luka177 has joined #linux-amlogic
zsoltiv_ has joined #linux-amlogic
Daanct12 has quit [Quit: WeeChat 4.1.2]
JohnnyonFlame has quit [Read error: Connection reset by peer]
mripard has quit [Quit: mripard]
mripard has joined #linux-amlogic
mripard has quit [Quit: mripard]
mripard has joined #linux-amlogic
ldevulder has quit [Quit: Leaving]
psydroid has joined #linux-amlogic
<f_> Alright S905 DRAM actually seems to become unreliable thus linux panics and if you're unlucky, congrats! you're running undefined code :P
<f_> At least that's what it seems to be happening.
<f_> If you're lucky it kernel panics.
<f_> (requiring a reset)
<f_> Doesn't sound good, does it?
jacobk has quit [Ping timeout: 245 seconds]
buzzmarshall has joined #linux-amlogic
luka177 has quit [Ping timeout: 264 seconds]
luka177 has joined #linux-amlogic
vagrantc has joined #linux-amlogic
jacobk has joined #linux-amlogic
JohnnyonFlame has joined #linux-amlogic
jacobk has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
GNUtoo has quit [Ping timeout: 240 seconds]
GNUtoo has joined #linux-amlogic
jacobk has joined #linux-amlogic
JohnnyonFlame has quit [Ping timeout: 260 seconds]
psydroid has quit [Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/]
vagrantc has quit [Quit: leaving]
naoki has joined #linux-amlogic
naoki has quit [Quit: naoki]
naoki has joined #linux-amlogic
JohnnyonFlame has joined #linux-amlogic
jacobk has quit [Ping timeout: 245 seconds]