From: Stephan Linz <linz@mazet.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [patch] MicroBlaze port of U-Boot
Date: Wed, 7 Apr 2004 09:09:05 +0200 [thread overview]
Message-ID: <04040708495006.16618@pcj86> (raw)
In-Reply-To: <20040406194020.B1B153E624@dns1.atmark-techno.com>
Am Dienstag, 6. April 2004 21:40 schrieb Yasushi SHOJI:
> Hello all,
>
> Here is a patch against the current CVS for microblaze port of
> u-boot. I does nothing but boot itself, but this can be a start.
>
> Suggestions, thoughts, and comments are welcome, of course.
>
> best regards,
> --
> yashi
Looks nice - two hints/annotations:
1.) You should avoid the serial_init() & main_loop() calls inside your
board_init() function. I think it's an unclean U-Boot coding style. The right
place would be in lib_microblaze/board.c functions board_init_[rf]() or
board_init() for targets without Flash/RAM abstraction (like Nios).
Why do you do so?
2.) As far as I can remember the Microblaze CPU is the Soft CPU by Xilinx
like Nios by Altera. So the core will be very very flexible and have to be
configurable. Have a look at the differen Nios targets and let you inspire to
map your specific CPU configuration into the U-Boot configuration managment.
Best regards,
Stepha Linz
next prev parent reply other threads:[~2004-04-07 7:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 19:40 [U-Boot-Users] [patch] MicroBlaze port of U-Boot Yasushi SHOJI
2004-04-07 7:09 ` Stephan Linz [this message]
2004-04-07 11:19 ` Yasushi SHOJI
2004-04-18 21:25 ` Wolfgang Denk
2004-06-26 14:27 ` Yasushi SHOJI
2004-06-28 17:28 ` Yasushi SHOJI
2004-06-28 18:08 ` Wolfgang Denk
2004-04-18 21:06 ` Wolfgang Denk
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=04040708495006.16618@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox