public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 1/2] RiOTboard: add new board
Date: Mon, 31 Mar 2014 22:02:34 +0200	[thread overview]
Message-ID: <20140331220234.0b2ec49e@e6520eb> (raw)
In-Reply-To: <53384461.40904@denx.de>

Hi Stefano,

Le Sun, 30 Mar 2014 18:20:49 +0200,
Stefano Babic <sbabic@denx.de> a ?crit :
> A general remark. I agree by reading the whole thread about checking at
> runtime which is the running board (you do it getting the cpu type).
> 
> However, you use also a compiler switch mechanism, adding RIOTBOARD or
> MARSBOARD in the boards.cfg. You have implemented two ways to for the
> same thing. This makes in principle your runtime detection useless,
> because you can use #if CONFIG_MARSBOARD instead of "if board_type ==
> BOARD_IS_MARSBOARD)". Is it possible to use only the runtime detection ?
> I think the main problem is CONFIG_ENV_IS_*, that is different for the
> two boards. What do you think about it ?
> 
I've tried and I don't see how to include functions to handle both MMC
and SF environment in the same binary with the current env code.

A workaround would be to use MMC to store env also on the MarSBoard but
as it is using the SPI flash as the boot source I would prefer to keep
the env in the SPI flash.

Best regards,
Eric

  parent reply	other threads:[~2014-03-31 20:02 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26 18:26 [U-Boot] [PATCH 1/2] RiOTboard: add new board Eric Bénard
2014-03-26 18:26 ` [U-Boot] [PATCH 2/2] MarSBoard: " Eric Bénard
2014-03-26 19:02   ` Wolfgang Denk
2014-03-26 19:26     ` Eric Bénard
2014-03-26 21:31     ` [U-Boot] [PATCH v2 1/2] RiOTboard: " Eric Bénard
2014-03-26 21:31       ` [U-Boot] [PATCH v2 2/2] MarSBoard: " Eric Bénard
2014-03-27  2:21         ` Otavio Salvador
2014-03-27  5:01           ` Fabio Estevam
2014-03-27  5:36             ` Wolfgang Denk
2014-03-27 12:44               ` Fabio Estevam
2014-03-27 12:50                 ` Otavio Salvador
2014-03-27 16:04                   ` Eric Bénard
2014-03-27 15:59                 ` Eric Bénard
2014-03-27 16:34                   ` Fabio Estevam
2014-03-27 16:42                 ` Wolfgang Denk
2014-03-27  5:31           ` Wolfgang Denk
2014-03-27  7:05         ` Stefan Roese
2014-03-27  7:40           ` Eric Bénard
2014-03-27 17:10           ` [U-Boot] [PATCH v3 1/2] RiOTboard: " Eric Bénard
2014-03-27 17:10             ` [U-Boot] [PATCH v3 2/2] MarSBoard: " Eric Bénard
2014-03-28  7:30               ` Stefan Roese
2014-03-28 10:09               ` Wolfgang Denk
2014-03-28 10:01             ` [U-Boot] [PATCH v3 1/2] RiOTboard: " Wolfgang Denk
2014-03-29 21:29               ` [U-Boot] [PATCH v4 " Eric Bénard
2014-03-29 21:29                 ` [U-Boot] [PATCH v4 2/2] MarSBoard: " Eric Bénard
2014-03-30 16:20                 ` [U-Boot] [PATCH v4 1/2] RiOTboard: " Stefano Babic
2014-03-30 19:52                   ` Eric Bénard
2014-03-31  6:55                     ` Stefano Babic
2014-03-31 20:02                   ` Eric Bénard [this message]
2014-04-01  8:41                     ` Stefano Babic
2014-04-01  8:50                       ` Eric Bénard

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=20140331220234.0b2ec49e@e6520eb \
    --to=eric@eukrea.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox