From: Jarkko Nikula <jarkko.nikula@nokia.com>
To: ext Paul Walmsley <paul@pwsan.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH RESEND 0/4] Runtime constants: define (some) OMAP address bases at runtime rather than compile time for multiboot
Date: Wed, 21 Nov 2007 09:03:39 +0200 [thread overview]
Message-ID: <20071121090339.4f256297.jarkko.nikula@nokia.com> (raw)
In-Reply-To: <20071121001620.571082090@pwsan.com>
On Tue, 20 Nov 2007 17:16:20 -0700
"ext Paul Walmsley" <paul@pwsan.com> wrote:
> So, convert the users of these defines to use runtime-computed global
> variables where possible. Where not possible (e.g., in static
> initializers), use chip-specific preprocessor macros. The global
> variables are set up early in the board-*.c files in the map_io()
> code, before almost everything else.
>
Hi
How about calling omap2_set_globals_242x() from
arch/arm/mach-omap2/io.c: omap2_map_common_io() in order to avoid
modifications to n board files?
Jarkko
next prev parent reply other threads:[~2007-11-21 7:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 0:16 [PATCH RESEND 0/4] Runtime constants: define (some) OMAP address bases at runtime rather than compile time for multiboot Paul Walmsley
2007-11-21 0:16 ` [PATCH RESEND 1/4] Runtime constants: introduce omap2_set_globals_*() Paul Walmsley
2007-11-21 0:16 ` [PATCH RESEND 2/4] Runtime constants: use runtime-computed SDRC base Paul Walmsley
2007-11-21 0:16 ` [PATCH RESEND 3/4] Runtime constants: use runtime-computed SMS base Paul Walmsley
2007-11-21 0:16 ` [PATCH RESEND 4/4] Runtime constants: use runtime-computed system control module base Paul Walmsley
2007-11-21 7:03 ` Jarkko Nikula [this message]
2007-11-21 7:13 ` [PATCH RESEND 0/4] Runtime constants: define (some) OMAP address bases at runtime rather than compile time for multiboot Paul Walmsley
2007-11-21 7:56 ` Jarkko Nikula
2007-11-23 22:08 ` Tony Lindgren
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=20071121090339.4f256297.jarkko.nikula@nokia.com \
--to=jarkko.nikula@nokia.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=paul@pwsan.com \
/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