From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: not able to understand 'icedcc_putc'
Date: Tue, 2 Feb 2010 09:33:53 +0100 [thread overview]
Message-ID: <20100202083353.GA22848@pengutronix.de> (raw)
In-Reply-To: <7f245da81001290848n5630c6b6q68f19369fd0ad5aa@mail.gmail.com>
Hello,
On Fri, Jan 29, 2010 at 10:18:55PM +0530, Chetan Nanda wrote:
> Hello,
>
> I am newbie to ARM core. This might be a very silly question, but I am not
> able to understand how 'icedcc_putc' function prints a character on console
> (UART).
It doesn't, so no wonder you don't see how it does.
icedcc_putc uses the debug communications channel. You can read it via
jtag.
If you want to understand the output on the serial console, you have to
look into <mach/uncompress.h>.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2010-02-02 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 16:48 not able to understand 'icedcc_putc' Chetan Nanda
2010-02-02 8:33 ` Uwe Kleine-König [this message]
2010-02-02 8:41 ` Chetan Nanda
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=20100202083353.GA22848@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).