Thanks for the reply. I mostly wanted to verify that my understanding of dt
is correct, and this was confusing. I was also hoping to learn something
new (why was the specification in the .dtb file no consistent with the
actual memory being used) - which you've helped with by pointing out the
@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
Can anyone explain how/why the dtc specification of memory size is not
being used, and/or where the actual size is coming from?
On Friday, April 25, 2014 10:02:40 PM UTC-7, ags wrote:
Not necessarily an issue. Originally I was wondering if only half of
available physical memory was being
On Sat, May 3, 2014 at 4:40 PM, ags alfred.g.schm...@gmail.com wrote:
Can anyone explain how/why the dtc specification of memory size is not being
used, and/or where the actual size is coming from?
u-boot... Would you feel more comfortable if i patch the
am335x-boneblack.dtb to the correct
Not necessarily an issue. Originally I was wondering if only half of
available physical memory was being made available. Still, I'd like to
understand why the device tree bindings indicate 256 MB memory, yet it
appears that the full 512 MB are available.
On Thursday, April 24, 2014 7:23:51 AM
Any suggestions on where to look next to figure out what's going on here?
Seems that either something other than the device tree in file
/boot/am335x-boneblack.dts is being read at boot, or there is something
else that is overriding later on, or a boot parameter... or the memory
On Thu, Apr 24, 2014 at 9:13 AM, ags alfred.g.schm...@gmail.com wrote:
Any suggestions on where to look next to figure out what's going on here?
Seems that either something other than the device tree in file
/boot/am335x-boneblack.dts is being read at boot, or there is something
else that is
Hi,
I don't have access to my lab at the moment, so I can not try it myself,
but can you rebuild a fdt and make a change in am335x-bone-common.dtsi?
Please also do:
cat /proc/meminfo before and after the change?
Just search for memory and replace it with:
memory {
I don't see a dtsi in /boot. I did dtc -I dtb -O dts -o test.dts
/boot/am335x-boneblack.dtb. Looking at test.dts I still see memory {...
reg = 0x8000 0x1000 };
However, cat /proc/meminfo returns a first line of MemTotal: 510600 kB
which seems OK - I suppose. It looks like
Hi,
On 04/20/2014 08:03 PM, ags wrote:
I don't see a dtsi in /boot. I did dtc -I dtb -O dts -o test.dts
/boot/am335x-boneblack.dtb. Looking at test.dts I still see memory {...
reg = 0x8000 0x1000 };
However, cat /proc/meminfo returns a first line of MemTotal: 510600
kB which seems OK
On Sunday, April 20, 2014 1:05:03 PM UTC-7, robert.berger wrote:
Which kernel version do you use?
The original installed on flash (shipped in Jan/Feb this year):
I have BBB A6A running Angstrom distro:
Linux beaglebone 3.8.13 #1 SMP Wed Sep 4 09:09:32 CEST 2013 armv7l
GNU/Linux
--
For
11 matches
Mail list logo
