Re: bochs_hw_init fails to request framebuffer on EFI boot with plymouth visible

2020-01-12 Thread Gerd Hoffmann
On Fri, Jan 10, 2020 at 05:32:11PM +0100, Marek Marczykowski-Górecki wrote: > Hi, > > This is the context of "bochs_drm: failed bochs_hw_init() results in > panic". When I boot the system, if plymouth is visible, it crashes. But > if I press ESC to hide it, it boots fine. bochs_drm is build as

Re: bochs_drm: failed bochs_hw_init() results in panic

2020-01-12 Thread Gerd Hoffmann
> Now the messages looks like this: > > [ 29.800835] bochs-drm :00:02.0: remove_conflicting_pci_framebuffers: > bar 0: 0xc000 -> 0xc0ff > [ 29.800840] bochs-drm :00:02.0: remove_conflicting_pci_framebuffers: > bar 2: 0xc1087000 -> 0xc1087fff > [ 29.800842] checking generic

Re: [PATCH] drm/cirrus: Let DRM core send VBLANK events

2020-01-12 Thread Daniel Vetter
On Fri, Jan 10, 2020 at 12:57:07PM +0100, Thomas Zimmermann wrote: > In drm_atomic_helper_fake_vblank() the DRM core sends out VBLANK > events if struct drm_crtc_state.no_vblank is enabled. Replace cirrus' > VBLANK events with the DRM core's functionality. > > Signed-off-by: Thomas Zimmermann >

CISTI'2020 - Doctoral Symposium | Seville, Spain; Deadline: February 14

2020-01-12 Thread Maria Lemos
* Published in IEEE Xplore and indexed by ISI, Scopus, EI-Compendex, Google Scholar, etc. ** Conference with H5-Index = 16 (Google Scholar Ranking) --- Doctoral Symposium of