From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: "Li.Xiubo@freescale.com" <Li.Xiubo@freescale.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
"plagnioj@jcrosoft.com" <plagnioj@jcrosoft.com>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"shawn.guo@linaro.org" <shawn.guo@linaro.org>,
"alexander.stein@systec-electronic.com"
<alexander.stein@systec-electronic.com>
Subject: Re: [PATCHv2 0/4] LS1021A: Add dcfb framebuffer driver support.
Date: Thu, 04 Dec 2014 09:09:27 +0000 [thread overview]
Message-ID: <548024C7.3060004@ti.com> (raw)
In-Reply-To: <BY2PR0301MB0613ABEA1410C04CF07C1C7C9B780@BY2PR0301MB0613.namprd03.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1585 bytes --]
On 04/12/14 10:30, Li.Xiubo@freescale.com wrote:
> Sorry for confusing, it was delayed for other reasons internal.
>
> I am not familiar about the DRM, and I'd like to know if the DRM driver will be
> support, should I also develop the libdrm too ? Or just coding in kernel level ?
For simple drm drivers (this looks like it would be a simple one), I
don't think there's any need for libdrm support. The generic DRM
interfaces should be enough, so just kernel level coding needed.
> Is there any Document about how to have /dev/fbX device to use ?
There's DRM documentation here:
https://www.kernel.org/doc/htmldocs/drm/index.html
And many existing drivers to use as examples. The dri-devel list
(http://lists.freedesktop.org/mailman/listinfo/dri-devel), which is the
mailing list used for DRM development, is active and you probably can
get more support from there than from the fbdev list.
It should not be a huge effort to write a drm driver for a simple LCD
controller like this. I would bet that you can write a working driver in
a week.
> If possible, I'd like this could be accept for this time. And I will add the DRM
> Version later(for developing and testing will take a long time).
I'm sorry but "it was delayed for internal reasons" and "our customer
needs this driver" are not very good reasons for getting a driver merged
to mainline Linux.
You can provide your driver to your customer as a separate patch series
which they can apply. There should be no conflicts or other issues
there, so it should be simple.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-12-04 9:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 9:15 [PATCHv2 0/4] LS1021A: Add dcfb framebuffer driver support Xiubo Li
2014-12-03 9:15 ` [PATCHv2 1/4] video: fsl-dcfb: Add dcfb framebuffer driver for LS1021A platform Xiubo Li
2014-12-04 9:21 ` Alexander Stein
2014-12-03 9:16 ` [PATCHv2 2/4] video: fsl-dcfb: Add devicetree binding support Xiubo Li
2014-12-03 9:16 ` [PATCHv2 3/4] ARM: ls1021a: dtsi: Add dt node support for dcfb Xiubo Li
2014-12-03 9:16 ` [PATCHv2 4/4] ARM: ls1021a: dts: Add and enable dt node " Xiubo Li
2014-12-03 9:51 ` [PATCHv2 0/4] LS1021A: Add dcfb framebuffer driver support Arnd Bergmann
2014-12-04 1:56 ` Li.Xiubo
2014-12-04 8:10 ` Tomi Valkeinen
2014-12-04 8:30 ` Li.Xiubo
2014-12-04 9:09 ` Tomi Valkeinen [this message]
2014-12-04 9:54 ` Li.Xiubo
2014-12-04 9:59 ` Tomi Valkeinen
2014-12-04 10:03 ` Li.Xiubo
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=548024C7.3060004@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=Li.Xiubo@freescale.com \
--cc=alexander.stein@systec-electronic.com \
--cc=arnd@arndb.de \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
--cc=shawn.guo@linaro.org \
/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).