From: Walter Goossens <waltergoossens-CmkmPbn3yAE@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: microblaze console init
Date: Sat, 11 Dec 2010 23:15:31 +0100 [thread overview]
Message-ID: <4D03F803.6060903@home.nl> (raw)
In-Reply-To: <AANLkTinw3mqpmiUkzf9Drgg+f+b3hFBUoHLmtWSO75GY-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 12/11/10 10:59 PM, Grant Likely wrote:
> On Sat, Dec 11, 2010 at 2:50 PM, Walter Goossens<waltergoossens-CmkmPbn3yAE@public.gmane.org> wrote:
>> I do still have one concern, do I understand correctly that there is no way
>> to do address-translation (the "ranges" stuff) on a flattenend tree, using
>> the of_get_flat_dt_* functions? This would mean that this code would fail to
>> get the correct address for a uartlite connected to a bus that has
>> address-translation.
> Correct, none of the flat tree core code tries to do any range
> translation. In fact, it does very little in the way of looking at
> reg properties at all. Only the absolute bare minimum required to get
> through early boot. It could be done, but there really hasn't been a
> use case for it up to this point. Instead, ranges can be translated
> after the tree has been unflattened into the live form.
>
> g.
>
thanks for the quick response!
I was afraid of this... I'm affraid I do need to use it in the nios
code, well I don't need to but in order to be flexible (and use the
design I'm working with right now) but I would prefer it. The way around
this I currently use is a special parameter in chosen with the address
of the "early uart" (it's only used for early printk).
What's cleanest approach here? An extra property in "chosen" or range
translation in the flatttened tree?
Walter
next prev parent reply other threads:[~2010-12-11 22:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-11 21:50 microblaze console init Walter Goossens
[not found] ` <4D03F229.9070403-CmkmPbn3yAE@public.gmane.org>
2010-12-11 21:59 ` Grant Likely
[not found] ` <AANLkTinw3mqpmiUkzf9Drgg+f+b3hFBUoHLmtWSO75GY-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-12-11 22:15 ` Walter Goossens [this message]
[not found] ` <4D03F803.6060903-CmkmPbn3yAE@public.gmane.org>
2010-12-11 22:18 ` Grant Likely
2010-12-11 22:24 ` Walter Goossens
[not found] ` <4D03FA1B.9040804-CmkmPbn3yAE@public.gmane.org>
2010-12-13 18:59 ` Scott Wood
[not found] ` <20101213125947.12a6db54-N/eSCTBpGwP7j4BuCOFQISmX4OfbXNuMKnGXBo5VDl8@public.gmane.org>
2010-12-13 21:06 ` Walter Goossens
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=4D03F803.6060903@home.nl \
--to=waltergoossens-cmkmpbn3yae@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.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).