All of lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 11 Jun 2018 14:36:38 +0300	[thread overview]
Message-ID: <87efhd4ks9.fsf@intel.com> (raw)
In-Reply-To: <347606627.3373105.1528712212657@mail.yahoo.com>

On Mon, 11 Jun 2018, John Sledge <john_sledget@yahoo.com> wrote:
> 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 the code, I notice character device will be
> created under drm_dp_aux_register_devnode method.
> For example I made two kernel 4.6 with DRM_DP_AUX_CHARDEV=y and
> another kernel 4.6 with DRM_DP_AUX_CHARDEV=n. 
> So the steps was to build and install the kernel with
> DRM_DP_AUX_CHARDEV=y. Once finish, I tried to reboot and verified the
> /dev/drm_dp_aux_chardev* and it was there.
> Now, I will change the .config DRM_DP_AUXCHARDEV=n then follow the
> steps below to manual build the DRM module. I'm not really sure if I'm
> correct on this one.

Why are you disabling it again? Just enable the config, use the
resulting kernel, and do the rest in userspace.

> 1. rm /dev/drm_dp_aux_chardev* 2. make modules_prepare3. make
> SUBDIRS=scripts/mod4. make SUBDIRS=drivers/gpu/drm modules5. cp
> drivers/gpu/drm/i915/i915.ko
> /lib/modules/4.6.0-94.11-default/kernel/drivers/gpu/drm6. ... I copy
> all .ko under drm to the lib/modules/4.67. depmod8. modprobe
> i9159. ... I also modprobe all modules10. reboot
> The result was /dev/drm_dp_aux_chardev* was still there. My
> expectation was it would disrepair or remove.

Don't do this. I don't understand what you're trying to do.

> Please have comments and advice.

Please explain what you're trying to do to begin with. What's your end
goal?

BR,
Jani.


PS. Please prefer plain text instead of html on the list.


-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-06-11 11:36 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
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 [this message]
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=87efhd4ks9.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 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.