linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Allow using machine ID for DEBUG_LL macros
Date: Thu, 3 Feb 2011 19:13:08 -0800	[thread overview]
Message-ID: <20110204031307.GS3322@atomide.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1102032057070.12104@xanadu.home>

* Nicolas Pitre <nico@fluxnic.net> [110203 18:01]:
> On Thu, 3 Feb 2011, Tony Lindgren wrote:
> 
> > Hi all,
> > 
> > Here are two patches that allow using machine ID for DEBUG_LL
> > macros by adding a new macro inituart.
> 
> This won't work with the device tree support as the machine ID is then 
> replaced with a catch-it-all-with-dt-support machine ID.

Hmm, maybe for device tree we could only have it initialized later
on by setting up custom early_printk in early_printk.c based on the
device tree data or machine ID?

It won't work very early then though.. If we want it to work early
we could allocate some fixed memory chunk for addruart etc functions
for which the bootloader just passes addresses.

Tony

  reply	other threads:[~2011-02-04  3:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-04  1:22 [PATCH 0/2] Allow using machine ID for DEBUG_LL macros Tony Lindgren
2011-02-04  1:22 ` [PATCH 1/2] ARM: Add inituart macro to initialize DEBUG_LL serial port based on the machine ID Tony Lindgren
2011-02-04  2:16   ` Nicolas Pitre
2011-02-04  8:39   ` Russell King - ARM Linux
2011-02-04 12:32     ` Russell King - ARM Linux
2011-02-04 16:44       ` Tony Lindgren
2011-02-04  1:22 ` [PATCH 2/2] ARM: Add empty inituart macros Tony Lindgren
2011-02-04  2:20   ` Nicolas Pitre
2011-02-04  3:07     ` Tony Lindgren
2011-02-04  2:02 ` [PATCH 0/2] Allow using machine ID for DEBUG_LL macros Nicolas Pitre
2011-02-04  3:13   ` Tony Lindgren [this message]
2011-02-04  3:39     ` 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=20110204031307.GS3322@atomide.com \
    --to=tony@atomide.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).