public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] mx28evk: extend default environment
Date: Fri, 11 May 2012 16:15:14 +0200	[thread overview]
Message-ID: <201205111615.15028.marex@denx.de> (raw)
In-Reply-To: <CAP9ODKqNBZACicBdcJfOfzMGvwcFKsUaDmVeBqnbPiydDno8bQ@mail.gmail.com>

Dear Otavio Salvador,

> On Fri, May 11, 2012 at 10:54 AM, Otavio Salvador
> 
> <otavio@ossystems.com.br> wrote:
> >> Can we possibly unify it with what's already in m28evk? Also, it'd be
> >> cool if we had some default -- very generic -- env. Can we go in that
> >> direction?
> > 
> > I have prepared a set of commits in this direction. Please take a look
> > at:
> > 
> > https://github.com/otavio/u-boot/commit/5745dfbfa1bd69b23c73dc3d2b2c2932c
> > 338e750
> > https://github.com/otavio/u-boot/commit/d8b1ea575177038f6e37f28563f00c92
> > 60016ac9
> > 
> > Is that what you expect? I want to put sdcard based update commands
> > before sending it for merging.
> 
> Fabio has pointed a example for me of 'magnesium' board config. Is it
> what you expect? it does make sense for me to make a common header
> file for both boards and others that might come later.

Something like that, but you're missing update_sd_firmware ;-)

Best regards,
Marek Vasut

  reply	other threads:[~2012-05-11 14:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10 13:27 [U-Boot] [PATCH 1/2] mx28evk: extend default environment Fabio Estevam
2012-05-10 13:27 ` [U-Boot] [PATCH 2/2] MX28: Fix a typo in mx28_reg_8 macro Fabio Estevam
2012-05-10 17:23 ` [U-Boot] [PATCH 1/2] mx28evk: extend default environment Marek Vasut
2012-05-11 13:54   ` Otavio Salvador
2012-05-11 14:10     ` Otavio Salvador
2012-05-11 14:15       ` Marek Vasut [this message]
2012-05-11 14:25       ` Stefano Babic
2012-05-11 14:31         ` Otavio Salvador

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=201205111615.15028.marex@denx.de \
    --to=marex@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox