linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: Single binary kernel for all i.MX
Date: Fri, 12 Nov 2010 16:53:42 +0100	[thread overview]
Message-ID: <20101112155342.GJ18358@pengutronix.de> (raw)
In-Reply-To: <AANLkTim7znztJgGvZ5ZsV=ei=_W4YpjU3-5zWonrQ9ME@mail.gmail.com>

Hi Shawn,

On Fri, Nov 12, 2010 at 11:40:41PM +0800, Shawn Guo wrote:
> I'm studying at the implementation.  Can you please help me understand
> how "addruart" in plat-mxc/include/mach/debug-macro.S works for single
> image?
> 
>         .macro  addruart, rp, rv
>         ldr     \rp, =UART_PADDR        @ physical
>         ldr     \rv, =UART_VADDR        @ virtual
>         .endm
> 
> We have this macro to get physical base address of UART.  However
> UART_PADDR is defined as MX?_UART1_BASE_ADDR depending on
> CONFIG_ARCH_MX*.  When all CONFIG_ARCH_MX* get defined in single image
> case, how does UART_PADDR work for all CONFIG_ARCH_MX*?
In a kernel that supports more than one SoC, DEBUG_LL won't work.  This
is generally OK, because DEBUG_LL is only needed when bringing up a
machine.  Therefor you can use a tailored kernel that only supports your
shiny new machine.

Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-K?nig            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2010-11-12 15:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-05 12:18 Single binary kernel for all i.MX Sascha Hauer
2010-11-05 12:29 ` Baruch Siach
2010-11-05 12:31   ` Sascha Hauer
2010-11-05 18:59     ` Eric Miao
2010-11-07 11:34       ` Sascha Hauer
2010-11-12 15:40 ` Shawn Guo
2010-11-12 15:53   ` Uwe Kleine-König [this message]
2010-11-12 17:29     ` Gadiyar, Anand
2010-11-12 18:50       ` Uwe Kleine-König
2010-11-13 15:30         ` Nicolas Pitre
2010-11-13 15:26       ` Nicolas Pitre

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=20101112155342.GJ18358@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).