From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: OMAP display kconfig options changing
Date: Fri, 18 Dec 2015 18:14:19 +0200 [thread overview]
Message-ID: <567430DB.4000507@ti.com> (raw)
In-Reply-To: <20151218160514.GK23396@atomide.com>
[-- Attachment #1.1: Type: text/plain, Size: 803 bytes --]
On 18/12/15 18:05, Tony Lindgren wrote:
>> Are you referring to Kconfig options? Or userspace?
>
> Well sounds like both need updating :)
Depends... For simple fb apps, omapdrm works fine, and X with the
standard fbdev driver should work with omapdrm too.
But if the userspace is using any omapfb specific apps, then yes, update
is necessary.
>> But no, I don't have links to either.
>
> So change the Kconfig options and then deal with the flood
> of angry emails? :) I think we need instructions..
Ok. I think it's then best that I just update the defconfig to enable
omapfb as modules, as it is currently.
We can look again at changing the default to omapdrm after we've tested
it on OMAP2 too, and we have a better idea what the user needs to take
care of.
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 prev parent reply other threads:[~2015-12-18 16:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 8:55 OMAP display kconfig options changing Tomi Valkeinen
2015-12-18 13:53 ` 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 [this message]
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=567430DB.4000507@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).