From: Grant Likely <glikely@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Porting UBoot without UART
Date: Fri, 25 Feb 2005 09:00:11 -0700 [thread overview]
Message-ID: <528646bc0502250800b68e268@mail.gmail.com> (raw)
In-Reply-To: <20050225075152.8240FC1430@atlas.denx.de>
On Fri, 25 Feb 2005 08:51:47 +0100, Wolfgang Denk <wd@denx.de> wrote:
> Dear Grant,
>
> in message <528646bc0502242240233e0d7f@mail.gmail.com> you wrote:
> >
> >
> > >From the original post: "We're using some emulation box to develop our
> > SoC. Somehow the UART will the last component available for firmware
> > development."
> >
> > I don't think that is the situation that Shawn is describing. To me
> > it sounded like he is starting firmware development before all of the
> > functionality is delivered by the hardware engineers. I don't think
>
> You are right. Then Ladislav Michl suggested to use special console
> functions for output, which works, but misses most of the
> "interesting" startup messages which are printed long before the
> device funtions are installed.
Ahh, thank you. I had misunderstood what you were talking about.
> > that he is refering to initialization order. Shawn, could you please
> > clarify?
>
> Initialization order plays only a role here as a console device
> starts working too late. The native console port is the serial port.
So what needs to be modified to do this? Create new serial_putc,
_getc, _init etc. functions that send messages to where he needs them?
Cheers,
g.
next prev parent reply other threads:[~2005-02-25 16:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 19:21 [U-Boot-Users] Porting UBoot without UART Shawn Jin
2005-02-22 19:49 ` Ladislav Michl
2005-02-24 22:39 ` Wolfgang Denk
2005-02-25 6:40 ` Grant Likely
2005-02-25 7:51 ` Wolfgang Denk
2005-02-25 16:00 ` Grant Likely [this message]
2005-02-25 20:09 ` Wolfgang Denk
2005-02-27 11:55 ` Adam Kent
2005-02-25 17:55 ` Shawn Jin
2005-02-25 18:00 ` Grant Likely
2005-02-24 22:38 ` Wolfgang Denk
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=528646bc0502250800b68e268@mail.gmail.com \
--to=glikely@gmail.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.