On Mon, Feb 06, 2012 at 04:14:45PM -0500, Robert P. J. Day wrote: > > based on the output from grep: > > $ grep -r HAS_OMAP_NAND * > arch/arm/mach-omap/Kconfig: select HAS_OMAP_NAND > arch/arm/mach-omap/Kconfig: select HAS_OMAP_NAND > arch/arm/mach-omap/Kconfig: select HAS_OMAP_NAND > arch/arm/mach-omap/Kconfig: select HAS_OMAP_NAND > arch/arm/mach-omap/Kconfig:config HAS_OMAP_NAND > arch/arm/configs/phycard_a_l1_defconfig:CONFIG_HAS_OMAP_NAND=y > $ > > i'm not sure of the purpose of that Kconfig option. if nothing in the > source tree tests it, what value does it have? the definition of that > option is simply: > > config HAS_OMAP_NAND > bool > > am i missing something subtle? I can only guess that the nand driver depended on this. We can remove this. Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
