public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 3/3] x86: Add Intel Edison board files
Date: Thu, 06 Jul 2017 12:44:09 +0300	[thread overview]
Message-ID: <1499334249.22624.285.camel@linux.intel.com> (raw)
In-Reply-To: <CAEUhbmXSWjaLj5wStwc70kuORsriZWNdPbhJGnVecsR5ZxooOQ@mail.gmail.com>

On Thu, 2017-07-06 at 12:07 +0800, Bin Meng wrote:
> Hi Andy,
> 
> On Thu, Jul 6, 2017 at 4:56 AM, Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > Add Intel Edison board which is using U-Boot.
> 

Thanks for review, my answers below.

> Thank you for your efforts to bring edition support upstream! Looks
> quite clean. A few comments below.

I hope to see it soon there!

> > +config SYS_USB_OTG_BASE
> > +       hex
> > +       default 0xf9100000
> 
> Can this otg controller be put into device tree, like other
> peripherals?

I will check the possibility.


> > diff --git a/board/intel/edison/edison_start.S
> > b/board/intel/edison/edison_start.S
> 
> This file should be renamed to just start.S

Done.

> > +U-boot is a main bootloader on Intel Edison board.
> 
> U-Boot

Fixed.

> Are there instructions on how to program U-Boot on a board that does
> not have pre-flashed U-Boot? or in a situation that users flashed a
> bad image that makes the board brick.

We assume that board is supplied with official image. There is official
documentation how to "unbrick" board to the stock state. So, I consider
it out of scope of U-Boot documentation.

> > +/*-----------------------------------------------------------------
> > ------
> 
> nits: /* Boot */

Fixed (all cases).

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

  reply	other threads:[~2017-07-06  9:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-05 20:56 [U-Boot] [PATCH v2 0/3] x86: Introduce Intel Tangier SoC and Edison board Andy Shevchenko
2017-07-05 20:56 ` [U-Boot] [PATCH v2 1/3] x86: Add dma-mapping.h to architectural code Andy Shevchenko
2017-07-06  4:07   ` Bin Meng
2017-07-07  3:59   ` Simon Glass
2017-07-22  5:16     ` Bin Meng
2017-07-05 20:56 ` [U-Boot] [PATCH v2 2/3] x86: Add Intel Tangier support Andy Shevchenko
2017-07-06  4:07   ` Bin Meng
2017-07-05 20:56 ` [U-Boot] [PATCH v2 3/3] x86: Add Intel Edison board files Andy Shevchenko
2017-07-06  4:07   ` Bin Meng
2017-07-06  9:44     ` Andy Shevchenko [this message]
2017-07-06 11:28       ` Andy Shevchenko
2017-07-06 11:33         ` Felipe Balbi
2017-07-06 12:08           ` Bin Meng
2017-07-06 12:07         ` Bin Meng

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=1499334249.22624.285.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox