From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH] nand_spl: display warning message to inform the end of nand_spl
Date: Wed, 26 Feb 2014 15:20:27 +0100 [thread overview]
Message-ID: <530DF82B.20606@denx.de> (raw)
In-Reply-To: <1393404671-6385-1-git-send-email-yamada.m@jp.panasonic.com>
On 26.02.2014 09:51, Masahiro Yamada wrote:
> Now we have two different frameworks for doing the same thing.
> I'd like to propose to drop nand_spl framework.
> How about deleting it before v2014.07 release?
>
> In the interim, this commit will display a warning message
> when compiling nand_spl board.
>
> Now we have 19 nand_spl boards:
>
> MPC8315ERDB_NAND
> SIMPC8313_LP
> SIMPC8313_SP
> MPC8536DS_NAND
> MPC8569MDS_NAND
> MPC8572DS_NAND
> P1023RDS_NAND
> P1011RDB_NAND
> P1020RDB_NAND
> P2010RDB_NAND
> P2020RDB_NAND
> acadia_nand
> bamboo_nand
> canyonlands_nand
> glacier_nand
> haleakala_nand
> kilauea_nand
> rainier_nand
> sequoia_nand
>
> They must be ported to SPL before the deadline,
> otherwise they will be removed.
>
> Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
> Cc: Dave Liu <daveliu@freescale.com>
> Cc: Ron Madrid <info@sheldoninst.com>
> Cc: Roy Zang <tie-fei.zang@freescale.com>
> Cc: Stefan Roese <sr@denx.de>
The AMCC/APM PPC4xx NAND booting boards, which were used to introduce
the nand_spl infrastructure, are practically unmaintained. There doesn't
seem to be much interest in porting those boards to the SPL
infrastructure. So I'm fine with the date as well:
Acked-by: Stefan Roese <sr@denx.de>
Thanks,
Stefan
next prev parent reply other threads:[~2014-02-26 14:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 8:51 [U-Boot] [RFC PATCH] nand_spl: display warning message to inform the end of nand_spl Masahiro Yamada
2014-02-26 13:37 ` Tom Rini
2014-02-26 14:20 ` Stefan Roese [this message]
2014-02-26 14:27 ` Tom Rini
2014-03-04 19:16 ` [U-Boot] [U-Boot, RFC] " Tom Rini
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=530DF82B.20606@denx.de \
--to=sr@denx.de \
--cc=u-boot@lists.denx.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 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.