@ags:
u-boot reads the fdt, probes stuff, adds things to the fdt, modifies things
in the fdt and passes this modified version on the GNU/Linux kernel.
Assuming you configured your kernel correctly you can inspect the fdt in
runtime. I did this on a beagle bone black (with the "wrong" memory setting
in the fdt: memory { device_type = "memory"; reg = <0x80000000
0x10000000l>; };)
root@beagle-bone-black-ml:/proc/device-tree/memory# cat /proc/cpuinfo
processor : 0
model name : ARMv7 Processor rev 2 (v7l)
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls
vfpd32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc08
CPU revision : 2
Hardware : Generic AM33XX (Flattened Device Tree)
Revision : 0000
Serial : 0000000000000000
root@beagle-bone-black-ml:/proc/device-tree/memory# cat /proc/version
Linux version 3.14.1 (builder@ubuntu-srvr-lv-kvm3) (gcc version 4.8.1 (GCC)
) #1 SMP Mon Apr 21 14:46:38 EEST 2014
root@beagle-bone-black-ml:/proc/device-tree/memory# hexdump -C
'/proc/device-tree/memory/name'
00000000 6d 65 6d 6f 72 79 00 |memory.|
00000007
root@beagle-bone-black-ml:/proc/device-tree/memory# hexdump -C
'/proc/device-tree/memory/device_type'
00000000 6d 65 6d 6f 72 79 00 |memory.|
00000007
root@beagle-bone-black-ml:/proc/device-tree/memory# hexdump -C
'/proc/device-tree/memory/reg'
00000000 80 00 00 00 20 00 00 00 |.... ...|
00000008
As you can see the reg setting was "automagically" changed by u-boot to
0x20000000 and passed on to the GNU/Linux kernel.
So it will not make any difference if you change the memory size setting in
the fdt file, except for making things a bit more consistent.
Regards,
Robert
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
