Tomi, could you please kindly ask Stephen (CCed) to include the DSS2 tree into linux-next, because you are going to merge it the next merge window, and there does not seem to be any blocker for this. Being in linux-next for a while is really important. On Mon, 2009-11-09 at 13:45 +0200, Tomi Valkeinen wrote: > This patch set implement new display subsystem driver (DSS2) and omapfb driver > for OMAP2/3. The patches have been reviewed on linux-omap and linux-fbdev-devel > mailing lists. The patches can also be found from master branch in > http://gitorious.org/linux-omap-dss2/linux. The branch is based on the > linux-next tree. > > The patches include DSS documentation patch that includes more instructions for > module parameters, sysfs files etc. > > The patches enable DSS2 for OMAP3430 SDP board and support for other boards can > be sent after the DSS2 has been merged. DSS2 is used in various boards, for > example Nokia N900, Beagle Board and Overo. > > I don't currently have any OMAP2 board to test DSS2, but it has worked on OMAP2 > and the possible fixes needed should be minimal. > > OMAP1 is not supported, and so the old DSS needs to be used on OMAP1 boards. My > longer term plan is to move all OMAP2 stuff from the old DSS to the new one, > and then shrink the old DSS to support OMAP1 only. > > DSS2 is partly based on the old omapfb driver by Imre Deak, and Imre has also > contributed to DSS2 quite a bit. Ville Syrjälä has been contributing to scaling > and tv-out work, and Topi Pohjolainen to VRFB. Also some contributions have > been made by Hardik Shah, Vaibhav Hiremath, and perhaps some others that I have > forgotten =). Tomi, could you please kindly ask Stephen (CCed) to include the DSS2 tree into linux-next, because you are going to merge it the next merge window, and there does not seem to be any blocker for this. Being in linux-next for a while is really important. -- Best Regards, Artem Bityutskiy (Артём Битюцкий) -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
