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] [RFC] Adding support for NI Ettus Research USRP E3XX series
Date: Thu, 3 Sep 2015 21:44:19 +0200	[thread overview]
Message-ID: <201509032144.19673.marex@denx.de> (raw)
In-Reply-To: <1441305841-27703-1-git-send-email-moritz.fischer@ettus.com>

On Thursday, September 03, 2015 at 08:44:00 PM, Moritz Fischer wrote:
> Hi all,

Hi!

> this patch adds basic support for NI Ettus Research E3XX series
> boards. I tagged this RFC because I'm not sure if the boards/xilinx/zynq
> subdirectory is the correct place for this, as I'll have some follow up
> patches that read the devices EEPROM for ethernet address etc.

It's not, it should be board/ettus/e3xx/ .

> Would putting it under boards/ni/zynq be the correct way of integrating it?
> While technically a Zynq device there are a lot of custom modifications,
> that I wouldn't like to force into board/xilinx/zynq/board.c in my follow
> up patches. However duplicating the entire board.c doesn't seem like a
> good idea neither.
> 
> Any suggestions? For future reference do you want me to split out dts etc
> in a separate patch?

It's always boards/VENDOR/BOARD/ .

Best regards,
Marek Vasut

  parent reply	other threads:[~2015-09-03 19:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-03 18:44 [U-Boot] [RFC] Adding support for NI Ettus Research USRP E3XX series Moritz Fischer
2015-09-03 18:44 ` [U-Boot] [RFC] zynq: Add support for E3xx board Moritz Fischer
2015-09-03 22:15   ` Peter Crosthwaite
2015-09-03 23:18   ` Sören Brinkmann
2015-09-03 19:44 ` Marek Vasut [this message]
2015-09-03 20:05   ` [U-Boot] [RFC] Adding support for NI Ettus Research USRP E3XX series Marek Vasut

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=201509032144.19673.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