Op 07-07-15 om 11:18 schreef Daniel Vetter: > On Tue, Jul 07, 2015 at 09:08:13AM +0200, Maarten Lankhorst wrote: >> This allows the first atomic call during hw init to be a real modeset, >> which is useful for forcing a recalculation. > fbcon is optional, you can't rely on anything being done in any specific > way. What exactly do you need this for, what's the implications? In the hw readout I noticed some warnings when I wasn't setting any mode property in the readout. I want the first function to be the modeset, so we have a sane base to commit changes on. Ideally this whole function would have a atomic counterpart which does it in one go. :)
- [PATCH v2 02/20] drm: Don't update plane properties for ... Maarten Lankhorst
- [Intel-gfx] [PATCH v2 02/20] drm: Don't update plan... Daniel Vetter
- [Intel-gfx] [PATCH v2 02/20] drm: Don't update ... Maarten Lankhorst
- [Intel-gfx] [PATCH v2 02/20] drm: Don't upd... Daniel Vetter
- [Intel-gfx] [PATCH v2 02/20] drm: Don't... Maarten Lankhorst
- [Intel-gfx] [PATCH v2 02/20] drm: ... Daniel Vetter
- [Intel-gfx] [PATCH v2 02/20] drm: Don't... Maarten Lankhorst
- [Intel-gfx] [PATCH v2 02/20] drm: ... Daniel Vetter
- [Intel-gfx] [PATCH v2 02/20] d... Maarten Lankhorst
- [Intel-gfx] [PATCH v2 02/2... Daniel Vetter
- [Intel-gfx] [PATCH v2 02/2... Maarten Lankhorst
- [Intel-gfx] [PATCH v2 02/2... Daniel Vetter
- [Intel-gfx] [PATCH v2 02/2... Maarten Lankhorst