#
282199 |
|
28-Apr-2015 |
dumbbell |
drm: Update the device-independent code to match Linux 3.8.13
This update brings few features: o Support for the setmaster/dropmaster ioctls. For instance, they are used to run multiple X servers simultaneously. o Support for minor devices. The only user-visible change is a new entry in /dev/dri but it is useless at the moment. This is a first step to support render nodes [1].
The main benefit is to greatly reduce the diff with Linux (at the expense of an unreadable commit diff). Hopefully, next upgrades will be easier.
No updates were made to the drivers, beside adapting them to API changes.
[1] https://en.wikipedia.org/wiki/Direct_Rendering_Manager#Render_nodes
r280814 is merged at the same time to avoid a short window where RANDR might be broken:
drm: Import Linux commit 9bc3cd5673d84d29272fa7181a4dfca83cbb48c1
Author: Ville Syrjälä <ville.syrjala@linux.intel.com> Date: Fri May 31 12:17:08 2013 +0000
drm: Sort connector modes based on vrefresh
Keeping the modes sorted by vrefresh before the pixel clock makes the mode list somehow more pleasing to the eye.
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Reviewed-by: Alex Deucher <alexander.deucher@amd.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
PR: 198936 (r280814) Tested by: Many people MFC of: r280183, r280187 (original commit by glebius), r280814 Relnotes: yes
|
#
274865 |
|
22-Nov-2014 |
dumbbell |
drm: Take vt(4) default mode from loader tunables
By default, vt(4) gets the "preferred mode" from DRM, when using a DRM video driver as its backend. The preferred mode is usually the native screen resolution.
Now, if this mode isn't appropriate, a user can use loader tunables to select a mode. The tunables are read in the following order: 1. kern.vt.fb.modes.$connector_name 2. kern.vt.fb.default_mode
For example, to set a 1024x768 mode, no matter the connector: kern.vt.fb.default_mode="1024x768"
To set a 800x600 mode only on the laptop builtin screen: kern.vt.fb.modes.LVDS-1="800x600"
Beside r274031, this MFC includes:
r274049: drm: When reading connector mode tunables, list connectors
... and their associated tunables. This gives a way to know the list of available connectors, no matter the driver.
The problem is that xrandr(1) can list connectors but it uses a different naming.
r274050: vt(4): Document kern.vt.fb.default_mode and kern.vt.fb.modes.*
Those tunables are used to set a specific mode in vt(4) instead of using the default mode.
Differential Revision: https://reviews.freebsd.org/D1098 Reviewed by: ak@, emaste@, kwm@
r274051: vt(4): Improve the description of kern.vt.fb.modes.$connector
Differential Revision: https://reviews.freebsd.org/D1098 Submitted by: emaste@
r274053: vt(4): Start new sentences on their own lines
Submitted by: brueffer@
MFC of: r274031, r274049, r274050, r274051, r274053
|
#
282199 |
|
28-Apr-2015 |
dumbbell |
drm: Update the device-independent code to match Linux 3.8.13
This update brings few features: o Support for the setmaster/dropmaster ioctls. For instance, they are used to run multiple X servers simultaneously. o Support for minor devices. The only user-visible change is a new entry in /dev/dri but it is useless at the moment. This is a first step to support render nodes [1].
The main benefit is to greatly reduce the diff with Linux (at the expense of an unreadable commit diff). Hopefully, next upgrades will be easier.
No updates were made to the drivers, beside adapting them to API changes.
[1] https://en.wikipedia.org/wiki/Direct_Rendering_Manager#Render_nodes
r280814 is merged at the same time to avoid a short window where RANDR might be broken:
drm: Import Linux commit 9bc3cd5673d84d29272fa7181a4dfca83cbb48c1
Author: Ville Syrjälä <ville.syrjala@linux.intel.com> Date: Fri May 31 12:17:08 2013 +0000
drm: Sort connector modes based on vrefresh
Keeping the modes sorted by vrefresh before the pixel clock makes the mode list somehow more pleasing to the eye.
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Reviewed-by: Alex Deucher <alexander.deucher@amd.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
PR: 198936 (r280814) Tested by: Many people MFC of: r280183, r280187 (original commit by glebius), r280814 Relnotes: yes
|
#
274865 |
|
22-Nov-2014 |
dumbbell |
drm: Take vt(4) default mode from loader tunables
By default, vt(4) gets the "preferred mode" from DRM, when using a DRM video driver as its backend. The preferred mode is usually the native screen resolution.
Now, if this mode isn't appropriate, a user can use loader tunables to select a mode. The tunables are read in the following order: 1. kern.vt.fb.modes.$connector_name 2. kern.vt.fb.default_mode
For example, to set a 1024x768 mode, no matter the connector: kern.vt.fb.default_mode="1024x768"
To set a 800x600 mode only on the laptop builtin screen: kern.vt.fb.modes.LVDS-1="800x600"
Beside r274031, this MFC includes:
r274049: drm: When reading connector mode tunables, list connectors
... and their associated tunables. This gives a way to know the list of available connectors, no matter the driver.
The problem is that xrandr(1) can list connectors but it uses a different naming.
r274050: vt(4): Document kern.vt.fb.default_mode and kern.vt.fb.modes.*
Those tunables are used to set a specific mode in vt(4) instead of using the default mode.
Differential Revision: https://reviews.freebsd.org/D1098 Reviewed by: ak@, emaste@, kwm@
r274051: vt(4): Improve the description of kern.vt.fb.modes.$connector
Differential Revision: https://reviews.freebsd.org/D1098 Submitted by: emaste@
r274053: vt(4): Start new sentences on their own lines
Submitted by: brueffer@
MFC of: r274031, r274049, r274050, r274051, r274053
|