All of lore.kernel.org
 help / color / mirror / Atom feed
From: Haleigh Novak <haleigh@edt.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] post_codes in u-boot?
Date: Fri, 9 Dec 2016 23:50:39 +0000	[thread overview]
Message-ID: <1481327439650.14735@edt.com> (raw)

Hello All,


I am currently deciphering post_code ouput on a machine running Yocto with a bios of coreboot with a payload of SeaBIOS and another (i think) u-boot, in searching online for one of the post_code values I stumbled on a post (http://lists.denx.de/pipermail/u-boot/2016-January/241577.html) noting that u-boot has post codes of its own. I was wondering if there was a consolidation of most (if not all) of the post_codes used, like there sort of is in coreboot at /src/console/post_code.h; or if there is not would someone mind giving me a direction on what function(s) u-boot uses to post the u-boot post_codes; i.e. coreboot utilizes a function called post_code as well as asm code and some of the binaries have their own post codes  - is there anything like that in u-boot?


Thank you for your time.

HN

             reply	other threads:[~2016-12-09 23:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-09 23:50 Haleigh Novak [this message]
2016-12-12  2:30 ` [U-Boot] post_codes in u-boot? Bin Meng

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=1481327439650.14735@edt.com \
    --to=haleigh@edt.com \
    --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.