Thread (6 messages) 6 messages, 5 authors, 2014-01-03

Re: commit e38c0a1f breaks powerpc boards with uli1575 chip

From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: 2013-12-30 03:14:46
Also in: linux-devicetree, lkml

On Thu, 2013-12-19 at 08:42 +0400, Nikita Yushchenko wrote:
No, this does not help.

I've dumped the actual content of 'range' and 'addr' at the failure
point 
(i.e. ar point that returns error with e38c0a1f but passes without 
e38c0a1f ):

OF: default map, cp=0, s=10000, da=70
range:  01 00 00 00 00 00 00 00 00 00 00 00
 addr:  00 00 00 00 00 00 00 00 00 00 00 70
Something that has a #address-cells larger than 2, or more generally,
an address field that contains more than a single number, must have
a specific translation backend, like we have for PCI.

This is a bit annoying but originates from the original OFW stuff on
which this stuff is based where the bus node would provide the methods
for translation.

Cheers,
Ben.
 
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help