search for: fbdev

.../usr/lib/xorg/modules/extensions/libglx.so [ 2665.855] (II) Module glx: vendor="X.Org Foundation" [ 2665.855] compiled for 1.17.2, module version = 1.0.0 [ 2665.855] ABI class: X.Org Server Extension, version 9.0 [ 2665.855] (==) AIGLX enabled [ 2665.855] (II) LoadModule: "fbdev" [ 2665.856] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so [ 2665.857] (II) Module fbdev: vendor="X.Org Foundation" [ 2665.857] compiled for 1.17.2, module version = 0.4.3 [ 2665.857] Module class: X.Org Video Driver [ 2665.857] ABI class: X.Org Video Driver,...

...ensions/libglx.so > [ 2665.855] (II) Module glx: vendor="X.Org Foundation" > [ 2665.855] compiled for 1.17.2, module version = 1.0.0 > [ 2665.855] ABI class: X.Org Server Extension, version 9.0 > [ 2665.855] (==) AIGLX enabled > [ 2665.855] (II) LoadModule: "fbdev" > [ 2665.856] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so > [ 2665.857] (II) Module fbdev: vendor="X.Org Foundation" > [ 2665.857] compiled for 1.17.2, module version = 0.4.3 > [ 2665.857] Module class: X.Org Video Driver > [ 2665.857] ABI cl...

Compatibility updates for xserver 1.20. Adam Jackson (8): Default to 32bpp if the console is 8bpp (and we weren't told otherwise) Use own thunk functions instead of fbdevHW*Weak Pass the pci device (if any) through to fbdevhw in probe and preinit Fix shadow fb allocation size (v2) Remove dead pix24bpp variable Use shadowUpdate32to24 at 24bpp Update for 1.20 ABI fbdev 0.5.0 Alan Coopersmith (3): configure: Drop AM_MAINTAINER...

Adam Jackson (1): fbdev 0.4.0 Brice Goglin (1): Replace a non-ascii char with the corresponding groff escape in fbdev.man Ian Romanick (1): Add conditional support for pci-rework branch. Matthias Hopf (1): Fixed leftover PCIACCESS -> XSERVER_LIBPCIACCESS. Michel D?nzer (1): Only determine pi...

...> > > This is a sligtly updated version of a series sent on 24 Nov 2017. > > > > --- > > v2: > > - rebased on current drm-next > > - dropped staging/sm750fb changes > > - added kernel docs for DRM helpers > > v3: > > - move kerneldoc to fbdev, where functions are implemented > > - split kerneldoc for remove_conflicting_framebuffers() > > Ah, that's not quite what I had in mind. I think having the docs (also) in > the drm helpers would be good, since that's where drm people will look, > and that's the func...

This was only added for the drm's fbdev emulation support, so that it would try harder to show the Oops. Unfortunately this never really worked reliably, and in practice ended up pushing the real Oops off the screen due to plentyfull locking, sleep-while-atomic and other issues. So we removed all that support from the fbdev emulation a...

...replacing firmware FB driver with proper DRI driver and adds handover support to Tegra driver. This is a sligtly updated version of a series sent on 24 Nov 2017. --- v2: - rebased on current drm-next - dropped staging/sm750fb changes - added kernel docs for DRM helpers v3: - move kerneldoc to fbdev, where functions are implemented - split kerneldoc for remove_conflicting_framebuffers() - propagate return value in remove_conflicting_pci_framebuffers() --- Micha? Miros?aw (13): fbdev: show fbdev number for debugging fbdev: allow apertures == NULL in remove_conflicting_framebuffers() fb...

...replacing firmware FB driver with proper DRI driver and adds handover support to Tegra driver. This is a sligtly updated version of a series sent on 24 Nov 2017. --- v2: - rebased on current drm-next - dropped staging/sm750fb changes - added kernel docs for DRM helpers v3: - move kerneldoc to fbdev, where functions are implemented - split kerneldoc for remove_conflicting_framebuffers() - propagate return value in remove_conflicting_pci_framebuffers() --- Micha? Miros?aw (13): fbdev: show fbdev number for debugging fbdev: allow apertures == NULL in remove_conflicting_framebuffers() fb...

Calling directly into the fbdev stack only works when the fbdev layer is built into the kernel as well, or both are loadable modules: drivers/gpu/drm/nouveau/nouveau_drm.o: in function `nouveau_drm_probe': nouveau_drm.c:(.text+0x1f90): undefined reference to `remove_conflicting_pci_framebuffers' The change seems to have...

...t; This makes the redundant fb helpers .load_lut, .gamma_set and .gamma_get >> totally obsolete. >> >> I think the gamma_store can end up invalid on error. But the way I read >> it, that can happen in drm_mode_gamma_set_ioctl as well, so why should >> this pesky legacy fbdev stuff be any better? >> >> drm_fb_helper_save_lut_atomic justs saves the gamma lut for later. However, >> it saves it to the gamma_store which should already be up to date with what >> .gamma_get would return and is thus a nop. So, zap it. > > Removing drm_fb_helper_s...

...; remove_conflicting_pci_framebuffers(). > > Signed-off-by: Micha? Miros?aw <mirq-linux at rere.qmqm.pl> Since the only driver that seems to use this is the staging one, which imo is a DOA project, not sure it's worth to bother with this here. -Daniel > --- > drivers/video/fbdev/core/fbmem.c | 22 ++++++++++++++++++++++ > include/drm/drm_fb_helper.h | 12 ++++++++++++ > include/linux/fb.h | 2 ++ > 3 files changed, 36 insertions(+) > > diff --git a/drivers/video/fbdev/core/fbmem.c b/drivers/video/fbdev/core/fbmem.c > index 30a18d4c9de...

...; remove_conflicting_pci_framebuffers(). > > Signed-off-by: Micha? Miros?aw <mirq-linux at rere.qmqm.pl> Since the only driver that seems to use this is the staging one, which imo is a DOA project, not sure it's worth to bother with this here. -Daniel > --- > drivers/video/fbdev/core/fbmem.c | 22 ++++++++++++++++++++++ > include/drm/drm_fb_helper.h | 12 ++++++++++++ > include/linux/fb.h | 2 ++ > 3 files changed, 36 insertions(+) > > diff --git a/drivers/video/fbdev/core/fbmem.c b/drivers/video/fbdev/core/fbmem.c > index 30a18d4c9de...

Remove unnecessary dependencies in the include statements of the header file <linux/fb.h>. Several files throughout the kernel include the fbdev header, so reducing dependencies positively affects other subsystems as well. Also fix up nouveau and fbtft, which need backlight.h in some their source files. v2: * include backlight.h in fbtft (kernel test robot) Thomas Zimmermann (8): drm/nouveau: Include <linux/backlight.h> staging...

...also only associated with the intel_drmfb fbcon, controlled by >> i915.ko. In this situation, we already handle adjusting the backlight >> when the fbcon is blanked/unblanked and do not require backlight trying >> to do the same. >> >> Attempting to register with the fbdev as a client causes lockdep to warn >> about a dependency cycle: > > The fbdev notifier strikes again! > > Last time I looked into this I think the proper solution would be to split > the backlight part from the other fbdev notifier (which is used by fbcon > for reacting to f...

...duplicated code for replacing firmware FB driver with proper DRI driver and adds handover support to Tegra driver. The last patch is here because it uses new semantics of remove_conflicting_framebuffers() from this series. This can be considered independently, though. --- Micha? Miros?aw (13): fbdev: show fbdev number for debugging fbdev: add remove_conflicting_pci_framebuffers() drm/amdgpu: use simpler remove_conflicting_pci_framebuffers() drm/bochs: use simpler remove_conflicting_pci_framebuffers() drm/cirrus: use simpler remove_conflicting_pci_framebuffers() drm/mgag200: use simpl...

...duplicated code for replacing firmware FB driver with proper DRI driver and adds handover support to Tegra driver. The last patch is here because it uses new semantics of remove_conflicting_framebuffers() from this series. This can be considered independently, though. --- Micha? Miros?aw (13): fbdev: show fbdev number for debugging fbdev: add remove_conflicting_pci_framebuffers() drm/amdgpu: use simpler remove_conflicting_pci_framebuffers() drm/bochs: use simpler remove_conflicting_pci_framebuffers() drm/cirrus: use simpler remove_conflicting_pci_framebuffers() drm/mgag200: use simpl...

...d remove features, e.g. 50145474f6ef ("fbcon: remove soft scrollback code"). Now the problem is that most modern-ish drivers really only treat fbcon as an dumb kernel console until userspace takes over, and Oops printer for some emergencies. Looking at drm drivers and the basic vesa/efi fbdev drivers shows that only 3 drivers support any kind of acceleration: - nouveau, seems to be enabled by default - omapdrm, when a DMM remapper exists using remapper rewriting for y/xpanning - gma500, but that is getting deleted now for the GTT remapper trick, and the accelerated copyarea never s...

...oject, not sure it's worth to bother with this here. > > afaik, this device is used in production by few manufacturers and it is > usefull for them to have it in the tree and the only reason it is still > in staging is because Tomi announced he will not take any new drivers in > fbdev. And, so I have not taken the initiative to properly move it out > of staging. I think Bartlomiej will also not accept new drivers in fbdev. Imo, if no one cares about porting it to kms (which will give you an fbdev driver for free), then we should throw it out. At least I thought staging was o...

...oject, not sure it's worth to bother with this here. > > afaik, this device is used in production by few manufacturers and it is > usefull for them to have it in the tree and the only reason it is still > in staging is because Tomi announced he will not take any new drivers in > fbdev. And, so I have not taken the initiative to properly move it out > of staging. I think Bartlomiej will also not accept new drivers in fbdev. Imo, if no one cares about porting it to kms (which will give you an fbdev driver for free), then we should throw it out. At least I thought staging was o...

...h the intel_drmfb fbcon, controlled by > >> i915.ko. In this situation, we already handle adjusting the backlight > >> when the fbcon is blanked/unblanked and do not require backlight trying > >> to do the same. > >> > >> Attempting to register with the fbdev as a client causes lockdep to warn > >> about a dependency cycle: > > > > The fbdev notifier strikes again! > > > > Last time I looked into this I think the proper solution would be to split > > the backlight part from the other fbdev notifier (which is used b...