public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Scott McNutt <smcnutt@psyent.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] nios2: remove EP1C20, EP1S10, EP1S40 boards
Date: Thu, 22 Apr 2010 08:36:47 -0400	[thread overview]
Message-ID: <4BD042DF.2010203@psyent.com> (raw)
In-Reply-To: <1271842363-31298-1-git-send-email-thomas@wytron.com.tw>

Hi Thomas,

Thomas Chou wrote:
> The example configuration files of nios2-generic board can generated
> binary to run on the EP1C20, EP1S10, and EP1S40 boards. So the three
> boards can be removed.
> 
> With nios2-generic approach, the fpga parameter header file can
> be generated from hardware designs using tools. Porting u-boot for

What tools are you referring to?

> nios2 boards is simplified. Vendors can supply their fpga parameter
> file or patches to add a new nios2-generic board instance. There is

Support for several Altera nios2 boards has been available in u-boot
for at least four years. To date, this vendor has offered no support
whatsoever, either through patches, files, consultation or otherwise.

Is there any reason you believe this is likely to change?

> no need to include other boards support for nios2 in the u-boot
> mainline.

I'm not convinced that this is true.

Regards,
--Scott

  reply	other threads:[~2010-04-22 12:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21  9:32 [U-Boot] [PATCH] nios2: remove EP1C20, EP1S10, EP1S40 boards Thomas Chou
2010-04-22 12:36 ` Scott McNutt [this message]
2010-04-23  3:41   ` Thomas Chou
2010-04-23  4:21     ` Scott McNutt
2010-04-23  4:30       ` Thomas Chou
2010-05-28  5:59       ` Thomas Chou

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=4BD042DF.2010203@psyent.com \
    --to=smcnutt@psyent.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