<SlimeyX>
i have a few boards that use p1010 and t1023 im trying to port to openwrt but u-boot was crippled by the vendor so im trying to figure out from the gpl sources how to fix that
rvalue has quit [Ping timeout: 252 seconds]
<SlimeyX>
the t family cpu is close to the reference board except the aqr106 and ath80xx eth phy instead of realtek
<SlimeyX>
nxp made a t1023wlan board thats elusive apparently
joeskb7 has quit [Quit: Lost terminal]
joeskb7 has joined #u-boot
MyNetAz has quit [Remote host closed the connection]
joeskb7 has quit [Quit: Lost terminal]
joeskb7 has joined #u-boot
joeskb7 has quit [Client Quit]
totkeks has quit [Ping timeout: 246 seconds]
joeskb7 has joined #u-boot
joeskb7 has quit [Client Quit]
joeskb7 has joined #u-boot
joeskb7 has quit [Client Quit]
joeskb7 has joined #u-boot
joeskb7 has quit [Client Quit]
joeskb7 has joined #u-boot
joeskb7 has quit [Quit: Lost terminal]
joeskb7 has joined #u-boot
joeskb7 has quit [Client Quit]
joeskb7 has joined #u-boot
ikarso has quit [Quit: Connection closed for inactivity]
* Forty-Bot
made a la1046 board for work but hasn't touched it recently
zibolo has quit [Ping timeout: 260 seconds]
zibolo_ has joined #u-boot
joeskb7 has quit [Quit: Lost terminal]
joeskb7 has joined #u-boot
joeskb7 has quit [Quit: Lost terminal]
joeskb7 has joined #u-boot
baltazar has quit [Ping timeout: 248 seconds]
baltazar has joined #u-boot
joeskb7 has quit [Quit: Lost terminal]
joeskb7 has joined #u-boot
goliath has quit [Quit: SIGSEGV]
Daanct12 has joined #u-boot
vardhan has joined #u-boot
mmu_man has quit [Ping timeout: 260 seconds]
<shadow>
I am clearly lacking depth or understanding about the LwIP dhcp issue. I think I should have written something else where I said 'lwip_init' in my postscript to the list
joeskb7 has quit [Quit: Lost terminal]
joeskb7 has joined #u-boot
joeskb7 has quit [Quit: Lost terminal]
joeskb7 has joined #u-boot
joeskb7 has quit [Quit: Lost terminal]
joeskb7 has joined #u-boot
joeskb7 has quit [Client Quit]
joeskb7 has joined #u-boot
joeskb7 has quit [Quit: Lost terminal]
persmule has quit [Remote host closed the connection]
warpme has quit [Read error: Connection reset by peer]
warpme has joined #u-boot
warpme has quit [Read error: Connection reset by peer]
prabhakalad has quit [Quit: Konversation terminated!]
prabhakalad has joined #u-boot
warpme has joined #u-boot
alpernebbi has quit [Ping timeout: 265 seconds]
alpernebbi has joined #u-boot
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
frytaped has joined #u-boot
persmule has joined #u-boot
goliath has joined #u-boot
vardhan has quit [Ping timeout: 252 seconds]
ALTracer has joined #u-boot
<ALTracer>
kboardinfo
<xypron>
Tartarus: concerning Jonas Karlmann's concerns about boot speed: I think it would make sense to change the sequence of standard bootmeths to: fast devices (i.e. block devices), global methods (i.e. EFI), slow devices (i.e. TFTP) in a follow up change.
rvalue has quit [Read error: Connection reset by peer]
<RoganDawes>
marex: I started with your imx28evk config file that I found via https://web.archive.org/web/20180831004104/http://jalderman.org/?p=348, but figured the RAM was different. I took the init sequence that Fabio added to his u-boot tree's Wink branch, which is almost identical to the default init, just with one bit different. I derived it by decrypting
<RoganDawes>
the bootstream file in the vendor's u-boot partition, using the rockbox project's sbtoelf utility. That gave me their bootlet that did the DDR initialisation on my board, and I then compared the words against the default init sequence to get the change. That was able to successfully boot on my hub when written to flash. So, I figured that it would
<RoganDawes>
make sense to use the same sequence of bytes as the DDR init sequence in my OpenOCD board init method.
rvalue has joined #u-boot
<RoganDawes>
Ends up being *significantly* different from what was in your config file, which was quite surprising. Obviously, some values were zeroes which I guess could easily be omitted as default, but there were a lot of differences apart from those.
<RoganDawes>
marex: doh, sorry. It was Fabio's initial config file I was thinking of. ignore me
<f_>
Hm, unsure what's going in, but I was subscribed to the u-boot@ ML, and despite that I just tried sending a mail there and it is awaiting moderation
<f_>
I thought that was only done if an email was sent from an unsubscribed address. TIL
vardhan has joined #u-boot
<Kwiboo>
xypron: I was thinking something similar, currently by defalt on rockchip we have boot_targets env "mmc1 mmc0 nvme scsi usb pxe dhcp spi" and bootmeths env is unset, being able to add the global bootmeths to boot_targets could be an option, e.g. use "mmc1 mmc0 nvme scsi efi_mgr usb pxe dhcp spi" or similar
<Kwiboo>
or possible until an ESP partition is found during normal bootdev hunt it can trigger the global efi_mgr bootmeth before continuing with the regular bootmeths
<xypron>
Kwiboo: The difference between efi_mgr and all the others is that it is global. I.e. it looks at all devices. So handling USB afterwards would not lead to a significant speed up as the USB bus needs to be scanned for the global method.
<xypron>
What we need to get rid of is the non-mgr EFI bootmeth. It should nor run before the EFI boot manager.
Daanct12 has quit [Quit: WeeChat 4.4.4]
<xypron>
Kwiboo: What is your Sunxi specific conern?
<Kwiboo>
however for rockchip this has changed since the initial conversion from distro boot to standard boot, when efi mgr was converted to a global bootmeth
<Kwiboo>
until the new bootdev hunt in that patch, this has not been a real issue, beside the earlier lmb and memory overlap issue, now this slows down boot and affect all rockchip users, e.g. pcie probe adds 1+ second for each unpopulated pcie controller and usb take 1-3 seconds for each usb controller
<sjg1>
shadow: Yes you do need to define CONFIG_LOG - that seems like a bug in the docs, or perhaps something we should adjust?
<shadow>
from not knowing much and web-search for how to enable debug output in U-Boot, I get to this point where the advice seems to be for developers looking to add debug statements but not clear to me how to consume debug output.
<shadow>
the docs are not wrong, they're just for a different audience is how I read into it
<shadow>
I'm looking for "you are a moderately technical user and here is how to provide better information to developers that know this stuff"
<shadow>
for example the advice from Marek in chat above follows the documentation but in one concise explanation it's easier to understand
RoganDawes has joined #u-boot
<shadow>
enum log_level_t "Log levels supported, ranging from most to least important" well okay if I'm looking for debug info, then the debug info is more important to me. It takes a moment to reason about this. A user documentation would say "use X, it is probably what you want. Increase to Y if you want one level more verbose than that."