<sjg1>
xypron: OK...I am not going to have much time for the next few weeks, but we'll see. If it breaks something we can revert it later I suppose. Could you add some test code to that patch?
naoki1 has joined #u-boot
naoki has quit [Ping timeout: 256 seconds]
naoki1 is now known as naoki
<Tartarus>
So, yes, I see a difference between "U-Boot creates the table" and "U-Boot copies the table via qfw", since I assume there is also the case of "U-Boot copies / is passed the table by other firmware on x86"
<Tartarus>
If in the x86 case we can point at them and not have to do anything else, the question I have is why can't we do that in qemu, or all qemu platforms if we do it on x86
goliath has quit [Quit: SIGSEGV]
<xypron>
sjg1: On sandbox_defconfig which uses ACPI 'efidebug memmap' called with ./u-boot -T a reservation at fffe000 shows up after running hello world. This could be checked in a python test. But you planned to restructure the code to move most of this to a module in lib/. After the restructuring a C test might be more adequate.
vagrantc has quit [Quit: leaving]
mmu_man has quit [Ping timeout: 256 seconds]
slobodan has quit [Ping timeout: 268 seconds]
<sjg1>
Tartarus: You can see the code at bios_linker_add_checksum(). I haven't dug into it but it needs to be set up by U-Boot
<sjg1>
Tartarus: Of course, I have a pretty low opinion of QEMU after they rejected this perfectly reasonable patch
persmule has quit [Remote host closed the connection]
persmule has joined #u-boot
mmu_man has quit [Ping timeout: 246 seconds]
mmu_man has joined #u-boot
dsimic has quit [Ping timeout: 256 seconds]
dsimic has joined #u-boot
mckoan is now known as mckoan|away
milkylainen has quit [Server closed connection]
milkylainen has joined #u-boot
<umbramalison>
struggling with a custom TI AM57xx board. IODelay hangs on readl iodelay_config_base. boot if i comment out IODelay from board.c. at run-time i can read iodelay_config_base. any idea why it might hang reading this reg on startup?
thopiekar has quit [Ping timeout: 256 seconds]
<umbramalison>
other than ti e2e forums which i'm already aware of, anywhere else where i might find some experience with custom ti boards and u-boot? thanks
thopiekar has joined #u-boot
gsz has quit [Ping timeout: 260 seconds]
xroumegue has quit [Ping timeout: 260 seconds]
<ad__>
umbramalison: there are some iodelay references in other ti stuff, did you had a look ?
<ad__>
board/ti/am57xx/board.c
<ad__>
board/ti/dra7xx/evm.c
<ad__>
maybe you can find proper access there
<umbramalison>
ad__ i'm fairly certain i based my board files on evm/idk and a phycore (as i have the eval board for it, but they didn't get theirs upstream). I just going to look again to be sure i'm making the most of any help i get :)
<umbramalison>
yes, so regarding IODelay, i have not deviated from ti/am57xx/board.c, ti/dra7xx/evm.c is a little different, but i don't see anything relevant.
<umbramalison>
I should state very clearly though, that the board design deviates, such as no PMIC (it is there, but it's managed by a housekeeper MCU). Therefore I have been stripping PMIC related things away
sam_sepi0l has quit [Read error: Connection reset by peer]
brassado has joined #u-boot
C-o-r-E has joined #u-boot
<C-o-r-E>
Hello
<C-o-r-E>
I'm trying to build u-boot for the nios2 platform and wondering what I need to flash
<C-o-r-E>
I've got a u-boot elf file, u-boot.bin, u-boot-no-dtb.bin etc. I guess that from the naming, I probably want to flash the .bin file as it includes the device tree?