From: Sergei Shtylyov <sshtylyov@mvista.com>
To: John Crispin <blogic@openwrt.org>
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: [PATCH V3 7/10] MIPS: ralink: adds early_printk support
Date: Mon, 28 Jan 2013 16:16:39 +0400 [thread overview]
Message-ID: <51066C27.4070403@mvista.com> (raw)
In-Reply-To: <1359358817-3867-1-git-send-email-blogic@openwrt.org>
Hello.
On 28-01-2013 11:40, John Crispin wrote:
> Add the code needed to make early printk work.
> Signed-off-by: John Crispin <blogic@openwrt.org>
> ---
> arch/mips/ralink/early_printk.c | 45 +++++++++++++++++++++++++++++++++++++++
> 1 file changed, 45 insertions(+)
> create mode 100644 arch/mips/ralink/early_printk.c
> diff --git a/arch/mips/ralink/early_printk.c b/arch/mips/ralink/early_printk.c
> new file mode 100644
> index 0000000..68aabb9
> --- /dev/null
> +++ b/arch/mips/ralink/early_printk.c
> @@ -0,0 +1,45 @@
> +/*
> + * This program is free software; you can redistribute it and/or modify it
> + * under the terms of the GNU General Public License version 2 as published
> + * by the Free Software Foundation.
> + *
> + * Copyright (C) 2011-2012 Gabor Juhos <juhosg@openwrt.org>
> + */
> +
> +#include <linux/io.h>
> +#include <linux/serial_reg.h>
> +
> +#include <asm/addrspace.h>
> +
> +/* UART registers */
this comment refers to the register #defines below, why it is here?
> +#define EARLY_UART_BASE 0x10000c00
> +
> +#define UART_REG_RX 0x00
> +#define UART_REG_TX 0x04
> +#define UART_REG_IER 0x08
> +#define UART_REG_IIR 0x0c
> +#define UART_REG_FCR 0x10
> +#define UART_REG_LCR 0x14
> +#define UART_REG_MCR 0x18
> +#define UART_REG_LSR 0x1c
WBR, Sergei
next prev parent reply other threads:[~2013-01-28 12:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 7:40 [PATCH V3 7/10] MIPS: ralink: adds early_printk support John Crispin
2013-01-28 12:16 ` Sergei Shtylyov [this message]
2013-01-28 21:26 ` John Crispin
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=51066C27.4070403@mvista.com \
--to=sshtylyov@mvista.com \
--cc=blogic@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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 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.