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 - Publicly Logged on https://irclog.whitequark.org/linux-amlogic
sputnik_ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 250 seconds]
warpme_ has quit [Quit: Connection closed for inactivity]
sputnik_ has joined #linux-amlogic
niceplaces has quit [Read error: Connection reset by peer]
niceplace has joined #linux-amlogic
Elpaulo has quit [Read error: Connection reset by peer]
Elpaulo has joined #linux-amlogic
TheAssassin has quit [Ping timeout: 272 seconds]
TheAssassin has joined #linux-amlogic
random_yanek has joined #linux-amlogic
TheAssassin has quit [Ping timeout: 272 seconds]
TheAssassin has joined #linux-amlogic
_whitelogger has joined #linux-amlogic
warpme_ has joined #linux-amlogic
buzzmarshall has quit [Remote host closed the connection]
Elpaulo has quit [Read error: Connection reset by peer]
Elpaulo has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
<narmstrong> xdarklight: I think it's a alpha issue
<narmstrong> xdarklight: OSD_COLOR_MATRIX_32_RGBA causes the blue tint, but you must badly configure alpha, the framebuffer must have all alpha bits set, and kmscube buffer not
sputnik_ has quit [Read error: Connection reset by peer]
sputnik_ has joined #linux-amlogic
random_yanek has quit [Ping timeout: 256 seconds]
random_yanek has joined #linux-amlogic
sputnik_ has quit [Read error: Connection reset by peer]
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Read error: Connection reset by peer]
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 256 seconds]
buzzmarshall has joined #linux-amlogic
armoon has joined #linux-amlogic
armoon has quit [Remote host closed the connection]
<xdarklight> narmstrong: I think you are right with this
<xdarklight> narmstrong: looking at the ALPHA value in VIU_OSD1_TEST_RDDATA[7:0] (and OSD2): 3.10 kernel: 0x1a2c=0x2d85757f, 0x1a4c=0x10808000 - mainline: 0x1a2c=0x10808000, 0x1a4c=0x00000000
<xdarklight> narmstrong: OSD1 is interesting, because alpha is 0x7f on 3.10 but 0x0 on mainline
vagrantc has joined #linux-amlogic
<xdarklight> narmstrong: you're 100% right. if I do this https://pastebin.com/LHxTa9rb and then try the result on my Le Potato board then I end up in the same situation as on Meson8b: no framebuffer output but kmscube looks fine!
vagrantc has quit [Quit: leaving]
Linnaea has quit [Read error: Connection reset by peer]
Linnaea has joined #linux-amlogic
sputnik_ has joined #linux-amlogic
sputnik__ has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 260 seconds]
Elpaulo has quit [Quit: Elpaulo]
repk has quit [Ping timeout: 272 seconds]
repk has joined #linux-amlogic
sputnik__ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
Darkmatter66_ has joined #linux-amlogic
Darkmatter66 has quit [Ping timeout: 256 seconds]
Xogium has quit [Read error: Connection reset by peer]
Xogium has joined #linux-amlogic
niceplaces has joined #linux-amlogic
niceplace has quit [Ping timeout: 256 seconds]
vagrantc has joined #linux-amlogic
ldevulder has joined #linux-amlogic
ldevulder_ has quit [Ping timeout: 256 seconds]
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 265 seconds]
sputnik_ has joined #linux-amlogic