From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Sascha Hauer" <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/3] ARM: Add "verbose" parameter for start_linux procedure
Date: Thu, 11 Jul 2013 11:38:46 +0400 [thread overview]
Message-ID: <1373528326.471370514@f400.i.mail.ru> (raw)
In-Reply-To: <20130711063147.GD14452@pengutronix.de>
> On Wed, Jul 10, 2013 at 07:13:15PM +0400, Alexander Shiyan wrote:
> > > On Wed, Jul 10, 2013 at 02:52:36PM +0200, Michael Olbrich wrote:
> > > > On Wed, Jul 10, 2013 at 11:00:39AM +0400, Alexander Shiyan wrote:
> > > > > This patch will make a normal booting more silent.
> > > >
> > > > Why? Booting the kernel is the most important task for barebox. Why
> > > > shouldn't we see a few lines about what is actually happening here by
> > > > default.
> > > >
> > > > If you really want no output then introduce a 'quiet' option.
> > >
> > > I think we really need different verbosity levels. standard would be
> > >
> > > - print commandline
> > > - print which kernel image is started
> > > - print which devicetree (if any) is used
> > >
> > > There's more I'd like to output optionally, but it's also interesting to
> > > output less in some cases.
> >
> > How many people have so many opinions.
> > What we do with patch then?
>
> For now I applied the following. This doesn't change anything in the
> verbosity but should solve your actual problem.
>
> The verbosity stuff needs a bit more thinking. Michael wants to be more
> verbose by standard, because he is the one who has to guess what's going
> wrong at our customers. I want to be more quiet optionally because less
> console output means less boot time.
>
> We could convert the meaning of the verbosity parameter could be one
> of KERN_* with the standard to KERN_INFO. Then we could implement
> everytging from quiet to chatty.
OK, thanks.
To be more detailed about problem, in my case devicetree is formed at
address 0xc0400000, and decompressed kernel placed at address 0xc0028000,
which erases devicetree.
(kernel .text : 0xc0028000 - 0xc0430cc4 (4132 kB))
---
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2013-07-11 7:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 7:00 Alexander Shiyan
2013-07-10 7:00 ` [PATCH 2/3] ARM: Use armlinux_bootparams address for DTB Alexander Shiyan
2013-07-10 7:00 ` [PATCH 3/3] mfd: syscon: Replace dev_info with dev_dbg for print used region Alexander Shiyan
2013-07-10 12:52 ` [PATCH 1/3] ARM: Add "verbose" parameter for start_linux procedure Michael Olbrich
2013-07-10 13:16 ` Sascha Hauer
2013-07-10 15:13 ` Alexander Shiyan
2013-07-11 6:31 ` Sascha Hauer
2013-07-11 7:38 ` Alexander Shiyan [this message]
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=1373528326.471370514@f400.i.mail.ru \
--to=shc_work@mail.ru \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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