T Tomi Valkeinen #
Message details and related content
Hello Paul, Here are some OMAP display changes for .38. I hope they are not too late, but the holidays messed up my schedules a bit. I made two branches, as I'm not sure which is better: for-paul-38 - This one is the original non-rebased branch. This causes a trivial conflict with fbdev/master in drivers/video/omap2/vram.c (SZ_2M is the right one), and also it contains a patch (memblock: fix memblock_is_region_memory()) which is not yet in mainline, but is in Andrew Morton's tree. for-paul-38-rebased - The above branch rebased on top of v2.6.37, and the memblock commit removed. Which one you prefer? Or is there some other way I should handle this? I could merge v2.6.37 to my branch, which would remove the conflict, but that would still leave the memblock patch. I guess the patch is going in soon, but as it's not in my area, I don't feel it's right to get it in via my patch set. Alternatively I could wait until the patch is in Linus' tree, but that could make it tight to be in time for the merge window. Tomi The following changes since commit c8ddb2713c624f432fa5fe3c7ecffcdda46ea0d4: Linux 2.6.37-rc1 (2010-11-01 07:54:12 -0400) are available in the git repository at: git://gitorious.org/linux-omap-dss2/linux.git for-paul-38 Archit Taneja (5): OMAP: DSS2: Fix: Read correct bit in dispc_enable_alpha_blending() OMAP: DSS2: Clean up DISPC color mode validation checks OMAP: DSS2: Add dss_features for omap4 and overlay manager related features OMAP: DSS2: Use dss_features to handle DISPC bits removed on OMAP4 OMAP: DSS2: Fix build breaks for rfbi.c and dsi.c