From: Javier Martinez Canillas <javier@dowhile0.org> To: Tomi Valkeinen <tomi.valkeinen@ti.com> Cc: Tony Lindgren <tony@atomide.com>, "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org> Subject: Re: OMAP display kconfig options changing Date: Tue, 22 Dec 2015 18:18:30 -0300 [thread overview] Message-ID: <CABxcv==VKi5jJ7=tEBe5fiPUpqpmaBd7C=t+_JohdXLA7eMR2Q@mail.gmail.com> (raw) In-Reply-To: <567430DB.4000507@ti.com> Hello Tomi, On Fri, Dec 18, 2015 at 1:14 PM, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote: > 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. > It does, I just tested omapdrm + X with the fbdev DDX and I was able to start X and the xfce4 wm. I just needed to enable DRM_FBDEV_EMULATION in omap2plus_defconfig to have fbdev emulation over DRM. > But if the userspace is using any omapfb specific apps, then yes, update > is necessary. > Yes but these people should have a migration plan anyways since omapfb (and fbdev in general) is going away right? >>> 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. > In that case I think you should squash the defconfig changes with commit ("70ba4e05531f omapfb/displays: change CONFIG_DISPLAY_* to CONFIG_FB_OMAP2_*") to maintain bisectability. Alternatively, the current panel and encoders Kconfig symbols could remain for omapfb since that's the current ones used in omap2plus_defconfig where omapfb is the default and have new Kconfig symbols for omapdrm (i.e: CONFIG_DRM_OMAP_ENCODER_TFP410). > 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 > Best regards, Javier
WARNING: multiple messages have this Message-ID (diff)
From: javier@dowhile0.org (Javier Martinez Canillas) To: linux-arm-kernel@lists.infradead.org Subject: OMAP display kconfig options changing Date: Tue, 22 Dec 2015 18:18:30 -0300 [thread overview] Message-ID: <CABxcv==VKi5jJ7=tEBe5fiPUpqpmaBd7C=t+_JohdXLA7eMR2Q@mail.gmail.com> (raw) In-Reply-To: <567430DB.4000507@ti.com> Hello Tomi, On Fri, Dec 18, 2015 at 1:14 PM, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote: > 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. > It does, I just tested omapdrm + X with the fbdev DDX and I was able to start X and the xfce4 wm. I just needed to enable DRM_FBDEV_EMULATION in omap2plus_defconfig to have fbdev emulation over DRM. > But if the userspace is using any omapfb specific apps, then yes, update > is necessary. > Yes but these people should have a migration plan anyways since omapfb (and fbdev in general) is going away right? >>> 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. > In that case I think you should squash the defconfig changes with commit ("70ba4e05531f omapfb/displays: change CONFIG_DISPLAY_* to CONFIG_FB_OMAP2_*") to maintain bisectability. Alternatively, the current panel and encoders Kconfig symbols could remain for omapfb since that's the current ones used in omap2plus_defconfig where omapfb is the default and have new Kconfig symbols for omapdrm (i.e: CONFIG_DRM_OMAP_ENCODER_TFP410). > 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 > Best regards, Javier
next prev parent reply other threads:[~2015-12-22 21:18 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-12-18 8:55 OMAP display kconfig options changing Tomi Valkeinen 2015-12-18 8:55 ` Tomi Valkeinen 2015-12-18 13:53 ` Tony Lindgren 2015-12-18 13:53 ` Tony Lindgren 2015-12-18 14:03 ` Adam Ford 2015-12-18 14:03 ` Adam Ford 2015-12-18 15:04 ` Tomi Valkeinen 2015-12-18 15:04 ` Tomi Valkeinen 2015-12-18 15:00 ` Tomi Valkeinen 2015-12-18 15:00 ` Tomi Valkeinen 2015-12-18 16:05 ` Tony Lindgren 2015-12-18 16:05 ` Tony Lindgren 2015-12-18 16:14 ` Tomi Valkeinen 2015-12-18 16:14 ` Tomi Valkeinen 2015-12-22 21:18 ` Javier Martinez Canillas [this message] 2015-12-22 21:18 ` Javier Martinez Canillas 2015-12-29 10:23 ` Tomi Valkeinen 2015-12-29 10:23 ` Tomi Valkeinen 2015-12-29 12:13 ` Javier Martinez Canillas 2015-12-29 12:13 ` Javier Martinez Canillas 2016-01-21 21:51 ` Tony Lindgren 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='CABxcv==VKi5jJ7=tEBe5fiPUpqpmaBd7C=t+_JohdXLA7eMR2Q@mail.gmail.com' \ --to=javier@dowhile0.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-omap@vger.kernel.org \ --cc=tomi.valkeinen@ti.com \ --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: linkBe 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.