From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Tony Lindgren <tony@atomide.com>, linux-omap@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org
Subject: OMAP display kconfig options changing
Date: Fri, 18 Dec 2015 10:55:41 +0200 [thread overview]
Message-ID: <5673CA0D.4000706@ti.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 535 bytes --]
Hi Tony,
I've just pushed a patch series to fbdev for-next branch which makes the
OMAP DRM and FB drivers independent of each other. This requires
changing the related Kconfig options.
What should I do with omap2plus_defconfig?
At the moment omap2plus_defconfig enables the omapfb driver and panels
as modules. Should I change it to do the same with the new code? Or
should I change it to use omapdrm, which is the better maintained and
developed driver (although no one has probably tried omapdrm on omap2)?
Tomi
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2015-12-18 8:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 8:55 Tomi Valkeinen [this message]
2015-12-18 13:53 ` OMAP display kconfig options changing Tony Lindgren
2015-12-18 14:03 ` Adam Ford
2015-12-18 15:04 ` Tomi Valkeinen
2015-12-18 15:00 ` Tomi Valkeinen
2015-12-18 16:05 ` Tony Lindgren
2015-12-18 16:14 ` Tomi Valkeinen
2015-12-22 21:18 ` Javier Martinez Canillas
2015-12-29 10:23 ` Tomi Valkeinen
2015-12-29 12:13 ` Javier Martinez Canillas
2016-01-21 21:51 ` Tony Lindgren
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=5673CA0D.4000706@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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 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).