From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: what is the purpose of config option HAS_OMAP_NAND?
Date: Tue, 7 Feb 2012 11:51:41 +0100 [thread overview]
Message-ID: <20120207105141.GC3852@pengutronix.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1202061612300.17751@oneiric>
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@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-02-07 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 21:14 what is the purpose of config option HAS_OMAP_NAND? Robert P. J. Day
2012-02-07 10:51 ` Sascha Hauer [this message]
2012-02-07 11:00 ` Robert P. J. Day
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120207105141.GC3852@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=rpjday@crashcourse.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.