From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH v2 13/15] bootstage: Add microsecond boot time measurement
Date: Mon, 13 Feb 2012 15:27:04 -0800 [thread overview]
Message-ID: <CAPnjgZ1OJz=WgcFZhRfc85u4MTLs_M7rURw2wpO5R89_vT5kGw@mail.gmail.com> (raw)
In-Reply-To: <CAPnjgZ28OeDLUpWw0_PcDDUOyQGsCV7RHKby9yExVu7kmrGd=A@mail.gmail.com>
Hi Mike,
On Sat, Jan 14, 2012 at 5:27 PM, Simon Glass <sjg@chromium.org> wrote:
> Hi Mike,
>
> On Sat, Jan 14, 2012 at 5:22 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> > On Saturday 14 January 2012 20:16:35 Simon Glass wrote:
> >> On Sat, Jan 14, 2012 at 5:09 PM, Mike Frysinger wrote:
> >> > On Thursday 12 January 2012 00:41:24 Simon Glass wrote:
> >> >> Still don't quite get it though. For example, the beagle board
> defines
> >> >> show_boot_progress() but does not define CONFIG_SHOW_BOOT_PROGRESS,
> so
> >> >> wouldn't that break that board?
> >> >
> >> > that sounds like an odd-man-out that needs fixing rather than
> allowing to
> >> > live
> >>
> >> Fair enough. although I suspect there will be many. If I could
> >> actually get a MAKEALL to run without producing 100s of broken boards
> >> then it would be easier to do this sort of thing. At the moment it's
> >> like looking for a needle in a haystack. My warnings series aimed to
> >> improve things slightly, but I don't think others have these problems.
> >
> > that's fair. if it's a small # of boards, i'd prefer to migrate them.
> if
> > it's a lot more, we can punt for now (add to the TODO?) and add comments
> to
> > the code why we have these checks.
>
> OK, I don't know the answer to that but will try it out, and adjust
> that patch as needed.
>
I have got back to this now - it seem that I can rely on the existing weak
function, so I will do so.
I only want to update two of the patches, so will just send those ones. The
rest should be fine as is.
Regards,
SImon
next prev parent reply other threads:[~2012-02-13 23:27 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-10 21:07 [U-Boot] [RFC PATCH v2 0/15] bootstage: record and publish boot progress timing Simon Glass
2011-12-10 21:07 ` [U-Boot] [RFC PATCH v2 01/15] bootstage: Create an initial header for boot progress integers Simon Glass
2012-01-08 8:26 ` Mike Frysinger
2012-01-08 17:22 ` Simon Glass
2012-01-08 19:46 ` Mike Frysinger
2012-01-08 23:43 ` Simon Glass
2011-12-10 21:07 ` [U-Boot] [RFC PATCH v2 02/15] bootstage: Make use of BOOTSTAGE_ID_RUN_OS in show_boot_progress() Simon Glass
2012-01-08 8:26 ` Mike Frysinger
2011-12-10 21:07 ` [U-Boot] [RFC PATCH v2 03/15] bootstage: Use show_boot_error() for -ve progress numbers Simon Glass
2012-01-08 8:27 ` Mike Frysinger
2011-12-10 21:07 ` [U-Boot] [RFC PATCH v2 04/15] bootstage: Convert progress numbers 1-9 into enums Simon Glass
2012-01-08 8:27 ` Mike Frysinger
2012-01-08 17:27 ` Simon Glass
2011-12-10 21:07 ` [U-Boot] [RFC PATCH v2 05/15] bootstage: Convert progress numbers 10-19 to enums Simon Glass
2012-01-08 8:28 ` Mike Frysinger
2012-01-08 17:29 ` Simon Glass
2011-12-10 21:07 ` [U-Boot] [RFC PATCH v2 06/15] bootstage: Convert progress numbers 20-41 " Simon Glass
2011-12-10 21:07 ` [U-Boot] [RFC PATCH v2 07/15] bootstage: Convert IDE progress numbers " Simon Glass
2011-12-10 21:08 ` [U-Boot] [RFC PATCH v2 08/15] bootstage: Convert NAND " Simon Glass
2011-12-10 21:08 ` [U-Boot] [RFC PATCH v2 09/15] bootstage: Convert net " Simon Glass
2011-12-10 21:08 ` [U-Boot] [RFC PATCH v2 10/15] bootstage: Convert FIT " Simon Glass
2011-12-10 21:08 ` [U-Boot] [RFC PATCH v2 11/15] bootstage: Define an optional microsecond timer Simon Glass
2012-01-08 8:30 ` Mike Frysinger
2012-01-08 17:33 ` Simon Glass
2012-01-08 19:57 ` Mike Frysinger
2012-01-08 23:49 ` Simon Glass
2011-12-10 21:08 ` [U-Boot] [RFC PATCH v2 12/15] bootstage: Replace show_boot_progress/error() with bootstage_...() Simon Glass
2011-12-10 21:08 ` [U-Boot] [RFC PATCH v2 13/15] bootstage: Add microsecond boot time measurement Simon Glass
2012-01-08 8:35 ` Mike Frysinger
2012-01-08 17:42 ` Simon Glass
2012-01-09 17:33 ` Mike Frysinger
2012-01-12 5:41 ` Simon Glass
2012-01-15 1:09 ` Mike Frysinger
2012-01-15 1:16 ` Simon Glass
2012-01-15 1:22 ` Mike Frysinger
2012-01-15 1:27 ` Simon Glass
2012-02-13 23:27 ` Simon Glass [this message]
2011-12-10 21:08 ` [U-Boot] [RFC PATCH v2 14/15] bootstage: Plumb in bootstage calls for basic operations Simon Glass
2011-12-10 21:08 ` [U-Boot] [RFC PATCH v2 15/15] bootstage: arm: Add bootstage calls in board and bootm Simon Glass
2012-01-08 8:36 ` Mike Frysinger
2012-01-08 17:43 ` Simon Glass
2012-01-08 19:58 ` Mike Frysinger
2012-01-08 23:48 ` Simon Glass
2012-01-09 17:31 ` Mike Frysinger
2012-01-12 5:38 ` Simon Glass
2012-01-03 22:33 ` [U-Boot] [RFC PATCH v2 0/15] bootstage: record and publish boot progress timing Simon Glass
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='CAPnjgZ1OJz=WgcFZhRfc85u4MTLs_M7rURw2wpO5R89_vT5kGw@mail.gmail.com' \
--to=sjg@chromium.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.