Hi Christian,
The latest driver fails to load on SRIOV VF with xen hypervisor driver.
+int amdgpu_device_resize_fb_bar(struct amdgpu_device *adev)
+{
+ u64 space_needed = roundup_pow_of_two(adev->mc.real_vram_size);
+ u32 rbar_size = order_base_2(((space_needed >> 20) | 1)) - 1;
+
Static analysis tools get annoyed that we don't indent this if
statement. Actually, the if statement isn't required because kfree()
can handle NULL pointers just fine. The DCE110STRENC_FROM_STRENC()
macro is a wrapper around container_of() but it's basically a no-op or a
cast. Anyway, it's not
Hi Andres,
With your this patch, OCLperf hung.
Could you explain more?
If I am correctly, the difference of with and without this patch is
setting first two queue or setting all queues of pipe0 to queue_bitmap.
Then UMD can use different number queue to submit command for compute
selected
On Sat, Nov 04, 2017 at 10:16:23AM +0100, walter harms wrote:
>
>
> Am 04.11.2017 07:12, schrieb Dan Carpenter:
> > The if statement wasn't indented so it makes static analysis tools and
> > probably very recent GCC versions complain.
> >
> > Signed-off-by: Dan Carpenter
Hi Martin:
The log do not have any useful information. For S3 issue I think you can do:
1. Do you have any other AMD GFX? such as Bonaire or Tonga. Please have a try
with the some driver.
2. Do you have a chance to set up com port? The com port is very useful for
debugging S3 issue.
a.
For clarity, are you saying that when you go back to whatever distro you had
installed on the machine previously it is still not booting correctly ?
The only problems I see in the xorg log are the following lines at the end, but
not sure if they are serious or not.
[ 205.542] (WW)
Hi Dave,
A few more fixes for 4.15.
The following changes since commit bf6eb600e5b835a96d676b2b9df603362a1e714c:
Merge branch 'linux-4.15' of git://github.com/skeggsb/linux into drm-next
(2017-11-03 09:17:08 +1000)
are available in the git repository at:
On Thu, Nov 2, 2017 at 5:22 PM, Felix Kuehling wrote:
> Thanks.
>
> I've given up on targeting a specific kernel release. This whole
> upstreaming process is way more work than I expected, and is taking much
> longer than I thought when I started. If I'm making this harder