All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emil Velikov <emil.l.velikov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "StDenis, Tom" <Tom.StDenis-5C7GfCeVMHo@public.gmane.org>
Cc: Tom St Denis <tstdenis82-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	amd-gfx mailing list
	<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: [PATCH] Autodetect libdrm path (v2)
Date: Tue, 7 Feb 2017 11:02:17 +0000	[thread overview]
Message-ID: <CACvgo537ciLvg=Q6enktu6ndMSEuSCM+RpmniJdgYNgZDQjUeQ@mail.gmail.com> (raw)
In-Reply-To: <CY4PR12MB1768AED537A0253EB70B1E4BF7400-rpdhrqHFk06yjjPBNVDk/QdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>

On 6 February 2017 at 22:39, StDenis, Tom <Tom.StDenis@amd.com> wrote:
>
> Apparently I missed the bottom of your reply (all of the clients I have outlook/gmail do top post only ...)
Both Outlook and Gmail can do inline replies and plain text. There
might be some magic required for the former though :-\
I would kindly suggest using inline/text when possible.

> as for the cmake changes. I'm for it if you want to submit a patch.  I can't imagine a lot of cross compiling though since users will typically be using it on the platform they built it for.
>
>
> Ironically, I had the pkg_check originally but was told that's a faux-pas.
>
It's a common misconception, influenced by the sheer volume of copy/paste :-)

>
> Unless this is breaking for actual users though it's not really a priority to bikeshed the build system of a 30 file project that is meant to work only on developer machines who are likely building for themselves
>
Up-to you really. FWIW using cmake/autoconf/etc. is a huge overkill.
The original makefile was missing a few things* worth 10-20 lines of
code while being noticeably smaller, quicker and easier to read ;-)

* Dependency tracking (pkg-config + foo.pc), incremental builds - ($CC
... -MM -MP ...), tarballs.

> Tom
>
> ________________________________
> From: amd-gfx <amd-gfx-bounces@lists.freedesktop.org> on behalf of StDenis, Tom <Tom.StDenis@amd.com>
> Sent: Monday, February 6, 2017 16:33
> To: Emil Velikov; Tom St Denis
> Cc: amd-gfx mailing list
>
> Subject: Re: [PATCH] Autodetect libdrm path (v2)
>
>
> I have to NAK that idea since we use umr on NPI work which doesn't necessarily have libdrm support.
>
>
> Also umr can read/write registers via pci access without amdgpu loaded (handy if amdgpu fails to init properly).
>
Must have missed this part. Thanks for the correction.

>
> Though you are right that libdrm is technically a requirement and I should add that to the README.
>
Ack.

Thanks
Emil
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  parent reply	other threads:[~2017-02-07 11:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-05 22:24 [PATCH] Autodetect libdrm path (v2) Tom St Denis
     [not found] ` <20170205222447.19945-1-tom.stdenis-5C7GfCeVMHo@public.gmane.org>
2017-02-05 22:28   ` Andres Rodriguez
     [not found]     ` <62ec2a45-ea86-a643-f7fd-3e5e5054540b-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-02-05 22:42       ` StDenis, Tom
2017-02-06 20:18   ` Emil Velikov
     [not found]     ` <CACvgo5230Use5sk8dm5jBbLqiJeSkgB6cDikz-N4omx-4Jgy9A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-06 21:33       ` StDenis, Tom
     [not found]         ` <CY4PR12MB17689AEC15DEF9662A16DEA3F7400-rpdhrqHFk06yjjPBNVDk/QdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-02-06 22:39           ` StDenis, Tom
     [not found]             ` <CY4PR12MB1768AED537A0253EB70B1E4BF7400-rpdhrqHFk06yjjPBNVDk/QdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-02-07 11:02               ` Emil Velikov [this message]
     [not found]                 ` <CACvgo537ciLvg=Q6enktu6ndMSEuSCM+RpmniJdgYNgZDQjUeQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-07 11:30                   ` Tom St Denis
     [not found]                     ` <13f9479c-1a5c-8887-858e-dadf819a7140-5C7GfCeVMHo@public.gmane.org>
2017-02-07 12:41                       ` Emil Velikov
2017-02-08  0:48                       ` Michel Dänzer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CACvgo537ciLvg=Q6enktu6ndMSEuSCM+RpmniJdgYNgZDQjUeQ@mail.gmail.com' \
    --to=emil.l.velikov-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=Tom.StDenis-5C7GfCeVMHo@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=tstdenis82-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.