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: Fri, 23 Apr 2010 00:21:13 -0400	[thread overview]
Message-ID: <4BD12039.3030107@psyent.com> (raw)
In-Reply-To: <4BD116EA.6080400@wytron.com.tw>

Hi Thomas,

Thomas Chou wrote:
>>> 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?

> 2. sopc-create-config-files
> 
> The script is available at
> 
>   http://sopc.et.ntust.edu.tw/?p=toolchain-build.git;
> a=blob_plain;f=tools/sopc-create-config-files;hb=HEAD

Ok ... GPL ... very nice! This addresses several of my big concerns.

> We cannot add every board, 
> and a generic approach should be taken as Michal suggested. We, (you, I 
> , the community and Altera), should work together to offer a better 
> solution.

Agreed. And please realize that I think the "generic approach" is
a great way to proceed. I listed my concerns in an earlier response
to Dalon. The availability of your GPL-ed script addresses most of
them.

> The binary generated with the nios2-generic target should work on these 
> three boards. I tested on  EP1C20 and I believe it will work on the 
> other two. These boards are still supported, just under a different name.

I tested on the 1c20 this evening as well ... works fine. I will test on
the 2c35 board tomorrow. I'd like to get a positive confirmation WRT the
1S10 and 1S40 before applying this patch.

>>> no need to include other boards support for nios2 in the u-boot
>>> mainline.
>> I'm not convinced that this is true.
>>
> Michal's work on microblaze-generic already proved this.

Michal proved the concept ... and the microblaze implementation (many
thanks for your contributions Michal). I'd like to _know_ that nothing
is broken before we remove existing code -- I don't want to leave
anyone high and dry. I've been in such situations ... it's no fun.

I'll apply the generic board patch to the nios 'next' branch, but I'd
like to hold off on blowing away those other board trees until we get
a chance to test the generic board on the actual targets. Fair enough?

Thanks for your efforts.

Regards,
--Scott

  reply	other threads:[~2010-04-23  4:21 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
2010-04-23  3:41   ` Thomas Chou
2010-04-23  4:21     ` Scott McNutt [this message]
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=4BD12039.3030107@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