nnel.
The second advice, I guess your correct since the display device i needed to
communicate is under Connector: DP-1 and not in Connector: eDP-1. This is based
on the application modeprint result.
Regards,John
On Friday, May 18, 2018, 5:48:31 PM GMT+8, Jani Nikula
wrote:
On Thu,
PM GMT+8, John Sledge
wrote:
Hi Jani,
Good day!
Thank you for taking the time to point out those information. It’s a great help
to me.
Also apologies for the late reply, your first reply went to my spam inbox, not
sure what happen and I was waiting for replies for days.
I'm still n
ntf("ioctl success");
}
return 0;}
Thanks,John
On Thursday, May 24, 2018, 8:38:02 PM GMT+8, Jani Nikula
wrote:
On Thu, 24 May 2018, John Sledge 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
t;> out.txt",offset); ret = system(call); }return 0;}
Regards,John
On Friday, May 25, 2018, 2:56:04 PM GMT+8, Jani Nikula
wrote:
On Fri, 25 May 2018, John Sledge wrote:
> Hi Jani,
> I can now see /dev/drm_dp_aux*.
> I'm not familiar with dd command.Correct
Hi Jani,
Thanks for the help. I was able to manage your advice on the
drm_dp_aux_chardev. Though I still need to learn more about the DRM vs kernel
process flow. Like for example, upon changing/adding DRM_DP_AUX_CHARDEV in
kernel .config, How did DRM_DP_AUX_CHARDEV was being invoke here? From t
Hi Jani,
I like to understand how the DRM_DP_AUX_CHARDEV=y kick off.
Regards,John
On Monday, June 11, 2018, 7:36:51 PM GMT+8, Jani Nikula
wrote:
On Mon, 11 Jun 2018, John Sledge wrote:
> Thanks for the help. I was able to manage your advice on the
> drm_dp_aux_chardev. Th
hanks,John
On Wednesday, June 13, 2018, 3:07:14 PM GMT+8, Jani Nikula
wrote:
On Wed, 13 Jun 2018, John Sledge 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
