From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] u-boot compiling
Date: Mon, 08 Oct 2012 19:55:28 +0300 [thread overview]
Message-ID: <50730580.9020508@petroprogram.com> (raw)
In-Reply-To: <1349713787.63802.YahooMailNeo@web164603.mail.gq1.yahoo.com>
I know nothing about u-boot because I use grub for booting my x86 machines
and this is just a wild guess but maybe you could try standard "quiet"
kernel parameter
to place somewhere during boot process.
That's is, if u-boot allows passing kernel paremeters like grub does ?
http://www.mjmwired.net/kernel/Documentation/kernel-parameters.txt
quiet [KNL] Disable most log messages
Best regards
Stefan
8.10.2012 19:29, Zoran Djordjevic kirjoitti:
> I want to achieve booting linux on my ARM board without messages
> displaying on console. AFAIK, I must have u-boot version compiled
> with that possiblity (CONFIG_SILENT_CONSOLE). My u-boot binary
> version (on my board CD) seems not to be of that kind, because when I
> set "silent" environment variable, nothing happens.
> So, I am interested if I can compile u-boot alone, by
> using Buildroot ie. without building kernel and root file system ?
> Also, what amount of boot time shortage can I expect when supressing
> console messages ?
>
> Regards
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121008/8b736dc1/attachment.html>
next prev parent reply other threads:[~2012-10-08 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 16:29 [Buildroot] u-boot compiling Zoran Djordjevic
2012-10-08 16:55 ` Stefan Fröberg [this message]
2012-10-09 20:45 ` Arnout Vandecappelle
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=50730580.9020508@petroprogram.com \
--to=stefan.froberg@petroprogram.com \
--cc=buildroot@busybox.net \
/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