Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] configs: add defconfig for TS-4900
Date: Thu, 22 Sep 2016 07:21:57 +0200	[thread overview]
Message-ID: <20160922072157.547f1747@free-electrons.com> (raw)
In-Reply-To: <017033a8-afa4-5b74-3d69-99b2bcefbbb9@mind.be>

Hello,

On Wed, 21 Sep 2016 22:35:35 +0200, Arnout Vandecappelle wrote:

>  As discussed in v1 of this patch, the problem is that this is a defconfig for a
> module. Several hardware revisions of this module exist with different DDR
> chips, which require a different U-Boot config. So we'd need several buildroot
> defconfigs for the different module revisions. And it's not easy to distinguish
> between them.
> 
>  In addition, recovery through USB requires a specific baseboard that sets the
> boot mode pins in a way that you actually boot from USB. Not everybody necessary
> has this baseboard.
> 
>  For these reasons, I agreed with Mathieu that it was OK to skip the bootloader.

OK, fine with me. Thanks for the explanation!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      reply	other threads:[~2016-09-22  5:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-17 20:23 [Buildroot] [PATCH v2 0/2] configs: Add ts4900 basic board support Mathieu Audat
2016-09-17 20:23 ` [Buildroot] [PATCH v2 1/2] ts4900-fpga: add ts4900-fpga package Mathieu Audat
2016-09-18 14:58   ` Thomas Petazzoni
2016-09-17 20:23 ` [Buildroot] [PATCH v2 2/2] configs: add defconfig for TS-4900 Mathieu Audat
2016-09-18 15:10   ` Thomas Petazzoni
2016-09-21 20:35     ` Arnout Vandecappelle
2016-09-22  5:21       ` Thomas Petazzoni [this message]

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=20160922072157.547f1747@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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