From: Westergreen, Dalon <dalon.westergreen@intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/7] arm: socfpga: update arria5 socdk default environment
Date: Sun, 22 Jan 2017 06:29:54 +0000 [thread overview]
Message-ID: <1485066592.20684.36.camel@intel.com> (raw)
In-Reply-To: <9c76207a-5d8f-c908-0d29-4b61e7a29a59@denx.de>
On Sun, 2017-01-22 at 01:36 +0100, Marek Vasut wrote:
> On 01/22/2017 12:04 AM, Westergreen, Dalon wrote:
> >
> > On Sat, 2017-01-21 at 20:29 +0100, Marek Vasut wrote:
> > >
> > > On 01/21/2017 06:31 PM, Dalon Westergreen wrote:
> > > >
> > > >
> > > > From: Dalon Westergreen <dalon.westergreen@intel.com>
> > > >
> > > > The default values for CONFIG_SYS_MMCSD_FS_BOOT_PARTITION
> > > > and CONFIG_SYS_MMCSD_FS_OS_PARTITION have changed and as
> > > > as result the default uboot environment for this board
> > > > needs updating.??This sets the default envirnment to
> > > > use the CONFIG_SYS_MMCSD_FS_BOOT_PARTITION and
> > > > CONFIG_SYS_MMCSD_FS_OS_PARTITION configs for the boot
> > > > and os partitions.
> > > >
> > > > Also set the default fdtimage value to match the
> > > > devicetree name in the linux kernel for this board.
> > > >
> > > > Signed-off-by: Dalon Westergreen <dalon.westergreen@intel.com>
> > >
> > > Acked-by: Marek Vasut <marex@denx.de>
> > >
> > > but please see my comment on 1/7
> > >
> > > btw I think this is repeating too much, why don't we pull the env into
> > > socfpga_common.h first ?
> >
> > I'd prefer to keep the boards separate and look at
> > moving to disto boot.
>
> If you create common env in socfpga_common.h first and then update it,
> the update will be in a single patch changing a single file. So will
> then be the switch to distro bootcmd. I would prefer such course of
> action over many patches doing the same thing in many files.
>
> Given how similar (and broken) the envs are for those boards, pulling
> the common env should be easy and very beneficial.
>
Okay, agreed. ?I will move all of the common env variables to?
socfpga_common.h. ?I will change the new board patch to do the same.
--
Thanks,
Dalon
next prev parent reply other threads:[~2017-01-22 6:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-21 17:31 [U-Boot] [PATCH 1/7] arm: socfpga: update de0 nano default environment Dalon Westergreen
2017-01-21 17:31 ` [U-Boot] [PATCH 2/7] arm: socfpga: update cyclone5 socdk " Dalon Westergreen
2017-01-21 19:29 ` Marek Vasut
2017-01-21 17:31 ` [U-Boot] [PATCH 3/7] arm: socfpga: update arria5 " Dalon Westergreen
2017-01-21 19:29 ` Marek Vasut
2017-01-21 23:04 ` Westergreen, Dalon
2017-01-22 0:36 ` Marek Vasut
2017-01-22 6:29 ` Westergreen, Dalon [this message]
2017-01-22 14:47 ` Marek Vasut
2017-01-21 17:31 ` [U-Boot] [PATCH 4/7] arm: socfpga: Update DE1 environment Dalon Westergreen
2017-01-21 17:31 ` [U-Boot] [PATCH 5/7] arm: socfpga: Update SoCKit environment Dalon Westergreen
2017-01-21 17:31 ` [U-Boot] [PATCH 6/7] arm: socfpga: Update sr1500 environment Dalon Westergreen
2017-01-21 19:30 ` Marek Vasut
2017-01-21 17:31 ` [U-Boot] [PATCH 7/7] arm: socfpga: add support for Terasic DE10-Nano board Dalon Westergreen
2017-01-21 19:33 ` Marek Vasut
2017-01-21 19:28 ` [U-Boot] [PATCH 1/7] arm: socfpga: update de0 nano default environment Marek Vasut
2017-01-21 21:55 ` Westergreen, Dalon
2017-01-21 22:03 ` Marek Vasut
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=1485066592.20684.36.camel@intel.com \
--to=dalon.westergreen@intel.com \
--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.