From: Daniel Gorsulowski <Daniel.Gorsulowski@esd.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] at91: Add esd gmbh MEESC board support
Date: Mon, 29 Jun 2009 12:59:54 +0200 [thread overview]
Message-ID: <4A489EAA.5090307@esd.eu> (raw)
In-Reply-To: <4A486152.50008@esd.eu>
Daniel Gorsulowski wrote:
> Jean-Christophe PLAGNIOL-VILLARD wrote:
>> <snip>
>>> +
>>> +int checkboard(void)
>>> +{
>>> + char str[32];
>>> + char buf[32];
>>> +
>>> + puts("Board: esd CAN-EtherCAT Gateway");
>>> + if (getenv_r("serial#", str, sizeof(str)) > 0) {
>>> + puts(", serial# ");
>>> + puts(str);
>>> + }
>>> + printf("\nHardware-revision: 1.%d\n", get_hw_rev());
>>> + printf("Crystal frequency:\t%8s MHz\n",
>>> + strmhz(buf, get_main_clk_rate()));
>>> + printf("CPU clock:\t\t%8s MHz\n",
>>> + strmhz(buf, get_cpu_clk_rate()));
>>> +#ifdef CONFIG_SHOW_VERBOSE_CLOCKINFO
>>> + printf("Master clock:\t\t%8s MHz\n",
>>> + strmhz(buf, get_mck_clk_rate()));
>>> + printf("PLL A clock:\t\t%8s MHz\n",
>>> + strmhz(buf, get_plla_clk_rate()));
>>> + printf("PLL B Reg.:\t\t0x%08X\n",
>>> + at91_sys_read(AT91_CKGR_PLLBR));
>>> + printf("PLL B clock:\t\t%8s MHz\n",
>>> + strmhz(buf, get_pllb_clk_rate()));
>>> +#endif
>>> + printf("Mach-type: %lu\n", gd->bd->bi_arch_number);
>>> + return 0;
>>> +}
>> please use cpu_info when it's possible to avoid copy & paste
>>
> Coud you explain a few more? I can't find a function called 'cpu_info'.
Found config option CONFIG_DISPLAY_CPUINFO and enabled it, thank you for
the hint.
Best regards,
Daniel Gorsulowski
next prev parent reply other threads:[~2009-06-29 10:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 10:21 [U-Boot] [PATCH] at91: Add esd gmbh MEESC board support Daniel Gorsulowski
2009-06-27 22:16 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-29 6:38 ` Daniel Gorsulowski
2009-06-29 10:59 ` Daniel Gorsulowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-29 11:24 Daniel Gorsulowski
2009-06-29 20:01 ` Jean-Christophe PLAGNIOL-VILLARD
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=4A489EAA.5090307@esd.eu \
--to=daniel.gorsulowski@esd.eu \
--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