public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lucas Stach <dev@lynxeye.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] tegra: add Colibri T20 board support
Date: Mon, 08 Oct 2012 18:38:17 +0200	[thread overview]
Message-ID: <1349714297.8837.6.camel@tellur> (raw)
In-Reply-To: <5072FF12.9070701@wwwdotorg.org>

Am Montag, den 08.10.2012, 10:28 -0600 schrieb Stephen Warren:
> On 10/07/2012 03:36 PM, Lucas Stach wrote:
> > This adds board support for the Toradex Colibri T20 module.
> > 
> > Working functions:
> > - SD card boot
> > - USB boot
> > - Network
> > - NAND environment
> > 
> > Signed-off-by: Lucas Stach <dev@lynxeye.de>
> > ---
> > v2:
> > - rename .dts file to match board name
> > v3:
> > - make comments more meaningful
> > - split into module and carrier board specific part to ease porting
> >   to other carrier boards
> 
> > diff --git a/board/toradex/dts/tegra20-colibri_t20_iris.dts b/board/toradex/dts/tegra20-colibri_t20_iris.dts
> 
> I suppose we can do this later, but since this patch has the C files
> split into separate board and carrier code, I'd also expect the .dts
> files to be split up in the same way.
> 
I initially tried exactly that, but since the .dts files are compiled a
bit different in u-boot than in the linux kernel it's not as easy as
doing a simple include. I'm planning to split them up later on, but I
first have to familiarize myself with the build process for dts in
u-boot.

For now I would wish to get this included as is, to get Colibri T20 some
public visibility as a working Tegra platform, so others could take this
board into account when making changes to the Tegra 20 common platform.

Thanks,
Lucas

  reply	other threads:[~2012-10-08 16:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-07 21:36 [U-Boot] [PATCH v3] tegra: add Colibri T20 board support Lucas Stach
2012-10-08 16:28 ` Stephen Warren
2012-10-08 16:38   ` Lucas Stach [this message]
2012-10-08 16:42     ` Stephen Warren

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=1349714297.8837.6.camel@tellur \
    --to=dev@lynxeye.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