<div dir="ltr"><div dir="ltr"><div dir="ltr">On Mon, 17 Feb 2020 at 09:22, Alexander Kanavin <<a href="mailto:alex.kanavin@gmail.com">alex.kanavin@gmail.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">\perhaps then make this chage such thst it only affects the<br>
architecture you have tested.</blockquote><div dir="auto"><br></div><div dir="auto">Fbdev backend is not documented, and there is no guarantee by upstream that it will work. You wouldn’t want to use it on actual targets either as it has no hw acceleration support. I think the change should apply to all, we should test standard drm/kms code paths everywhere and fix/report issues as needed.</div></div></div></blockquote><div><br></div><div>The issue with qemumips in particular is that it is still using cirrus for the graphics card, which has been superseded by '-vga std' for a long time:</div><div><a href="https://www.kraxel.org/blog/2014/10/qemu-using-cirrus-considered-harmful/">https://www.kraxel.org/blog/2014/10/qemu-using-cirrus-considered-harmful/</a><br></div><div><br></div><div>If that is switched, then fbdev backend should be no longer necessary just like in qemux86_64.</div><div><br></div><div>Alex</div></div></div></div>