From: Jani Nikula <jani.nikula@linux.intel.com>
To: John Sledge <john_sledget@yahoo.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: DRM Inquiry
Date: Thu, 24 May 2018 14:23:27 +0300 [thread overview]
Message-ID: <87r2m1jo0g.fsf@intel.com> (raw)
In-Reply-To: <524712366.665006.1527159421984@mail.yahoo.com>
On Thu, 24 May 2018, John Sledge <john_sledget@yahoo.com> wrote:
> I was able to update my kernel to 4.6 which has the DRM_DP_AUX_CHARDEV
> in the Kconfig file linux-4.6\drivers\gpu\drm. Though I also
> add DRM_DP_AUX_CHARDEV=y in kernel config. When invoke uname -r, I
> could see that the kernel is now 4.6.
If you're updating kernels, why not update to a recent kernel that's
actually supported...?
> How can I verify the DRM_DP_AUX_CHARDEV takes effect or got configure
> it correctly?
Boot the kernel, run 'ls /dev/drm_dp_aux*'. If you see stuff, you got it
right.
> It still unclear to me how to follow what you mean by using DRM DP AUX
> interface and getting /dev/drm_dp_auxN node(s) that allows me to read
> and write arbitrary DPCD offsets.
The device is a char device you can open, seek to an offset (which would
be the DPCD offset), and read. For testing, you can achieve the same
using dd.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-05-24 11:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <471791572.2287221.1526561265798.ref@mail.yahoo.com>
2018-05-17 12:47 ` DRM Inquiry John Sledge
2018-05-18 9:50 ` Jani Nikula
2018-05-24 4:19 ` John Sledge
2018-05-24 10:57 ` John Sledge
2018-05-24 11:23 ` Jani Nikula [this message]
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
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=87r2m1jo0g.fsf@intel.com \
--to=jani.nikula@linux.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 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.