what is the purpose of config option HAS_OMAP_NAND?

Robert P. J. Day rpjday at crashcourse.ca
Tue Feb 7 06:00:02 EST 2012


On Tue, 7 Feb 2012, Sascha Hauer wrote:

> 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.

  do you want me to submit a patch?  or are you already handling it?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================



More information about the barebox mailing list