<mps>
is there difference between itb and dtb generated files?
monstr has quit [Remote host closed the connection]
<cambrian_invader>
only the structure
<mps>
aha. could the itb be loaded with FDT file.itb in extlinux.conf directive
zibolo has quit [Ping timeout: 248 seconds]
frieder has quit [Remote host closed the connection]
obsrwr is now known as eternalforms
guillaume_g has quit [Quit: Konversation terminated!]
littlebobeep has quit [Ping timeout: 240 seconds]
littlebobeep has joined #u-boot
mckoan is now known as mckoan|away
NonaSuomy has joined #u-boot
apritzel_ has quit [Ping timeout: 260 seconds]
littlebobeep has quit [Ping timeout: 240 seconds]
sszy has quit [Ping timeout: 248 seconds]
littlebobeep has joined #u-boot
mrnuke has joined #u-boot
sicelo has quit [Quit: Bye!]
sicelo has joined #u-boot
sicelo has joined #u-boot
Patater has quit [Quit: Explodes into a thousand pieces]
Patater has joined #u-boot
apritzel_ has joined #u-boot
littlebobeep has quit [Ping timeout: 240 seconds]
littlebobeep has joined #u-boot
prabhakarlad has quit [Quit: Client closed]
<cambrian_invader>
mps: yes, but iminfo is probably more interesting
<cambrian_invader>
and Linux won't really be able to boot from it :)
<mps>
cambrian_invader: yes, after I looked details I found its file and see that it needs to be added to kernel image with mkimage
<mps>
I build chromebook kernels this way
<mps>
and this is in build scripts created long ago so I forgot about this
littlebobeep has quit [Ping timeout: 240 seconds]
littlebobeep has joined #u-boot
NonaSuomy has quit [Ping timeout: 246 seconds]
___nick___ has quit [Ping timeout: 248 seconds]
<emz229>
cambrian_invader: thank you for your help last week, I have made progress but still working on loading the env variable as early as possible..
<cambrian_invader>
np
<emz229>
is there a simple way to read a specific spi flash addres (even if its only one byte) around or before the call to board_early_init_f?
NonaSuomy has joined #u-boot
<cambrian_invader>
do it in that function?
<emz229>
a call to env_get can not work there because it is before the env even gets loaded
<emz229>
after looking though code of how the sf functions work.. im a bit more confused why there are so many layers to use the spi flash
<cambrian_invader>
the reason there are so many layers is that people have hacked features into it over the years
<cambrian_invader>
why do you need to read spi flash?
<emz229>
the system is setup so that on the first boot it saves a value to the environment of what SOM is in use, then reset, on that reset I need to read that value extremely early to be able to know how to configure the UART
<cambrian_invader>
why do you need to be able to configure the uart before the environment is loaded?
<emz229>
the call to setup_internal_uart() sets pads on the intel atom soc, which if the function is called later the port configuration does not seem to take effect
<cambrian_invader>
seems like that's only used when you have a debug uart enabled
<cambrian_invader>
can you boot without a debug uart?
<emz229>
yes, one board vendor decided to use the legacy (debug) uart output directly and one decided to use a embedded controller to output the uart data to the same pins
<emz229>
the platform will boot, but no console will be displayed if there is no uart
<cambrian_invader>
uh, specifically I mean CONFIG_DEBUG_UART
<cambrian_invader>
not just the uart you use for debugging