Tony, Would you please check if there are no further comments and could you pull them in? 1/8: https://patchwork.kernel.org/patch/92220/ 2/8: https://patchwork.kernel.org/patch/92232/ 3/8: https://patchwork.kernel.org/patch/92221/ 4/8: https://patchwork.kernel.org/patch/92230/ 5/8: https://patchwork.kernel.org/patch/92224/ 6/8: https://patchwork.kernel.org/patch/92222/ 7/8: https://patchwork.kernel.org/patch/92223/ 8/8: https://patchwork.kernel.org/patch/92229/ Regards, Sukumar Ghorai > -----Original Message----- > From: Ghorai, Sukumar > Sent: 2010-04-13 23:07 > To: linux-omap@xxxxxxxxxxxxxxx > Cc: Ghorai, Sukumar > Subject: [PATCH] nand support on omap3 boards > > The following set of patches applies on top of the Tony's master > branch. > And these are the patches required to enable nand (nor and onenand for > sdp > only) for different platform. > > Sukumar Ghorai (3): > OMAP: ZOOM: Introducing 'board-zoom-flash.c' > omap3: add support for NAND on zoom2 board > omap3: add support for NAND on zoom3 board > omap-3630-sdp : Add support for Flash > omap-3630-sdp: enable Flash device support > omap3: add support for NAND on LDP board > zoom2: enable NAND support > zoom3: enable NAND support > > arch/arm/configs/omap_3630sdp_defconfig | 77 +++++++++++++++++- > arch/arm/configs/omap_zoom2_defconfig | 90 > ++++++++++++++++++++- > arch/arm/configs/omap_zoom3_defconfig | 90 > ++++++++++++++++++++- > arch/arm/mach-omap2/Makefile | 4 + > arch/arm/mach-omap2/board-3630sdp.c | 110 > +++++++++++++++++++++++++ > arch/arm/mach-omap2/board-ldp.c | 41 +++++++++ > arch/arm/mach-omap2/board-sdp-flash.c | 2 + > arch/arm/mach-omap2/board-zoom-flash.c | 82 ++++++++++++++++++ > arch/arm/mach-omap2/board-zoom2.c | 49 +++++++++++ > arch/arm/mach-omap2/board-zoom3.c | 48 +++++++++++ > arch/arm/mach-omap2/include/mach/board-zoom.h | 11 +++ > 11 files changed, 601 insertions(+), 3 deletions(-) create mode 100644 > arch/arm/mach-omap2/board-zoom-flash.c -- 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
