More specific libdrm error message

Xie, AlexBin AlexBin.Xie at amd.com
Mon Jan 16 22:00:41 UTC 2017


Hi Emil,


Thanks for the advice. I noticed that you have changed some tests using drmGetDevices2.

I mark this to my to do list.


Thanks,

Alex Bin Xie

________________________________
From: Emil Velikov <emil.l.velikov at gmail.com>
Sent: Thursday, January 12, 2017 2:26 PM
To: Edward O'Callaghan
Cc: Xie, AlexBin; amd-gfx at lists.freedesktop.org
Subject: Re: More specific libdrm error message

On 12 January 2017 at 01:29, Edward O'Callaghan
<funfunctor at folklore1984.net> wrote:
> Hi Xie,
>
> Perhaps you want to use `fprintf(stderr, "...")` over `printf("..")` and
> lose the space before the start parenthesis. Also, line wrap
> your commit message.
>
> Side note, use git send-email so that the patch is inline and not a HTML
> email for easy review and application of the patch.
>
Thanks Edward.

Xie, suggesting to run almost anything as root is a bad idea ;-)
Instead one could auth, in order to have the correct permissions.
Alternatively can use the renderD node all together.

Idea for future work:
Would be even better to use drmGetDevices2 to fetch all the devices
and use the correct node since card0/renderD128 is not guaranteed to
be a amdgpu one. Or maybe even run all the amdgpu devices through the
tests ?

Please correctly wrap commit messages and code.

Thanks
Emil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/amd-gfx/attachments/20170116/5285fee7/attachment.html>


More information about the amd-gfx mailing list