From: Stephan Linz <linz@mazet.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] u-boot and NIOS dk 1s10 board
Date: Wed, 19 Nov 2003 08:36:17 +0100 [thread overview]
Message-ID: <03111908361707.23084@pcj86> (raw)
In-Reply-To: <20031118154940.011F9C5F5F@atlas.denx.de>
Am Dienstag, 18. November 2003 16:49 schrieb Wolfgang Denk:
> In message <03111816211506.23084@pcj86> you wrote:
> > > 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.
>
> Another option is to pass configuration options from the Makefile.
> See for example how CPU type, core frequency, availability of L2
> cache and bus mode are handled for the TQM82xx boards.
Yes, I know about because of my last few PPC projects, but I think there are
to many options for a NIOS board. We have to configure whole CPU
functionality (not only a board). I'll compare both ways.
br,
Stephan
next prev parent reply other threads:[~2003-11-19 7:36 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
2003-11-18 15:49 ` Wolfgang Denk
2003-11-19 7:36 ` Stephan Linz [this message]
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=03111908361707.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.