persmule has quit [Remote host closed the connection]
monstr has quit [Remote host closed the connection]
persmule has joined #u-boot
cbmuser has quit [Quit: WeeChat 3.0]
cbmuser has joined #u-boot
mighty-bob has joined #u-boot
mighty-bob has quit [Client Quit]
sszy has joined #u-boot
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ikarso has joined #u-boot
warpme has joined #u-boot
pgreco has quit [Ping timeout: 268 seconds]
pgreco has joined #u-boot
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
monstr has joined #u-boot
monstr has quit [Remote host closed the connection]
f_ has joined #u-boot
<umbramalison>
Pinmux padconf/iodelay (ti) historically is called from board.c on init. In Linux, this exists in DTS under pmx_core/iodelay_core nodes. I see these constructs in uboot dts files too. Do you know if by putting pinmux into dts I can remove it from board.c?
zkrx has quit [Ping timeout: 256 seconds]
zkrx has joined #u-boot
warpme has joined #u-boot
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme has joined #u-boot
f_ has quit [Quit: To contact me, send a memo using MemoServ, PM f_[xmpp], or send an email. See https://vitali64.duckdns.org/.]
<NishanthMenon>
Tartarus: default is usually with vendor SDK images - at least the boards that do not have complete automated update capabilities (usually the older boards) do not get flashed with upstream u-boot.
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme has joined #u-boot
monstr has joined #u-boot
dsimic has quit [Ping timeout: 240 seconds]
naoki has joined #u-boot
dsimic has joined #u-boot
monstr has quit [Ping timeout: 252 seconds]
schroes_ is now known as schroes__
schroes__ is now known as schroes
mmu_man has joined #u-boot
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme has joined #u-boot
naoki has quit [Quit: naoki]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]