@@ -37,7 +37,7 @@ Audit each individual driver, make sure it'll work with the generic
37
37
implementation (there's lots of outdated locking leftovers in various
38
38
implementations), and then remove it.
39
39
40
- Contact: Daniel Vetter, respective driver maintainers
40
+ Contact: Simona Vetter, respective driver maintainers
41
41
42
42
Level: Intermediate
43
43
@@ -61,7 +61,7 @@ do by directly using the new atomic helper driver callbacks.
61
61
.. [2 ] https://lwn.net/Articles/653071/
62
62
.. [3 ] https://lwn.net/Articles/653466/
63
63
64
- Contact: Daniel Vetter, respective driver maintainers
64
+ Contact: Simona Vetter, respective driver maintainers
65
65
66
66
Level: Advanced
67
67
@@ -75,7 +75,7 @@ helper should also be moved from drm_plane_helper.c to the atomic helpers, to
75
75
avoid confusion - the other helpers in that file are all deprecated legacy
76
76
helpers.
77
77
78
- Contact: Ville Syrjälä, Daniel Vetter, driver maintainers
78
+ Contact: Ville Syrjälä, Simona Vetter, driver maintainers
79
79
80
80
Level: Advanced
81
81
@@ -97,7 +97,7 @@ with the current helpers:
97
97
- Then we could go through all the drivers and remove the more-or-less confused
98
98
checks for plane_state->fb and plane_state->crtc.
99
99
100
- Contact: Daniel Vetter
100
+ Contact: Simona Vetter
101
101
102
102
Level: Advanced
103
103
@@ -116,7 +116,7 @@ Somewhat related is the legacy_cursor_update hack, which should be replaced with
116
116
the new atomic_async_check/commit functionality in the helpers in drivers that
117
117
still look at that flag.
118
118
119
- Contact: Daniel Vetter, respective driver maintainers
119
+ Contact: Simona Vetter, respective driver maintainers
120
120
121
121
Level: Advanced
122
122
@@ -169,7 +169,7 @@ interfaces to fix these issues:
169
169
``_helper_funcs `` since they are not part of the core ABI. There's a
170
170
``FIXME `` comment in the kerneldoc for each such case in ``drm_crtc.h ``.
171
171
172
- Contact: Daniel Vetter
172
+ Contact: Simona Vetter
173
173
174
174
Level: Intermediate
175
175
@@ -194,7 +194,7 @@ performance-critical drivers it might also be better to go with a more
194
194
fine-grained per-buffer object and per-context lockings scheme. Currently only
195
195
the ``msm `` and `i915 ` drivers use ``struct_mutex ``.
196
196
197
- Contact: Daniel Vetter, respective driver maintainers
197
+ Contact: Simona Vetter, respective driver maintainers
198
198
199
199
Level: Advanced
200
200
@@ -251,7 +251,7 @@ being rewritten without dependencies on the fbdev module. Some of the
251
251
helpers could further benefit from using struct iosys_map instead of
252
252
raw pointers.
253
253
254
- Contact: Thomas Zimmermann <
[email protected] >,
Daniel Vetter
254
+ Contact: Thomas Zimmermann <
[email protected] >,
Simona Vetter
255
255
256
256
Level: Advanced
257
257
@@ -297,7 +297,7 @@ Various hold-ups:
297
297
version of the varios drm_gem_fb_create functions. Maybe called
298
298
drm_gem_fb_create/_with_dirty/_with_funcs as needed.
299
299
300
- Contact: Daniel Vetter
300
+ Contact: Simona Vetter
301
301
302
302
Level: Intermediate
303
303
@@ -329,7 +329,7 @@ everything after it has done the write-protect/mkwrite trickery:
329
329
330
330
Might be good to also have some igt testcases for this.
331
331
332
- Contact: Daniel Vetter, Noralf Tronnes
332
+ Contact: Simona Vetter, Noralf Tronnes
333
333
334
334
Level: Advanced
335
335
@@ -359,7 +359,7 @@ between setting up the &drm_driver structure and calling drm_dev_register().
359
359
360
360
- Once all drivers are converted, remove the load/unload callbacks.
361
361
362
- Contact: Daniel Vetter
362
+ Contact: Simona Vetter
363
363
364
364
Level: Intermediate
365
365
@@ -422,7 +422,7 @@ The task is to use struct iosys_map where it makes sense.
422
422
* TTM might benefit from using struct iosys_map internally.
423
423
* Framebuffer copying and blitting helpers should operate on struct iosys_map.
424
424
425
- Contact: Thomas Zimmermann <
[email protected] >, Christian König,
Daniel Vetter
425
+ Contact: Thomas Zimmermann <
[email protected] >, Christian König,
Simona Vetter
426
426
427
427
Level: Intermediate
428
428
@@ -558,7 +558,7 @@ This is a really varied tasks with lots of little bits and pieces:
558
558
<https://lore.kernel.org/lkml/[email protected] /> `_
559
559
for some example code that could be reused.
560
560
561
- Contact: Daniel Vetter
561
+ Contact: Simona Vetter
562
562
563
563
Level: Advanced
564
564
@@ -587,7 +587,7 @@ There's a bunch of issues with it:
587
587
this (together with the drm_minor->drm_device move) would allow us to remove
588
588
debugfs_init.
589
589
590
- Contact: Daniel Vetter
590
+ Contact: Simona Vetter
591
591
592
592
Level: Intermediate
593
593
@@ -608,7 +608,7 @@ Both these problems can be solved by switching over to drmm_kzalloc(), and the
608
608
various convenience wrappers provided, e.g. drmm_crtc_alloc_with_planes(),
609
609
drmm_universal_plane_alloc(), ... and so on.
610
610
611
- Contact: Daniel Vetter
611
+ Contact: Simona Vetter
612
612
613
613
Level: Intermediate
614
614
@@ -628,7 +628,7 @@ cache is also tied to &drm_gem_object.import_attach. Meanwhile we paper over
628
628
this problem for USB devices by fishing out the USB host controller device, as
629
629
long as that supports DMA. Otherwise importing can still needlessly fail.
630
630
631
- Contact: Thomas Zimmermann <
[email protected] >,
Daniel Vetter
631
+ Contact: Thomas Zimmermann <
[email protected] >,
Simona Vetter
632
632
633
633
Level: Advanced
634
634
@@ -709,7 +709,7 @@ Plan to fix this:
709
709
2. In all, only look at one of the three status bits set by the above helpers.
710
710
3. Remove the other two status bits.
711
711
712
- Contact: Daniel Vetter
712
+ Contact: Simona Vetter
713
713
714
714
Level: Intermediate
715
715
0 commit comments