From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/9] openrisc: Add board info printout to cmd_bdinfo
Date: Tue, 22 Nov 2011 05:49:31 +0100 [thread overview]
Message-ID: <201111220549.31644.marek.vasut@gmail.com> (raw)
In-Reply-To: <20111122043032.GA7328@chokladfabriken.org>
> On Mon, Nov 21, 2011 at 11:53:32PM +0100, Marek Vasut wrote:
> > > +int do_bdinfo(cmd_tbl_t *cmdtp, int flag, int argc, char * const
> > > argv[]) +{
> > > + bd_t *bd = gd->bd;
> > > +
> > > + print_num("mem start", (ulong)bd->bi_memstart);
> > > + print_lnum("mem size", (u64)bd->bi_memsize);
> > > + print_num("flash start", (ulong)bd->bi_flashstart);
> > > + print_num("flash size", (ulong)bd->bi_flashsize);
> > > + print_num("flash offset", (ulong)bd->bi_flashoffset);
> > > +
> > > +#if defined(CONFIG_CMD_NET)
> > > + print_eth(0);
> > > + printf("ip_addr = %pI4\n", &bd->bi_ip_addr);
> > > +#endif
> > > +
> > > + printf("baudrate = %ld bps\n", bd->bi_baudrate);
> >
> > Would consistent format of the printed data be a problem ? ;-)
>
> I'm sorry, I don't think I understand what you are referring to here.
> When printed, they are all lined up.
> If I haven't missed something, every arch does the printing like that.
Ok, then that's good.
>
> Stefan
next prev parent reply other threads:[~2011-11-22 4:49 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 5:21 [U-Boot] [PATCH 0/9] Add support for the OpenRISC architecture Stefan Kristiansson
2011-11-19 5:21 ` [U-Boot] [PATCH 1/9] openrisc: Add architecture header files Stefan Kristiansson
2011-11-19 6:06 ` Mike Frysinger
2011-11-19 5:21 ` [U-Boot] [PATCH 2/9] openrisc: Add architecture image support Stefan Kristiansson
2011-11-21 22:45 ` Marek Vasut
2011-11-22 9:43 ` [U-Boot] [PATCH] Fix clash between IH_ARCH_NDS32 and IH_ARCH_SANDBOX Stefan Kristiansson
2011-11-22 11:03 ` [U-Boot] 回覆: " macpaul at andestech.com
2011-11-22 14:15 ` Marek Vasut
2011-11-23 6:10 ` Macpaul Lin
2011-11-19 5:21 ` [U-Boot] [PATCH 3/9] openrisc: Add cpu files Stefan Kristiansson
2011-11-19 5:59 ` Mike Frysinger
2011-11-20 4:27 ` Stefan Kristiansson
2011-11-20 5:27 ` Mike Frysinger
2011-11-21 22:50 ` Marek Vasut
2011-11-22 3:51 ` Stefan Kristiansson
2011-11-22 4:46 ` Marek Vasut
2011-11-22 7:17 ` Stefan Kristiansson
2011-11-22 14:07 ` Marek Vasut
2011-11-22 20:29 ` Scott Wood
2011-11-22 20:54 ` Mike Frysinger
2011-11-19 5:21 ` [U-Boot] [PATCH 4/9] openrisc: Add library functions Stefan Kristiansson
2011-11-19 6:04 ` Mike Frysinger
2011-11-21 22:52 ` Marek Vasut
2011-11-22 4:19 ` Stefan Kristiansson
2011-11-22 4:48 ` Marek Vasut
2011-11-22 6:00 ` Stefan Kristiansson
2011-11-22 14:10 ` Marek Vasut
2011-11-19 5:21 ` [U-Boot] [PATCH 5/9] openrisc: Add board info printout to cmd_bdinfo Stefan Kristiansson
2011-11-21 22:53 ` Marek Vasut
2011-11-22 4:30 ` Stefan Kristiansson
2011-11-22 4:49 ` Marek Vasut [this message]
2011-11-19 5:21 ` [U-Boot] [PATCH 6/9] openrisc: Add support for standalone programs Stefan Kristiansson
2011-11-19 5:21 ` [U-Boot] [PATCH 7/9] openrisc: Add openrisc-generic example board Stefan Kristiansson
2011-11-19 5:21 ` [U-Boot] [PATCH 8/9] openrisc: Add architecture to MAKEALL Stefan Kristiansson
2011-11-19 5:21 ` [U-Boot] [PATCH 9/9] openrisc: Add MAINTAINERS entry Stefan Kristiansson
2011-11-21 22:54 ` Marek Vasut
2011-11-22 4:32 ` Stefan Kristiansson
2011-11-19 6:07 ` [U-Boot] [PATCH 0/9] Add support for the OpenRISC architecture Mike Frysinger
2011-11-19 7:23 ` Stefan Kristiansson
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=201111220549.31644.marek.vasut@gmail.com \
--to=marek.vasut@gmail.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