From: jeremy.kerr@canonical.com (Jeremy Kerr)
To: linux-arm-kernel@lists.infradead.org
Subject: Boot interface for device trees on ARM
Date: Wed, 19 May 2010 16:50:53 +0800 [thread overview]
Message-ID: <201005191650.55978.jeremy.kerr@canonical.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1005180802010.12758@xanadu.home>
Nicolas,
> Exact. For example, on ARM the machine ID is also used to figure out
> the MMU mapping needed to be able to simply be able to debug the very
> early assembly boot stage when there isn't even a stack available.
I get the impression that this is the only thing that we need the io_pg_offset
for - setting up the debug page mapping, for very early printk output.
If this is the case, I would much rather have it as a compile-time constant
when doing this early debug; this is what I have been doing for DT boot in my
tree (however, I would like to move it to something more configurable).
In the cases where we need to debug the pre-C stuff (ie, machine bringup), I
think we can live with a compile-time constant, rather than having to define a
special 'exception' in the DT boot interface to handle this.
Or is there another early use of the mdesc that I'm not aware of?
Cheers,
Jeremy
next prev parent reply other threads:[~2010-05-19 8:50 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 2:54 Boot interface for device trees on ARM Jeremy Kerr
2010-05-18 4:34 ` Nicolas Pitre
2010-05-18 5:24 ` Jeremy Kerr
2010-05-18 8:49 ` David Gibson
2010-05-18 12:24 ` Nicolas Pitre
2010-05-18 14:06 ` Jason McMullan
2010-05-19 0:21 ` David Gibson
2010-05-19 0:28 ` David Gibson
2010-05-19 1:28 ` Nicolas Pitre
2010-05-19 6:50 ` David Gibson
2010-05-19 14:45 ` Grant Likely
2010-05-19 1:41 ` Jamie Lokier
2010-05-19 7:12 ` David Gibson
2010-05-19 14:21 ` Grant Likely
2010-05-19 7:25 ` Mitch Bradley
2010-05-19 8:50 ` Jeremy Kerr [this message]
2010-05-18 11:57 ` Nicolas Pitre
2010-05-19 12:13 ` Grant Likely
2010-05-19 16:45 ` Jamie Lokier
2010-05-19 17:10 ` Grant Likely
2010-05-19 17:32 ` M. Warner Losh
2010-05-19 11:57 ` Grant Likely
2010-05-19 12:08 ` Russell King - ARM Linux
2010-05-19 17:52 ` Nicolas Pitre
2010-05-19 20:08 ` Jamie Lokier
2010-05-19 20:22 ` Nicolas Pitre
2010-05-21 16:24 ` John Rigby
2010-05-21 16:27 ` Jamie Bennett
2010-05-21 19:59 ` Russell King - ARM Linux
2010-06-03 21:12 ` Grant Likely
2010-06-04 20:01 ` Grant Likely
2010-06-04 20:33 ` John Rigby
2010-06-04 20:37 ` Jon Loeliger
2010-06-04 21:07 ` Grant Likely
2010-06-05 1:33 ` Jeremy Kerr
2010-06-05 2:29 ` Nicolas Pitre
2010-06-05 5:59 ` Grant Likely
2010-06-09 4:26 ` Jeremy Kerr
2010-06-09 13:09 ` Nicolas Pitre
2010-05-19 11:45 ` Grant Likely
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=201005191650.55978.jeremy.kerr@canonical.com \
--to=jeremy.kerr@canonical.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).