From mboxrd@z Thu Jan 1 00:00:00 1970 From: Walter Goossens Subject: Re: microblaze console init Date: Sat, 11 Dec 2010 23:24:27 +0100 Message-ID: <4D03FA1B.9040804@home.nl> References: <4D03F229.9070403@home.nl> <4D03F803.6060903@home.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org To: Grant Likely Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org List-Id: devicetree@vger.kernel.org On 12/11/10 11:18 PM, Grant Likely wrote: > On Sat, Dec 11, 2010 at 3:15 PM, Walter Goossens wrote: >> On 12/11/10 10:59 PM, Grant Likely wrote: >>> On Sat, Dec 11, 2010 at 2:50 PM, Walter Goossens >>> 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? > Implement ranges translation in the flat tree code. It wouldn't be > very hard, and will be a lot more maintainable in the long run. > > g. > I'll have a stab at it. Thanks! Walter