From: chetannanda@gmail.com (Chetan Nanda)
To: linux-arm-kernel@lists.infradead.org
Subject: not able to understand 'icedcc_putc'
Date: Fri, 29 Jan 2010 22:18:55 +0530 [thread overview]
Message-ID: <7f245da81001290848n5630c6b6q68f19369fd0ad5aa@mail.gmail.com> (raw)
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).
############3
static void icedcc_putc(int ch)
{
int status, i = 0x4000000;
do {
if (--i < 0)
return;
asm volatile ("mrc p14, 0, %0, c0, c0, 0" : "=r" (status));
} while (status & 2);
asm("mcr p14, 0, %0, c1, c0, 0" : : "r" (ch));
}
#############
Thanks for your help
~cnanda
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100129/22e360fb/attachment-0001.htm>
next reply other threads:[~2010-01-29 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 16:48 Chetan Nanda [this message]
2010-02-02 8:33 ` not able to understand 'icedcc_putc' Uwe Kleine-König
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=7f245da81001290848n5630c6b6q68f19369fd0ad5aa@mail.gmail.com \
--to=chetannanda@gmail.com \
--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).