* Pandita, Vikram <vikram.pandita@xxxxxx> [091203 10:27]: > Tony > > >-----Original Message----- > >From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Tony > >Lindgren > >Sent: Thursday, December 03, 2009 11:36 AM > >To: linux-omap@xxxxxxxxxxxxxxx > >Subject: Merge plans for 2.6.33 merge window > > > >Hi all, > <snip> > >Then there are some new board files, like > >touchbook and various fixes. > > 3630 board support (zoom3/sdp3630) is already integrated in for-next. > However the only pending patches missing for 3630 boards to boot are these serial patches: > http://patchwork.kernel.org/patch/61671/ > http://patchwork.kernel.org/patch/61672/ > > Now there has been much discussion on the approach (errata vs feature). > As a moderator, how would you like us to proceed on this? The best solution way would be to check the revision register for the serial module if available and then initialize the serial port accordinly. If this feature cannot be checked in the serial module, and is only needed during the serial init, you might as well implement the test in arch/arm/mach-omap2/serial.c. So probably no need to add that to id.c. Regards, Tony -- 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
