From: Alexander Shiyan <shc_work@mail.ru>
To: barebox@lists.infradead.org
Subject: [PATCH] ARM: imx51: Remove stale comment
Date: Sat, 21 May 2016 09:35:24 +0300 [thread overview]
Message-ID: <1463812524-24463-1-git-send-email-shc_work@mail.ru> (raw)
Signed-off-by: Alexander Shiyan <shc_work@mail.ru>
---
arch/arm/mach-imx/imx51.c | 19 -------------------
1 file changed, 19 deletions(-)
diff --git a/arch/arm/mach-imx/imx51.c b/arch/arm/mach-imx/imx51.c
index 70e8971..a6784d0 100644
--- a/arch/arm/mach-imx/imx51.c
+++ b/arch/arm/mach-imx/imx51.c
@@ -83,25 +83,6 @@ int imx51_devices_init(void)
return 0;
}
-/*
- * Saves the boot source media into the $bootsource environment variable
- *
- * This information is useful for barebox init scripts as we can then easily
- * use a kernel image stored on the same media that we launch barebox with
- * (for example).
- *
- * imx25 and imx35 can boot into barebox from several media such as
- * nand, nor, mmc/sd cards, serial roms. "mmc" is used to represent several
- * sources as its impossible to distinguish between them.
- *
- * Some sources such as serial roms can themselves have 3 different boot
- * possibilities (i2c1, i2c2 etc). It is assumed that any board will
- * only be using one of these at any one time.
- *
- * Note also that I suspect that the boot source pins are only sampled at
- * power up.
- */
-
#define DP_MFN_800_DIT 60 /* PL Dither mode */
/*
--
2.4.9
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2016-05-21 6:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-21 6:35 Alexander Shiyan [this message]
2016-05-23 7:49 ` Sascha Hauer
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=1463812524-24463-1-git-send-email-shc_work@mail.ru \
--to=shc_work@mail.ru \
--cc=barebox@lists.infradead.org \
/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