mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: bernhard@bwalle.de
To: ptxdist@pengutronix.de
Cc: Bernhard Walle <walle@corscience.de>
Subject: [ptxdist] [PATCH] mtd-utils.in: Add busybox dependencies
Date: Tue, 13 Mar 2012 12:17:38 +0100	[thread overview]
Message-ID: <1331637458-8293-1-git-send-email-bernhard@bwalle.de> (raw)

From: Bernhard Walle <walle@corscience.de>

Some tools that mtd-utils provide can be also provided by busybox. Add
the dependencies here as done in other configuration files to prevent
the user from misconfiguration.

Signed-off-by: Bernhard Walle <walle@corscience.de>
---
 rules/mtd-utils.in |   32 ++++++++++++++++++++++++++++++++
 1 file changed, 32 insertions(+)

diff --git a/rules/mtd-utils.in b/rules/mtd-utils.in
index a9bab13..800202b 100644
--- a/rules/mtd-utils.in
+++ b/rules/mtd-utils.in
@@ -43,9 +43,13 @@ config MTD_UTILS_FLASH_ERASEALL
 	bool
 	prompt "flash_eraseall (deprecated)"
 	select MTD_UTILS_FLASH_ERASE
+	depends on !BUSYBOX_FLASH_ERASEALL || ALLYES
 	help
 	  ...use flash_erase instead
 
+comment "flash_eraseall is disabled by busybox flash_eraseall"
+	depends on BUSYBOX_FLASH_ERASEALL
+
 config MTD_UTILS_FLASH_INFO
 	bool
 	prompt "flash_info"
@@ -55,9 +59,13 @@ config MTD_UTILS_FLASH_INFO
 config MTD_UTILS_FLASH_LOCK
 	bool
 	prompt "flash_lock"
+	depends on !BUSYBOX_FLASH_LOCK || ALLYES
 	help
 	  This utility locks one or more sectors of flash device.
 
+comment "flash_lock is disabled by busybox flash_lock"
+	depends on BUSYBOX_FLASH_LOCK
+
 config MTD_UTILS_FLASH_OTP_DUMP
 	bool
 	prompt "flash_otp_dump"
@@ -73,15 +81,23 @@ config MTD_UTILS_FLASH_OTP_INFO
 config MTD_UTILS_FLASH_UNLOCK
 	bool
 	prompt "flash_unlock"
+	depends on !BUSYBOX_FLASH_UNLOCK || ALLYES
 	help
 	  This utility unlock all sectors of flash device.
 
+comment "flash_unlock is disabled by busybox flash_unlock"
+	depends on BUSYBOX_FLASH_UNLOCK
+
 config MTD_UTILS_FLASHCP
 	bool
 	prompt "flashcp"
+	depends on !BUSYBOX_FLASHCP || ALLYES
 	help
 	  Flash Copy - Written by Abraham van der Merwe
 
+comment "flashcp is disabled by busybox flashcp"
+	depends on BUSYBOX_FLASHCP
+
 config MTD_UTILS_FTL_CHECK
 	bool
 	prompt "ftl_check"
@@ -126,10 +142,14 @@ config MTD_UTILS_MTDDEBUG
 config MTD_UTILS_NANDDUMP
 	bool
 	prompt "nanddump"
+	depends on !BUSYBOX_NANDDUMP || ALLYES
 	help
 	  This utility dumps the contents of raw NAND chips or NAND
 	  chips contained in DoC devices.
 
+comment "nanddump is disabled by busybox nanddump"
+	depends on BUSYBOX_NANDDUMP
+
 config MTD_UTILS_NANDTEST
 	bool
 	prompt "nandtest"
@@ -139,11 +159,15 @@ config MTD_UTILS_NANDTEST
 config MTD_UTILS_NANDWRITE
 	bool
 	prompt "nandwrite"
+	depends on !BUSYBOX_NANDWRITE || ALLYES
 	help
 	  This utility writes a binary image directly to a NAND flash
 	  chip or NAND chips contained in DoC devices. This is the
 	  "inverse operation" of nanddump.
 
+comment "nandwrite is disabled by busybox nandwrite"
+	depends on BUSYBOX_NANDWRITE
+
 config MTD_UTILS_NFTL_FORMAT
 	bool
 	prompt "nftl_format"
@@ -206,9 +230,13 @@ if MTD_UTILS_UBI_UTILS
 config MTD_UTILS_UBIATTACH
 	bool
 	prompt "ubiattach"
+	depends on !BUSYBOX_UBIATTACH || ALLYES
 	help
 	  Attach an ubi device to a mtd device
 
+comment "ubiattach is disabled by busybox ubiattach"
+	depends on BUSYBOX_UBIATTACH
+
 config MTD_UTILS_UBICRC32
 	bool
 	prompt "ubicrc32"
@@ -218,9 +246,13 @@ config MTD_UTILS_UBICRC32
 config MTD_UTILS_UBIDETACH
 	bool
 	prompt "ubidetach"
+	depends on !BUSYBOX_UBIDETACH || ALLYES
 	help
 	  Detach an ubi device from a mtd device
 
+comment "ubidetach is disabled by busybox nandwrite"
+	depends on BUSYBOX_UBIDETACH
+
 config MTD_UTILS_UBIFORMAT
 	bool
 	select GCCLIBS_GCC_S
-- 
1.7.9.4


-- 
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2012-03-13 11:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 11:17 bernhard [this message]
2012-03-13 13:35 ` Michael Olbrich
  -- strict thread matches above, loose matches on Subject: below --
2012-02-29 18:11 bernhard
2012-03-08 10:58 ` Michael Olbrich

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=1331637458-8293-1-git-send-email-bernhard@bwalle.de \
    --to=bernhard@bwalle.de \
    --cc=ptxdist@pengutronix.de \
    --cc=walle@corscience.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox