All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chin Liang See <clsee@altera.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/6] arm: socfpga: Switch CONFIG_HOSTNAME to CONFIG_SYS_BOARD
Date: Mon, 7 Dec 2015 20:08:54 +0800	[thread overview]
Message-ID: <1449490134.1803.0.camel@altera.com> (raw)
In-Reply-To: <201512071301.17733.marex@denx.de>

On Mon, 2015-12-07 at 13:01 +0100, Marek Vasut wrote:
> On Monday, December 07, 2015 at 11:01:24 AM, Chin Liang See wrote:
> > On Mon, 2015-12-07 at 09:36 +0100, Marek Vasut wrote:
> > > On Monday, December 07, 2015 at 07:25:31 AM, Chin Liang See
> > > wrote:
> > > > On Sat, 2015-12-05 at 21:44 +0100, Marek Vasut wrote:
> > > > > We already have the CONFIG_SYS_BOARD variable, which defines
> > > > > the
> > > > > name
> > > > > of the board. The value in CONFIG_HOSTNAME is exactly the
> > > > > same
> > > > > and is
> > > > > thus just a duplicity, so switch it to reuse CONFIG_SYS_BOARD
> > > > > .
> > > > > 
> > > > > Signed-off-by: Marek Vasut <marex@denx.de>
> > > > > Cc: Chin Liang See <clsee@altera.com>
> > > > > Cc: Dinh Nguyen <dinguyen@opensource.altera.com>
> > > > > ---
> > > > > 
> > > > >  include/configs/socfpga_arria5_socdk.h   | 2 --
> > > > >  include/configs/socfpga_common.h         | 4 ++++
> > > > >  include/configs/socfpga_cyclone5_socdk.h | 2 --
> > > > >  include/configs/socfpga_de0_nano_soc.h   | 2 --
> > > > >  include/configs/socfpga_mcvevk.h         | 2 --
> > > > >  include/configs/socfpga_sockit.h         | 2 --
> > > > >  include/configs/socfpga_socrates.h       | 2 --
> > > > >  include/configs/socfpga_sr1500.h         | 3 ---
> > > > >  8 files changed, 4 insertions(+), 15 deletions(-)
> > > > > 
> > > > > diff --git a/include/configs/socfpga_arria5_socdk.h
> > > > > b/include/configs/socfpga_arria5_socdk.h
> > > > > index a036856..3d5665d 100644
> > > > > --- a/include/configs/socfpga_arria5_socdk.h
> > > > > +++ b/include/configs/socfpga_arria5_socdk.h
> > > > > @@ -56,8 +56,6 @@
> > > > > 
> > > > >  #define CONFIG_ENV_OFFSET		512	/* just
> > > > > 
> > > > > after
> > > > > 
> > > > > the MBR */
> > > > > 
> > > > >  /* Extra Environment */
> > > > > 
> > > > > -#define CONFIG_HOSTNAME		socfpga_arria5
> > > > > -
> > > > > 
> > > > >  #define CONFIG_EXTRA_ENV_SETTINGS \
> > > > >  
> > > > >  	"verify=n\0" \
> > > > >  	"loadaddr= " __stringify(CONFIG_SYS_LOAD_ADDR) "\0"
> > > > > \
> > > > > 
> > > > > diff --git a/include/configs/socfpga_common.h
> > > > > b/include/configs/socfpga_common.h
> > > > > index 4b2d246..f74c758 100644
> > > > > --- a/include/configs/socfpga_common.h
> > > > > +++ b/include/configs/socfpga_common.h
> > > > > @@ -69,6 +69,10 @@
> > > > > 
> > > > >  #define CONFIG_CMDLINE_EDITING			/*
> > > > > Command
> > > > > 
> > > > > history etc */
> > > > > 
> > > > >  #define CONFIG_SYS_HUSH_PARSER
> > > > > 
> > > > > +#ifndef CONFIG_SYS_HOSTNAME
> > > > > +#define CONFIG_SYS_HOSTNAME	CONFIG_SYS_BOARD
> > > > > +#endif
> > > > > +
> > > > 
> > > > I saw the change of hostname for socdk would be
> > > > "socfpga_cyclone5"
> > > > to
> > > > "cyclone5-socdk" and same for other board. Wonder any impact on
> > > > this
> > > > change?
> > > 
> > > It should have no impact, unless you're using the hostname in
> > > your
> > > scripts
> > > for something. You would have no way to tell apart the cyclone5
> > > boards with
> > > the old hostname though, since socfpga_cyclone5 is too generic.
> > > In
> > > case this
> > > breaks some script of yours, setenv hostname socfpga_cyclone5
> > > would
> > > fix it.
> > 
> > I grep previously and its not used. But will take note if any side
> > effect noticed.
> 
> OK, thanks


Acked-by: Chin Liang See <clsee@altera.com>

Thanks
Chin Liang

  reply	other threads:[~2015-12-07 12:08 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-05 20:44 [U-Boot] [PATCH 1/6] arm: socfpga: de0_nano: Zap VIRTUAL_TARGET Marek Vasut
2015-12-05 20:44 ` [U-Boot] [PATCH 2/6] arm: socfpga: sockit: " Marek Vasut
2015-12-07  6:14   ` Chin Liang See
2015-12-05 20:44 ` [U-Boot] [PATCH 3/6] arm: socfpga: Switch CONFIG_G_DNL_MANUFACTURER to CONFIG_SYS_VENDOR Marek Vasut
2015-12-07  6:18   ` Chin Liang See
2015-12-05 20:44 ` [U-Boot] [PATCH 4/6] arm: socfpga: Switch CONFIG_HOSTNAME to CONFIG_SYS_BOARD Marek Vasut
2015-12-07  6:25   ` Chin Liang See
2015-12-07  8:36     ` Marek Vasut
2015-12-07 10:01       ` Chin Liang See
2015-12-07 12:01         ` Marek Vasut
2015-12-07 12:08           ` Chin Liang See [this message]
2015-12-05 20:44 ` [U-Boot] [PATCH 5/6] arm: socfpga: Introduce common board code Marek Vasut
2015-12-07 12:53   ` Chin Liang See
2015-12-07 13:23     ` Marek Vasut
2015-12-07 13:32       ` Chin Liang See
2015-12-07 14:23         ` Marek Vasut
2015-12-07 14:29           ` Chin Liang See
2015-12-07 14:37             ` Marek Vasut
2015-12-07 14:56               ` Chin Liang See
2015-12-07 17:46                 ` Marek Vasut
2015-12-08 12:34                   ` Chin Liang See
2015-12-08 12:57                     ` Marek Vasut
2015-12-09 13:46                       ` Chin Liang See
2015-12-05 20:44 ` [U-Boot] [PATCH 6/6] arm: socfpga: Drop the board boilerplate Marek Vasut
2015-12-07 12:56   ` Chin Liang See
2015-12-07 13:22     ` Marek Vasut
2015-12-07 13:29       ` Chin Liang See
2015-12-07  6:11 ` [U-Boot] [PATCH 1/6] arm: socfpga: de0_nano: Zap VIRTUAL_TARGET Chin Liang See

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=1449490134.1803.0.camel@altera.com \
    --to=clsee@altera.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.