devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: [RFC][PATCH] add FDT address translation
Date: Wed, 05 Jan 2011 00:20:16 +0100	[thread overview]
Message-ID: <4D23AB30.5050502@home.nl> (raw)
In-Reply-To: <20110104223847.GA13014-MrY2KI0G/OVr83L8+7iqerDks+cytr/Z@public.gmane.org>

On 1/4/11 11:38 PM, Grant Likely wrote:
> On Tue, Jan 04, 2011 at 10:47:57PM +0100, Walter Goossens wrote:
>> Nobody interested in this stuff?
> Heh, it's a little hard to get people's attention on patches posted
> right before the new year and right before the merge window.  I
> personally won't be able to take a proper look at it before -rc1.
>
> g.
That's no problem, I'm in no hurry, just wanted to know if there was 
still interest. Otherwise I'd just push it in the nios2 tree, but since 
this is not at all nios2 specific I'd rather wait a bit longer and get 
it in the devicetree git...

Thanks for the reply!

Walter
>> I'm working on devicetree support for the NiosII processor and there
>> bridges are quite commonly used so this is a must to get early
>> printk going without dirty hacks. I thought at least Microblaze
>> would need this as well as that's also a synthesizable core but
>> maybe I'm mistaking.
>>
>> On 12/30/10 12:38 AM, Walter Goossens wrote:
>>> This patch adds address translations to fdt. Needed when the early
>>> console is connected to a simple-bus that has address translation
>>> enabled.
>>>
>>> To be honest, I'm not too happy about this solution but it works
>>> and most code is stolen from other parts of the fdt code, so I'm
>>> probably not doing too weird stuff :)
>>> What do you guys think of this?
>>>
>>> Greetz Walter
>>>
>>>
>>> _______________________________________________
>>> devicetree-discuss mailing list
>>> devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
>>> https://lists.ozlabs.org/listinfo/devicetree-discuss
>> _______________________________________________
>> devicetree-discuss mailing list
>> devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
>> https://lists.ozlabs.org/listinfo/devicetree-discuss
>

  parent reply	other threads:[~2011-01-04 23:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-29 23:38 [RFC][PATCH] add FDT address translation Walter Goossens
     [not found] ` <4D1BC658.4040608-CmkmPbn3yAE@public.gmane.org>
2011-01-04 21:47   ` Walter Goossens
     [not found]     ` <4D23958D.6000206-CmkmPbn3yAE@public.gmane.org>
2011-01-04 22:38       ` Grant Likely
     [not found]         ` <20110104223847.GA13014-MrY2KI0G/OVr83L8+7iqerDks+cytr/Z@public.gmane.org>
2011-01-04 23:20           ` Walter Goossens [this message]
2011-02-12  9:11   ` Grant Likely
     [not found]     ` <20110212091124.GC17755-MrY2KI0G/OVr83L8+7iqerDks+cytr/Z@public.gmane.org>
2011-02-13 21:51       ` 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=4D23AB30.5050502@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).