From: Jani Nikula <jani.nikula@linux.intel.com>
To: John Sledge <john_sledget@yahoo.com>,
"Taylor, Clinton A" <clinton.a.taylor@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: RE: [Intel-gfx] DRM Inquiry
Date: Wed, 13 Jun 2018 10:07:04 +0300 [thread overview]
Message-ID: <87po0v17xj.fsf@intel.com> (raw)
In-Reply-To: <1298594041.4470364.1528855624318@mail.yahoo.com>
On Wed, 13 Jun 2018, John Sledge <john_sledget@yahoo.com> wrote:
> I like to understand how the DRM_DP_AUX_CHARDEV=y kick off.
Try 'git grep DRM_DP_AUX_CHARDEV' in your kernel git repo, and see how
it affects conditional compilation.
This list isn't kernel development 101.
You still didn't say what your end goal is. Forget everything about DP
AUX and the chardev and so on, just tell us what you're trying to
achieve. Maybe you're asking about X, but you really want to know about
Y.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-06-13 7:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <471791572.2287221.1526561265798.ref@mail.yahoo.com>
[not found] ` <471791572.2287221.1526561265798@mail.yahoo.com>
2018-05-18 9:50 ` DRM Inquiry Jani Nikula
2018-05-24 4:19 ` John Sledge
2018-05-24 10:57 ` John Sledge
2018-05-24 11:23 ` Jani Nikula
2018-05-25 6:36 ` John Sledge
2018-05-25 6:55 ` Jani Nikula
2018-05-25 8:11 ` John Sledge
2018-05-25 8:33 ` Jani Nikula
2018-05-25 15:56 ` Taylor, Clinton A
2018-05-25 17:14 ` Jani Nikula
2018-06-11 10:16 ` RE: [Intel-gfx] " John Sledge
2018-06-11 11:36 ` Jani Nikula
2018-06-13 2:07 ` John Sledge
2018-06-13 7:07 ` Jani Nikula [this message]
2018-06-13 8:21 ` John Sledge
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=87po0v17xj.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=clinton.a.taylor@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=john_sledget@yahoo.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).