<milkylainen>
LeSpocky: More specifically? The dt memory node?
sughosh has quit [Ping timeout: 252 seconds]
<LeSpocky>
milkylainen: I think that should do if that's what Linux gets the information on memory size from
<LeSpocky>
I'm currently reading U-Boot code to understand possibilities and what is done with other boards
<LeSpocky>
boot is done through a script which loads kernel image and .dtb from ubifs and calls bootz then
<milkylainen>
LeSpocky: Linux can get various bits of memory information in a lot of ways. :) cmdline, dt, atags, e820, acpi, uefi etc..
<LeSpocky>
I know, doesn't make it easier ;-)
<milkylainen>
Mmm. In short. It's an architectural mess.
<milkylainen>
LeSpocky: Sometimes if I couldn't be bothered with dt I modify the cmdline.
<LeSpocky>
I can also make two different .dtb files and load one or the other, not decided which way to go yet
michalkotyla has joined #u-boot
pbergin has quit [Quit: Leaving]
sdfgsdfg has quit [Quit: ZzzZ]
mmu_man has quit [Ping timeout: 245 seconds]
michalkotyla has quit [Quit: michalkotyla]
behanw has joined #u-boot
sstiller has quit [Quit: Leaving]
sdfgsdfg has joined #u-boot
Lokis has joined #u-boot
<ad__>
using "ums 0 mmc 0" but dd from host PC returns in 1 second for a 1GB file
<ad__>
it was workign yesterday. not clar what could be
<Lokis>
hi, Is there any specific method on how to debug "data abort" or "prefetch abort" crashes when developing u-boot?
<ad__>
Lokis: custom board ?
<ad__>
as far as i know, would be sure ddr are well working and properly initialized
<Lokis>
ad__: yes, based on reference design
<ad__>
and all power are stable, cleanb without ripple, enough current on PS, and the like (of course, if custom board)
<Lokis>
ad__: the board, passed all hw tests and linux runs great, just sometimes when I run into these crashes they are really hard to detect, but it is mostly caused by faulty code in my situation
<Lokis>
ad__: in most recent crash I just add some printf's and crashing stop, I thought maybe someone in this channel runs into these type or problems often.
camus1 has joined #u-boot
camus has quit [Ping timeout: 256 seconds]
camus1 is now known as camus
sdfgsdfg has quit [Quit: ZzzZ]
mmu_man has joined #u-boot
monstr has quit [Ping timeout: 268 seconds]
monstr has joined #u-boot
Lokis has quit [Read error: Connection reset by peer]
camus1 has joined #u-boot
camus has quit [Ping timeout: 256 seconds]
camus1 is now known as camus
Antilokis has joined #u-boot
camus has quit [Ping timeout: 252 seconds]
camus has joined #u-boot
tnovotny has quit [Quit: Leaving]
monstr has quit [Remote host closed the connection]
<Forty-Bot>
ad__: did you sync/umount?
redbrain has joined #u-boot
matthias_bgg has quit [Quit: Leaving]
guillaume_g has quit [Quit: Konversation terminated!]
redbrain has quit [Ping timeout: 252 seconds]
srk has quit [Ping timeout: 245 seconds]
redbrain has joined #u-boot
tom5760 has quit [Remote host closed the connection]