All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Linz <linz@mazet.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] u-boot and NIOS dk 1s10 board
Date: Tue, 18 Nov 2003 16:21:15 +0100	[thread overview]
Message-ID: <03111816211506.23084@pcj86> (raw)
In-Reply-To: <1B1B671D73FED2119B1000A0C9B8A9600108ED04@ORBNET>

Am Dienstag, 18. November 2003 15:13 schrieb Scott McNutt:
> Hi All,
>
> I agree with all of the comments I have seen so far WRT
> Nios configuration issues. My primary motivation is to make
> sure Nios users new to u-boot, can build a __working__ version
> of u-boot by simply:
>
>     $ make DK1C20_config | DK1S10_config | etc.
>     $ make
>
> As long as this holds true, I'm happy :-)

Yes, right.

>
> > Yes, of course. We have to make different configuration
> > files -- one for each board. But, do we really need different
> > board directories with almost the same code in it?
>
> u-boot has a clever mechanism we can use to avoid code
> duplication by using the VENDOR make variable. A good
> example is in board/siemens: the SCM and CCM boards
> both share common code.

Sounds interesting. I will spend some time on it next weekend.

>
> Since this mechanism is supported ... and it is being used by
> other board families, we can do the same. It's a bit more
> work ... but I believe it will satisfy everyone :-)
>
> > Ex.: My current Stratix patch is based on the Cyclone board,
> > because both boards are equal in context of u-boot basics need.
> > Only the second serial i/f  differs (not needed til now). So there
> > will be more identicalness than differences for both boards.
>
> Understood. We can create board/altera_nios (or some other
> meaningful name) and take advantage of the VENDOR variable
> to accommodate common code. Stephen & Patrice, please let
> me know your thoughts.

Hmm, sounds good to me. More comments next week. I have to look up the VENDOR 
make mechanism and play with it. I don't know more about it.


br,
Stephan

  reply	other threads:[~2003-11-18 15:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-18 14:13 [U-Boot-Users] u-boot and NIOS dk 1s10 board Scott McNutt
2003-11-18 15:21 ` Stephan Linz [this message]
2003-11-18 15:49   ` Wolfgang Denk
2003-11-19  7:36     ` Stephan Linz
2003-11-19  9:01       ` Wolfgang Denk
2003-11-19  9:37         ` Stephan Linz
2003-11-19 10:04           ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2003-11-17 18:40 Scott McNutt
2003-11-18  8:27 ` Stephan Linz
2003-11-18  9:17   ` Patrice Kadionik
2003-11-18 10:23     ` Stephan Linz
2003-11-14 13:48 Scott McNutt
2003-11-14 13:06 Patrice Kadionik
2003-11-14 14:13 ` Stephan Linz
     [not found]   ` <3FB509B9.5050004@enseirb.fr>
     [not found]     ` <03111418170801.23084@pcj86>
2003-11-17 16:48       ` Patrice Kadionik

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=03111816211506.23084@pcj86 \
    --to=linz@mazet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.