From: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
To: Inki Dae <inki.dae@samsung.com>
Cc: Joonyoung Shim <jy0922.shim@samsung.com>,
Seung-Woo Kim <sw0312.kim@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Kukjin Kim <kgene.kim@samsung.com>,
linux-samsung-soc@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/3] drm/exynos: Allow module to be autoloaded
Date: Mon, 28 Jul 2014 16:45:22 +0200 [thread overview]
Message-ID: <1406558722.29009.11.camel@dusk> (raw)
In-Reply-To: <53D65B5D.1060505@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
Hey Inki,
On Mon, 2014-07-28 at 23:17 +0900, Inki Dae wrote:
> On 2014년 07월 28일 17:30, Sjoerd Simons wrote:
> Sorry for late,
>
> I don't see why Exynos drm driver should be auto-loaded module. I think
> all devices covered by Exynos drm framework are not hot-plugged. Maybe
> there is my missing point. So can you explain why Exynos drm driver
> should be auto-loaded module?
The background for this is that I'm building a distribution-style
multiplatform kernel, that is to say a kernel which can boot on a big
set of different ARM boards. As such, the intention is to keep the core
zImage as small as possible and essentially build things as far as
possible as loadable modules. So in a sense, all of the hardware is
"hotplugged", depending on which board the kernel is actually booted on!
For that use-case, exynosdrm needs to be able to build as a module
(which it already can!) and it needs the required meta-data for
userspace to know when it should be loaded. The latter is what my patch
adds.
--
Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Collabora Ltd.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 6170 bytes --]
next prev parent reply other threads:[~2014-07-28 14:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 20:36 [PATCH 0/3] drm/exynos: Allow module to be autoloaded Sjoerd Simons
2014-07-18 20:36 ` [PATCH 1/3] Revert "drm/exynos: fix module build error" Sjoerd Simons
2014-07-18 20:36 ` [PATCH 2/3] Revert "drm/exynos: remove MODULE_DEVICE_TABLE definitions" Sjoerd Simons
2014-07-18 20:36 ` [PATCH 3/3] drm/exynos: Add MODULE_DEVICE_TABLE entries for various components Sjoerd Simons
2014-07-21 3:02 ` [PATCH 0/3] drm/exynos: Allow module to be autoloaded Inki Dae
2014-07-21 6:50 ` Sjoerd Simons
2014-07-28 8:30 ` Sjoerd Simons
2014-07-28 14:17 ` Inki Dae
2014-07-28 14:45 ` Sjoerd Simons [this message]
2014-07-29 5:38 ` Inki Dae
2014-07-29 8:05 ` Sjoerd Simons
2014-07-29 11:59 ` Andreas Färber
2014-07-29 12:29 ` Inki Dae
2014-07-29 13:43 ` Daniel Stone
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=1406558722.29009.11.camel@dusk \
--to=sjoerd.simons@collabora.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=jy0922.shim@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=sw0312.kim@samsung.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.