<sjg1>
Tartarus: Actually I'm not going to get any time for several days now. So I'll just send it as is. There is an fdtgrep tweak I need to make but it can come later, doesn't need to hold things up
qastokes has joined #u-boot
qastokes has quit [Quit: qastokes]
vagrantc has joined #u-boot
Lokis has joined #u-boot
Lokis has quit [Ping timeout: 252 seconds]
mmu_man has quit [Ping timeout: 265 seconds]
Xavier7 has joined #u-boot
samekh_ has joined #u-boot
samekh has quit [Ping timeout: 256 seconds]
vagrantc has quit [Quit: leaving]
persmule has quit [Remote host closed the connection]
camus1 has joined #u-boot
camus has quit [Ping timeout: 268 seconds]
camus1 is now known as camus
LeSpocky has quit [Ping timeout: 256 seconds]
LeSpocky has joined #u-boot
camus1 has joined #u-boot
camus has quit [Ping timeout: 252 seconds]
camus1 is now known as camus
Antilokis has joined #u-boot
qastokes has joined #u-boot
sdfgsdfg has quit [Quit: ZzzZ]
sdfgsdfg has joined #u-boot
camus has quit [Ping timeout: 240 seconds]
camus has joined #u-boot
qastokes has quit [Quit: qastokes]
camus1 has joined #u-boot
camus has quit [Ping timeout: 265 seconds]
camus1 is now known as camus
<simeonm>
I have CONFIG_SPL_LOAD_FIT_ADDRESS=0x0 and my SPL loads u-boot proper as a FIT image from SPI flash. Where would the FIT image be in memory (or would it be in memory at all?). If I do iminfo 0x0 I get "## Checking Image at 00000000 ...\nUnknown image format!"
<simeonm>
If I do an "sf read" of the FIT image into memory then iminfo works great and I can bootm also, but I want to avoid reading the entire FIT image twice...
<simeonm>
Any ideas?
agust has joined #u-boot
<simeonm>
Changing CONFIG_SPL_LOAD_FIT_ADDRESS do be the same address as I use for the "sf read" of the FIT image doesn't work either - iminfo still doesn't recognise a FIT image
<simeonm>
Indeed, crc32 of my FIT image u-boot-itb file matches the contents of memory after sf load + crc32, but crc32 at CONFIG_SPL_LOAD_FIT_ADDRESS after SPL loads the FIT does not match.
sughosh has joined #u-boot
sdfgsdfg has quit [Quit: ZzzZ]
Xavier7 has quit [Quit: IRcap 8.72 ]
camus1 has joined #u-boot
camus has quit [Ping timeout: 265 seconds]
camus1 is now known as camus
camus has quit [Ping timeout: 240 seconds]
camus has joined #u-boot
fdanis_away is now known as fdanis
mckoan|away is now known as mckoan
sughosh has quit [Read error: Connection reset by peer]
sakman has quit [Ping timeout: 256 seconds]
sszy has joined #u-boot
<chrfle>
thanks sjg1, I'll have a look at it
persmule has joined #u-boot
tre has joined #u-boot
tnovotny has joined #u-boot
persmule has quit [Ping timeout: 276 seconds]
<milkylainen>
sjg1: I have a lot of questions regarding configuration in relation to being in app mode.
<milkylainen>
like Cache-as-ram, 8259 interrupt controller, APIC etc. Do you need those in app mode?
persmule has joined #u-boot
matthias_bgg has joined #u-boot
persmule has quit [Ping timeout: 276 seconds]
sdfgsdfg has joined #u-boot
persmule has joined #u-boot
gsz has joined #u-boot
sbach has quit [Read error: Connection reset by peer]
sbach has joined #u-boot
pbergin has joined #u-boot
persmule has quit [Remote host closed the connection]
mmu_man has joined #u-boot
gsz has quit [Quit: leaving]
michalkotyla has joined #u-boot
michalkotyla has quit [Client Quit]
<milkylainen>
sjg1: CONFIG_EFI_RAM_SIZE. Hmm. Can't that just go from some max-size down? I don't really see the need to configure this manually? I mean. Whatever max UEFI can give us should be ok? For x86 you're going to encounter boards with various memory sizes?
sdfgsdfg has quit [Quit: ZzzZ]
<milkylainen>
hmm. Confusion coding? CONFIG_ENV_SOURCE_FILE or CONFIG_DEFAULT_ENV_FILE
<LeSpocky>
CounterPillow: if you're the patch author, reply on the mailinglist with something like "gentle ping", if you're not the patch author, but reviewed or tested the patch, reply and add your Reviewed-by: or Tested-by: line
<sjg1>
milkylainen: Yes it may be possible to find out how much memory there is and allocate most of that.