rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
naoki has joined #u-boot
Stat_headcrabbed has joined #u-boot
monstr has joined #u-boot
guest96 has joined #u-boot
naoki has quit [Ping timeout: 248 seconds]
naoki has joined #u-boot
naoki has quit [Ping timeout: 260 seconds]
naoki has joined #u-boot
naoki has quit [Read error: Connection reset by peer]
naoki has joined #u-boot
ldevulder has joined #u-boot
naoki has quit [Client Quit]
naoki1 has joined #u-boot
ldevulder has quit [Client Quit]
persmule has quit [Remote host closed the connection]
naoki1 is now known as naoki
ldevulder has joined #u-boot
guest96 has quit [Quit: Client closed]
mckoan|away is now known as mckoan
joeskb7 has quit [Remote host closed the connection]
joeskb7 has joined #u-boot
gsz has joined #u-boot
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
rockosov has quit [Ping timeout: 252 seconds]
rockosov has joined #u-boot
xroumegue has quit [Ping timeout: 246 seconds]
dsimic has quit [Ping timeout: 252 seconds]
Giedrius has joined #u-boot
dsimic has joined #u-boot
<Giedrius>
hello, hopefully quick question - I'm developing for an STM32MP135 processor, and have a question on GPIO pin configuration persistence throughout boot stages - I've changed the UART4 RX pin to an alternative location in U-Boot DT configuration, but it looks like the old location (from earlier boot stage?) was still configured in the GPIO
<Giedrius>
registers, therefore taking priority over my change (maybe because the original pin's bank is lower numbered)
<Giedrius>
is there some guidelines for whether GPIO registers are supposed to be reset before entering the next stage of booting, or are they supposed to be left at their last state when handing over the control down the line?
ex-parrot has quit [Quit: _b]
ex-parrot has joined #u-boot
xroumegue has joined #u-boot
mmu_man has joined #u-boot
gsz has quit [Ping timeout: 252 seconds]
la_mettrie has joined #u-boot
<la_mettrie>
is there a handy way to see clock rates or do i have to modify the source?
<samcday>
CONFIG_CMD_CLK
<samcday>
It requires the clock driver for your particular device to implement the clk_ops.dump func though
<Giedrius>
I found a dts file I hadn't updated for my board in optee-os. I'm now aware of these locations containing .dts files: tf-a, optee-os, u-boot, linux. Can I be missing anything else?
Giedrius has quit [Quit: Client closed]
Giedrius has joined #u-boot
ikarso has joined #u-boot
Guest64 has joined #u-boot
Guest64 has quit [Client Quit]
Guest94 has joined #u-boot
Guest94 has quit [Client Quit]
Guest64 has joined #u-boot
<apalos>
anyone remembers if rpi5 has ethernet support?
Guest64 has quit [Quit: Client closed]
Giedrius has quit [Quit: Client closed]
naoki has quit [Quit: naoki]
goliath has joined #u-boot
naoki has joined #u-boot
frytaped has quit [Ping timeout: 252 seconds]
mmu_man has quit [Ping timeout: 252 seconds]
mmu_man has joined #u-boot
ikarso has quit [Quit: Connection closed for inactivity]
totkeks has joined #u-boot
naoki has quit [Quit: naoki]
tec4 has quit [Quit: bye!]
tec4 has joined #u-boot
Stat_headcrabbed has quit [Quit: Stat_headcrabbed]
persmule has joined #u-boot
mmu_man has quit [Ping timeout: 245 seconds]
monstr has quit [Remote host closed the connection]
gsz has joined #u-boot
totkeks has quit [Ping timeout: 260 seconds]
ikarso has joined #u-boot
mckoan is now known as mckoan|away
vardhan has joined #u-boot
vardhan_ has joined #u-boot
vardhan has quit [Read error: Connection reset by peer]