From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/6] cmd_nvedit.c: allow board-specific code before/after saving the environment
Date: Tue, 15 May 2012 01:14:14 -0400 [thread overview]
Message-ID: <201205150114.15581.vapier@gentoo.org> (raw)
In-Reply-To: <4FB12E88.1050906@freescale.com>
On Monday 14 May 2012 12:10:48 Timur Tabi wrote:
> Mike Frysinger wrote:
> > this is less bloat:
> > int board_start_saveenv(void) __attribute__((weak, alias("saveenv")));
> >
> > int do_env_save(cmd_tbl_t *cmdtp, int flag, int argc, char * const
> > argv[]) {
> >
> > printf("Saving Environment to %s...\n", env_name_spec);
> > return board_saveenv() ? 1 : 0;
> >
> > }
>
> Ah, I see. This forces the board-specific function to call saveenv().
> That gives us more flexibility in the board code.
>
> However, I was trying to mimic what we have in the NAND layer, with
> nand_get_device() and nand_release_device(). That is, before we save the
> environment, we have to "get" it, and then after we save it, we can
> "release" it.
i don't think the nand approach is terribly applicable. different solutions
for different cases.
> Your approach, although it eliminates two weak functions, is not as
> "architecturally clean" as mine, IMHO.
i'd prefer my approach because it keeps down the bloat for the vast majority
of people out there while not restricting boards who want this override
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120515/8e4e7844/attachment.pgp>
next prev parent reply other threads:[~2012-05-15 5:14 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 22:21 [U-Boot] [PATCH 1/6] powerpc/85xx: minor clean-ups to the P2020DS board header file Timur Tabi
2012-05-04 22:21 ` [U-Boot] [PATCH 2/6] powerpc/85xx: fdt_set_phy_handle() should return an error code Timur Tabi
2012-05-04 22:21 ` [U-Boot] [PATCH 3/6] powerpc/85xx: clean up P1022DS board configuration header file Timur Tabi
2012-05-04 22:21 ` [U-Boot] [PATCH 4/6] lib/powerpc: addrmap_phys_to_virt() should return a pointer Timur Tabi
2012-05-04 22:21 ` [U-Boot] [PATCH 5/6] cmd_nvedit.c: allow board-specific code before/after saving the environment Timur Tabi
2012-05-14 5:20 ` Mike Frysinger
2012-05-14 16:10 ` Timur Tabi
2012-05-15 5:14 ` Mike Frysinger [this message]
2012-05-17 22:18 ` Wolfgang Denk
2012-05-17 22:35 ` Timur Tabi
2012-05-18 2:46 ` Mike Frysinger
2012-05-18 11:28 ` Wolfgang Denk
2012-05-18 15:58 ` Timur Tabi
2012-05-18 16:02 ` Jeroen Hofstee
2012-05-18 18:24 ` Wolfgang Denk
2012-05-18 18:23 ` Wolfgang Denk
2012-05-18 18:29 ` Fabio Estevam
2012-05-17 22:48 ` Scott Wood
2012-05-17 22:53 ` Timur Tabi
2012-05-18 2:14 ` Scott Wood
2012-05-18 2:21 ` Tabi Timur-B04825
2012-05-18 2:30 ` Scott Wood
2012-05-18 16:00 ` Timur Tabi
2012-05-18 16:13 ` Scott Wood
2012-05-18 16:17 ` Timur Tabi
2012-05-18 16:29 ` Scott Wood
2012-05-18 17:08 ` Timur Tabi
2012-05-18 17:21 ` Scott Wood
2012-05-18 18:13 ` McClintock Matthew-B29882
2012-05-18 18:28 ` Wolfgang Denk
2012-05-17 21:18 ` Timur Tabi
2012-05-04 22:21 ` [U-Boot] [PATCH 6/6] powerpc/85xx: p1022ds: use the saveenv board preparation functions Timur Tabi
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=201205150114.15581.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox