ChanServ changed the topic of #armlinux to: ARM kernel talk [Upstream kernel, find your vendor forums for questions about their kernels] | https://libera.irclog.whitequark.org/armlinux
rvalue has quit [Ping timeout: 245 seconds]
mraynal has quit [Remote host closed the connection]
matthias_bgg has quit [Read error: Connection reset by peer]
amitk has quit [Ping timeout: 246 seconds]
amitk has joined #armlinux
matthias_bgg has joined #armlinux
jpanisbl has joined #armlinux
amitk has quit [Ping timeout: 245 seconds]
dliviu has quit [Quit: Going away]
dliviu has joined #armlinux
headless has quit [Quit: Konversation terminated!]
amitk has joined #armlinux
adelaunay has joined #armlinux
alpernebbi has quit [Read error: Connection reset by peer]
alpernebbi has joined #armlinux
alpernebbi has quit [Client Quit]
<geertu>
ukleinek: You do like large patch series? ;-)
* geertu
tries to climb out of the drm rabbit hole, too
<javierm>
geertu: I see that you are having fun with workqueues :)
<geertu>
javierm: Oh, that?
<geertu>
That's a minor issue.
<javierm>
geertu: ah, Ok. Thought you were referring to that
<geertu>
javierm: I have added R1 (initially fake C1) support to ssd130xdrm.
<geertu>
Now the hard part is to make the fbdev emulation fall back to R1 if C1 is not available.
<javierm>
geertu: nice! I had in my TODO but never found the time
<javierm>
geertu: I did use DRM_FORMAT_C1 in commit e254b584dbc0 ("drm/ssd130x: Remove hardcoded bits-per-pixel in ssd130x_buf_alloc()") as a preparation but wanted to wire to ssd130x_formats
<javierm>
I guess the only thing that has to be done is skipping the xrgb8888 -> mono convesion if that format is chosen?
<geertu>
javierm: Yep. And that's working fine.
<javierm>
geertu: awesome
<geertu>
javierm: Oops, should have reviewed that patch (it's still marked for review). Should be R1 iso C1. Review sent.
amitk has quit [Read error: Connection reset by peer]
amitk has joined #armlinux
<ukleinek>
geertu: yeah, now that people poach in my patch area[1], I have to look for alternatives :-)
rgallaispou has quit [Remote host closed the connection]
rgallaispou has joined #armlinux
<arnd>
javierm, ardb: I'm still looking at the screen_info stuff to resend my series for cleaning that up. I was trying to add a patch to remove references to the global screen_info from efifb, but that clashes with the code from commit dcf8f5ce31656 ("drivers/fbdev/efifb: Allow BAR to be moved instead of claiming it")
<ardb>
i think the logic in that patch applies to other 'dumb' framebuffers that happen to be backed by a live BAR
<arnd>
would it make sense to move that entire PCI fixup and efifb_fix.smem_start relocation logic to drivers/pci/vgaarb.c instead? It looks to me like that would also allow adding the same feature to simpledrm/simplefb, which are missing it today
<arnd>
if both simpledrm and efifb are built into the kernel, the sysfb code tries to use simpledrm instead of efifb, so it would get back the bug that you fixed
<ardb>
so we don't need both in any case then, right?
<arnd>
ardb: I think sysfb keeps the fallback to efifb for the case in which sysfb_parse_mode() fails to find the right settings for simpledrm
monstr has quit [Remote host closed the connection]
rgallaispou has left #armlinux [#armlinux]
alpernebbi has quit [Ping timeout: 240 seconds]
amitk has joined #armlinux
adelaunay has quit [Quit: Client closed]
headless has joined #armlinux
jpanisbl has quit [Quit: Konversation terminated!]
torez has quit [Quit: torez]
frieder has quit [Remote host closed the connection]
<javierm>
arnd: that's correct yes, although many distros just disable the fbdev driver nowadays (at least Fedora and OpenSUSE, probably others)