Re: Regression in ARM CLCD Fb
On Sat, Oct 15, 2016 at 6:44 PM, Amit Pundirwrote: > Commit 25348160e9a4 ("video: ARM CLCD: add special panel hook for > Versatiles") broke CLCD framebuffer on my qemu-system-arm + > vexpress-v2p-ca9.dtb + Android test setup. Sent a patch tested on QEMU, check if it solves your problem! Yours, Linus Walleij > > Android boot failed with: > > E/SurfaceFlinger( 1003): ERROR: failed to open framebuffer (No such > file or directory), aborting > > It means Android didn't find /dev/fb* or equivalent /dev/graphics/fb*. > > Any thoughts on what might be going wrong here? Or am I missing > anything obvious in my Qemu setup, though it was working fine so far. > I'd be happy to help debug things. > > Regards, > Amit Pundir
Re: Regression in ARM CLCD Fb
On Sat, Oct 15, 2016 at 6:44 PM, Amit Pundir wrote: > Commit 25348160e9a4 ("video: ARM CLCD: add special panel hook for > Versatiles") broke CLCD framebuffer on my qemu-system-arm + > vexpress-v2p-ca9.dtb + Android test setup. Sent a patch tested on QEMU, check if it solves your problem! Yours, Linus Walleij > > Android boot failed with: > > E/SurfaceFlinger( 1003): ERROR: failed to open framebuffer (No such > file or directory), aborting > > It means Android didn't find /dev/fb* or equivalent /dev/graphics/fb*. > > Any thoughts on what might be going wrong here? Or am I missing > anything obvious in my Qemu setup, though it was working fine so far. > I'd be happy to help debug things. > > Regards, > Amit Pundir
Re: Regression in ARM CLCD Fb
On Sat, Oct 15, 2016 at 6:44 PM, Amit Pundirwrote: > Commit 25348160e9a4 ("video: ARM CLCD: add special panel hook for > Versatiles") broke CLCD framebuffer on my qemu-system-arm + > vexpress-v2p-ca9.dtb + Android test setup. OMG I have to fix that, sorry. Can you tell me how you invoke qemu? > Android boot failed with: > > E/SurfaceFlinger( 1003): ERROR: failed to open framebuffer (No such > file or directory), aborting > > It means Android didn't find /dev/fb* or equivalent /dev/graphics/fb*. > > Any thoughts on what might be going wrong here? Or am I missing > anything obvious in my Qemu setup, though it was working fine so far. > I'd be happy to help debug things. Probably not, I guess it's my screwup and relates to machines without the special CLCD control registers. I just need to reproduce it and I will fix. Yours, Linus Walleij
Re: Regression in ARM CLCD Fb
On Sat, Oct 15, 2016 at 6:44 PM, Amit Pundir wrote: > Commit 25348160e9a4 ("video: ARM CLCD: add special panel hook for > Versatiles") broke CLCD framebuffer on my qemu-system-arm + > vexpress-v2p-ca9.dtb + Android test setup. OMG I have to fix that, sorry. Can you tell me how you invoke qemu? > Android boot failed with: > > E/SurfaceFlinger( 1003): ERROR: failed to open framebuffer (No such > file or directory), aborting > > It means Android didn't find /dev/fb* or equivalent /dev/graphics/fb*. > > Any thoughts on what might be going wrong here? Or am I missing > anything obvious in my Qemu setup, though it was working fine so far. > I'd be happy to help debug things. Probably not, I guess it's my screwup and relates to machines without the special CLCD control registers. I just need to reproduce it and I will fix. Yours, Linus Walleij
Regression in ARM CLCD Fb
Hi, Commit 25348160e9a4 ("video: ARM CLCD: add special panel hook for Versatiles") broke CLCD framebuffer on my qemu-system-arm + vexpress-v2p-ca9.dtb + Android test setup. Android boot failed with: E/SurfaceFlinger( 1003): ERROR: failed to open framebuffer (No such file or directory), aborting It means Android didn't find /dev/fb* or equivalent /dev/graphics/fb*. Any thoughts on what might be going wrong here? Or am I missing anything obvious in my Qemu setup, though it was working fine so far. I'd be happy to help debug things. Regards, Amit Pundir
Regression in ARM CLCD Fb
Hi, Commit 25348160e9a4 ("video: ARM CLCD: add special panel hook for Versatiles") broke CLCD framebuffer on my qemu-system-arm + vexpress-v2p-ca9.dtb + Android test setup. Android boot failed with: E/SurfaceFlinger( 1003): ERROR: failed to open framebuffer (No such file or directory), aborting It means Android didn't find /dev/fb* or equivalent /dev/graphics/fb*. Any thoughts on what might be going wrong here? Or am I missing anything obvious in my Qemu setup, though it was working fine so far. I'd be happy to help debug things. Regards, Amit Pundir