On Tue, 13 Oct 2020, Byron Stanoszek wrote:
I'm having a problem with both the 5.8 and 5.9 kernels using the nouveau DRM
driver. I have a laptop with a VGA card (specs below) connected to a
5120x1440 screen. At boot time, the card correctly detects the screen, tries
to allocate fbdev fb0
I'm having a problem with both the 5.8 and 5.9 kernels using the nouveau DRM
driver. I have a laptop with a VGA card (specs below) connected to a 5120x1440
screen. At boot time, the card correctly detects the screen, tries to allocate
fbdev fb0, then the video hangs completely for 15-30 seconds
On Thu, 18 Apr 2013, David Herrmann wrote:
> You can acquire/drop DRM-Master via drmSetMaster/drmDropMaster.
>
> If your DRM card is a PCI device, you can use the sysfs "boot_vga"
> attribute of the parent PCI device.
> (/sys/class/drm/card0/device/boot_vga)
David,
Thanks! That was exactly what
On Thu, 18 Apr 2013, David Herrmann wrote:
You can acquire/drop DRM-Master via drmSetMaster/drmDropMaster.
If your DRM card is a PCI device, you can use the sysfs boot_vga
attribute of the parent PCI device.
(/sys/class/drm/card0/device/boot_vga)
David,
Thanks! That was exactly what I was
David,
I'm developing a small application that uses libdrm (DRM ioctls) to change the
resolution of a single graphics display and show a framebuffer. I've run into
two problems with this implementation that I'm hoping you can address.
1. Each application is its own process, which is designed
David,
I'm developing a small application that uses libdrm (DRM ioctls) to change the
resolution of a single graphics display and show a framebuffer. I've run into
two problems with this implementation that I'm hoping you can address.
1. Each application is its own process, which is designed to
