Re: [PATCH 1/3] ARM: Add "verbose" parameter for start_linux procedure
Alexander Shiyan
shc_work at mail.ru
Thu Jul 11 03:38:46 EDT 2013
> 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))
---
More information about the barebox
mailing list