FreeBSD 10 on Dockstar (Marvell Kirkwood)

[Nathan Whitehorn]

On 01/03/14 12:12, Ian Lepore wrote:
> On Tue, 2013-12-31 at 18:30 -0500, Nathan Whitehorn wrote:
>> On 12/31/13 16:10, Markus Pfeiffer wrote:
>>> Hi all,
>>>
>>> I managed "fixing" it by editing the dockstar.dts file and putting for ranges:
>>>
>>>   ranges = <0x0 0x2f 0xf9300000 0x00100000>
>>>
>>> Now I just have to figure out why this "fixes" it, and what damage that patch
>>> does.
>>> I also have some pathces for the LED on the dockstar which will tip up in my
>>> github soon.
>>>
>>> Cheers,
>>> markus
>> Which node did you add this to? I'm trying to make our FDT code more
>> standards-compliant. This seems like something where we missed a spot.
>> -Nathan
> The surrounding context looks like this:
>
> 	localbus at f1000000 {
> 		#address-cells = <2>;
> 		#size-cells = <1>;
> 		compatible = "mrvl,lbc";
>
> 		/* This reflects CPU decode windows setup. */
> 		ranges = <0x0 0x0f 0xf9300000 0x00100000
> 			  0x1 0x1e 0xfa000000 0x00100000
> 			  0x2 0x1d 0xfa100000 0x02000000
> 			  0x3 0x1b 0xfc100000 0x00000400>;
>
> 		nor at 0,0 {
> 			#address-cells = <1>;
>
> Specifying ranges here is a Marvel-SoC-specific thing, other arm socs
> don't require it.  The Marvell code uses these values to set up hardware
> memory mapping; on the Marvell chips it's possible to map DRAM, NAND,
> PCIe, etc into physical address ranges of your choosing.
>
> -- Ian
>
>

Ah, it's this horrible broken fdt_immr() stuff. I've killed that on PPC
now. I'll see what I can do for ARM.
-Nathan