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
buzzmarshall has quit [Quit: Konversation terminated!]
vagrantc has quit [Quit: leaving]
tdebrouw has joined #linux-amlogic
tdebrouw has quit [Client Quit]
jelly has quit [Read error: Connection reset by peer]
jelly has joined #linux-amlogic
buzzmarshall has joined #linux-amlogic
vagrantc has joined #linux-amlogic
vagrantc has quit [Remote host closed the connection]
tdebrouw has joined #linux-amlogic
vagrantc has joined #linux-amlogic
GNUtoo has quit [Ping timeout: 276 seconds]
GNUtoo has joined #linux-amlogic
tdebrouw has quit [Quit: Leaving.]
<xdarklight> gbisson: RE the UART problem you mentioned some time ago - you may want to try https://patchwork.kernel.org/project/linux-amlogic/cover/20211229135350.9659-1-yu.tu@amlogic.com/ (I didn't get the chance to review it yet - not feeling well today, but it should improve the precision of the UART clock / reduce jitter)
<gbisson> xdarklight: ok thanks! I'll give it a shot and let you know
vagrantc has quit [Ping timeout: 240 seconds]