<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/gpu/drm/vmwgfx, branch linux-5.9.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.9.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.9.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2020-09-30T03:44:28Z</updated>
<entry>
<title>drm/vmwgfx: Fix error handling in get_node</title>
<updated>2020-09-30T03:44:28Z</updated>
<author>
<name>Zack Rusin</name>
</author>
<published>2020-09-25T15:54:10Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f54c4442893b8dfbd3aff8e903c54dfff1aef990'/>
<id>urn:sha1:f54c4442893b8dfbd3aff8e903c54dfff1aef990</id>
<content type='text'>
ttm_mem_type_manager_func.get_node was changed to return -ENOSPC
instead of setting the node pointer to NULL. Unfortunately
vmwgfx still had two places where it was explicitly converting
-ENOSPC to 0 causing regressions. This fixes those spots by
allowing -ENOSPC to be returned. That seems to fix recent
regressions with vmwgfx.

Signed-off-by: Zack Rusin &lt;zackr@vmware.com&gt;
Reviewed-by: Roland Scheidegger &lt;sroland@vmware.com&gt;
Reviewed-by: Martin Krastev &lt;krastevm@vmware.com&gt;
Sigend-off-by: Roland Scheidegger &lt;sroland@vmware.com&gt;
</content>
</entry>
<entry>
<title>drm/vmwgfx: fix spelling mistake "Cant" -&gt; "Can't"</title>
<updated>2020-08-11T01:16:03Z</updated>
<author>
<name>Colin Ian King</name>
</author>
<published>2020-08-10T10:04:01Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e97644ebcdc83854e6e29e96285b25042445c28c'/>
<id>urn:sha1:e97644ebcdc83854e6e29e96285b25042445c28c</id>
<content type='text'>
There is a spelling mistake in a DRM_ERROR message. Fix it.

Signed-off-by: Colin Ian King &lt;colin.king@canonical.com&gt;
Signed-off-by: Roland Scheidegger &lt;sroland@vmware.com&gt;
</content>
</entry>
<entry>
<title>drm/vmwgfx: fix spelling mistake "Cound" -&gt; "Could"</title>
<updated>2020-08-11T01:16:03Z</updated>
<author>
<name>Colin Ian King</name>
</author>
<published>2020-08-05T11:31:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1ae96fce3e4dfe769515350b7f142b3bca1e0bb6'/>
<id>urn:sha1:1ae96fce3e4dfe769515350b7f142b3bca1e0bb6</id>
<content type='text'>
There is a spelling mistake in a DRM_ERROR message. Fix it.

Signed-off-by: Colin Ian King &lt;colin.king@canonical.com&gt;
Signed-off-by: Roland Scheidegger &lt;sroland@vmware.com&gt;
</content>
</entry>
<entry>
<title>drm/vmwgfx/ldu: Use drm_mode_config_reset</title>
<updated>2020-08-11T01:16:03Z</updated>
<author>
<name>Roland Scheidegger</name>
</author>
<published>2020-08-07T20:04:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=981243371a5d832af5bc572071172e955d02fe88'/>
<id>urn:sha1:981243371a5d832af5bc572071172e955d02fe88</id>
<content type='text'>
Same problem as in stdu, same fix.

Fixes: 51f644b40b4b ("drm/atomic-helper: reset vblank on crtc reset")
Acked-by: Charmaine Lee &lt;charmainel@vmware.com&gt;
Reviewed-by: Zack Rusin &lt;zackr@vmware.com&gt;
Signed-off-by: Roland Scheidegger &lt;sroland@vmware.com&gt;
</content>
</entry>
<entry>
<title>drm/vmwgfx/sou: Use drm_mode_config_reset</title>
<updated>2020-08-11T01:16:02Z</updated>
<author>
<name>Roland Scheidegger</name>
</author>
<published>2020-08-07T20:03:42Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1338441cf166e2ef789af5915b961d4e13a4ec31'/>
<id>urn:sha1:1338441cf166e2ef789af5915b961d4e13a4ec31</id>
<content type='text'>
Same problem as in stdu, same fix.

Fixes: 51f644b40b4b ("drm/atomic-helper: reset vblank on crtc reset")
Acked-by: Charmaine Lee &lt;charmainel@vmware.com&gt;
Reviewed-by: Zack Rusin &lt;zackr@vmware.com&gt;
Signed-off-by: Roland Scheidegger &lt;sroland@vmware.com&gt;
</content>
</entry>
<entry>
<title>drm/vmwgfx/stdu: Use drm_mode_config_reset</title>
<updated>2020-08-11T01:16:02Z</updated>
<author>
<name>Daniel Vetter</name>
</author>
<published>2020-08-06T15:42:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=68745d1edf1700a668c15ecbed466d18f14c7e9b'/>
<id>urn:sha1:68745d1edf1700a668c15ecbed466d18f14c7e9b</id>
<content type='text'>
When converting to atomic the state reset was done by directly calling
the functions, and before the modeset object was fully initialized.
This means the various -&gt;dev pointers weren't set up.

After

commit 51f644b40b4b794b28b982fdd5d0dd8ee63f9272
Author: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Date:   Fri Jun 12 18:00:49 2020 +0200

    drm/atomic-helper: reset vblank on crtc reset

this started to oops because now we're trying to derefence
drm_crtc-&gt;dev. Fix this up by entirely switching over to
drm_mode_config_reset, called once everything is set up.

Fixes: 51f644b40b4b ("drm/atomic-helper: reset vblank on crtc reset")
Reported-by: Tetsuo Handa &lt;penguin-kernel@i-love.sakura.ne.jp&gt;
Cc: Tetsuo Handa &lt;penguin-kernel@i-love.sakura.ne.jp&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@intel.com&gt;
Tested-by: Roland Scheidegger &lt;sroland@vmware.com&gt;
Signed-off-by: Roland Scheidegger &lt;sroland@vmware.com&gt;
</content>
</entry>
<entry>
<title>drm/vmwgfx: Fix two list_for_each loop exit tests</title>
<updated>2020-08-11T01:16:02Z</updated>
<author>
<name>Dan Carpenter</name>
</author>
<published>2020-06-26T10:39:59Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4437c1152ce0e57ab8f401aa696ea6291cc07ab1'/>
<id>urn:sha1:4437c1152ce0e57ab8f401aa696ea6291cc07ab1</id>
<content type='text'>
These if statements are supposed to be true if we ended the
list_for_each_entry() loops without hitting a break statement but they
don't work.

In the first loop, we increment "i" after the "if (i == unit)" condition
so we don't necessarily know that "i" is not equal to unit at the end of
the loop.

In the second loop we exit when mode is not pointing to a valid
drm_display_mode struct so it doesn't make sense to check "mode-&gt;type".

Fixes: a278724aa23c ("drm/vmwgfx: Implement fbdev on kms v2")
Signed-off-by: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Reviewed-by: Roland Scheidegger &lt;sroland@vmware.com&gt;
Signed-off-by: Roland Scheidegger &lt;sroland@vmware.com&gt;
</content>
</entry>
<entry>
<title>drm/vmwgfx: Use correct vmw_legacy_display_unit pointer</title>
<updated>2020-08-11T01:16:02Z</updated>
<author>
<name>Dan Carpenter</name>
</author>
<published>2020-06-26T10:34:37Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1d2c0c565bc0da25f5e899a862fb58e612b222df'/>
<id>urn:sha1:1d2c0c565bc0da25f5e899a862fb58e612b222df</id>
<content type='text'>
The "entry" pointer is an offset from the list head and it doesn't
point to a valid vmw_legacy_display_unit struct.  Presumably the
intent was to point to the last entry.

Also the "i++" wasn't used so I have removed that as well.

Fixes: d7e1958dbe4a ("drm/vmwgfx: Support older hardware.")
Signed-off-by: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Reviewed-by: Roland Scheidegger &lt;sroland@vmware.com&gt;
Signed-off-by: Roland Scheidegger &lt;sroland@vmware.com&gt;
</content>
</entry>
<entry>
<title>drm/vmwgfx: Use struct_size() helper</title>
<updated>2020-08-11T01:16:02Z</updated>
<author>
<name>Gustavo A. R. Silva</name>
</author>
<published>2020-06-17T21:51:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4f88b4ccb7036ce523b3c031d1226d6eda36417b'/>
<id>urn:sha1:4f88b4ccb7036ce523b3c031d1226d6eda36417b</id>
<content type='text'>
Make use of the struct_size() helper instead of an open-coded version
in order to avoid any potential type mistakes.

This code was detected with the help of Coccinelle and, audited and
fixed manually.

Signed-off-by: Gustavo A. R. Silva &lt;gustavoars@kernel.org&gt;
Signed-off-by: Roland Scheidegger &lt;sroland@vmware.com&gt;
</content>
</entry>
<entry>
<title>drm/ttm: ttm_bo_swapout_all doesn't use it's argument.</title>
<updated>2020-07-29T00:01:23Z</updated>
<author>
<name>Dave Airlie</name>
</author>
<published>2020-07-28T03:42:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ec731e516acf22ce870b735721c6f59e39d0ed44'/>
<id>urn:sha1:ec731e516acf22ce870b735721c6f59e39d0ed44</id>
<content type='text'>
Just drop the argument from this.

This does ask the question if this is the function vmwgfx
should be using or should it be doing an evict all like
the other drivers.

Reviewed-by: Christian König &lt;christian.koenig@amd.com&gt;
Reviewed-by: Zack Rusin &lt;zackr@vmware.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20200728034254.20114-1-airlied@gmail.com
</content>
</entry>
</feed>
