Tartarus changed the topic of #u-boot to: SOURCE MOVED TO https://source.denx.de/u-boot/u-boot.git / U-Boot v2025.04, v2025.07-rc4 are OUT / Merge Window is CLOSED, next branch is OPEN / Release v2025.07 is scheduled for 07 July 2025 / Channel archives at https://libera.irclog.whitequark.org/u-boot
ikarso has quit [Quit: Connection closed for inactivity]
mckoan_ has joined #u-boot
levitating has joined #u-boot
mckoan|away has quit [Ping timeout: 276 seconds]
hanetzer has quit [Ping timeout: 244 seconds]
hanetzer has joined #u-boot
mmu_man has quit [Ping timeout: 252 seconds]
per1cycle has quit [Quit: Ping timeout (120 seconds)]
per1cycle has joined #u-boot
hanetzer has quit [Quit: WeeChat 4.5.2]
clamor has joined #u-boot
monstr has joined #u-boot
naoki has quit [Quit: naoki]
naoki has joined #u-boot
monstr has quit [Ping timeout: 252 seconds]
Fr4nk has joined #u-boot
Fr4nk has quit [Quit: WeeChat 4.6.3]
Fr4nk has joined #u-boot
kiboneu has quit [Remote host closed the connection]
kiboneu has joined #u-boot
K900 has quit [Remote host closed the connection]
Algotech has quit [Ping timeout: 252 seconds]
K900 has joined #u-boot
Algotech has joined #u-boot
monstr has joined #u-boot
mmu_man has joined #u-boot
mmu_man has quit [Ping timeout: 244 seconds]
foxtrot has quit [Quit: Goodbye]
prabhakalad has joined #u-boot
<anshuld> Hello everyone, I posted an RFC on the mailing list regarding the init sequence though I forgot to CC the relevant contributors. If you have some time kindly go over the RFC here: https://lore.kernel.org/u-boot/DAQIYU2LVE61.2K9Z7L7EQ2QQY@ti.com/
<anshuld> Specifically, I was curious why we're doing the TLB size estimate (in arch_reserve_mmu) before dram_init_banksize in the init sequence (common/board.f:893).
catfish03 has quit [Remote host closed the connection]
sszy has joined #u-boot
alperak has joined #u-boot
warpme has joined #u-boot
prabhakalad has quit [Ping timeout: 272 seconds]
clamor has quit [Ping timeout: 248 seconds]
clamor has joined #u-boot
<apalos> anshuld: send the patch as an RFC and CC maintainers,
m5zs7k has quit [Ping timeout: 248 seconds]
m5zs7k has joined #u-boot
mmu_man has joined #u-boot
prabhakalad has joined #u-boot
soxrok2212 has quit [Ping timeout: 245 seconds]
soxrok2212 has joined #u-boot
shadowless has quit [Ping timeout: 252 seconds]
shadowless has joined #u-boot
haritz has joined #u-boot
haritz has quit [Changing host]
haritz has joined #u-boot
<dormito> Hmmm. Does u-boot have "lts" release, or just is regular (quarterly?) release?
<dormito> or to put another way: when picking a reals to use for a board, is just the latest release a good stratagy, or should some releases be prefered over others?
<mkorpershoek> dormito: latest is a good strategy. There are no LTS for U-Boot
<dormito> ok, thanks of the info.
funderscore is now known as f_
<dormito> ah nice
f_ is now known as funderscore
mmu_man has quit [Ping timeout: 260 seconds]
mmu_man has joined #u-boot
monstr has quit [Remote host closed the connection]
goliath has quit [Quit: SIGSEGV]
naoki has quit [Quit: naoki]
dsimic has quit [Ping timeout: 252 seconds]
dsimic has joined #u-boot
anshuld has quit [Quit: Connection closed for inactivity]
funderscore is now known as f_
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
clamor has quit [Ping timeout: 248 seconds]
clamor has joined #u-boot
clamor has quit [Ping timeout: 248 seconds]
sszy has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
<dormito> on the off chance anyone hear has watched the layerspace code: I have a custom lx2160 base board that worked on v2022.04, but rebasing it onto v2025.04 results in linux failing to probe the ethernet DPNI devices with -19
<dormito> anyhow, anyone know of a change that effected the mc networking? (I've been looing throug theh git logs, but nothing pops out)
<Tartarus> Sounds like the kind of thing to bisect where you also have your board support as a single patch to apply at each step
<dormito> yeah, that's probably what I'll have to do
<cambrian_invader> dormito: did you create them in userspace?
<dormito> cambrian_invader: they are setup with a DPL (uboot reports mc, dpc, and dpl are all successfully activated/delpyed before linux starts)
<cambrian_invader> maybe try manually creating the interface
<cambrian_invader> could be a dpl regression
<dormito> yeah, atm, I'm digging up my restool resources
<dormito> Hmmm. manually creating the interfaces with restool seems to hav made linux ethernet device, but the error connecting to the mac still gives -ENODEV (looks like a slightly different kernel message). and of course the interfaces don't actuallt function. bisect time it is I guess
<cambrian_invader> do you get anythin in dmesg?
<cambrian_invader> or /sys/kernel/debug/devices_deferred
<dormito> yeah, it adds the dpbp, the dpcons, then the dpni to iommu grou0, then phylink_fwnode_phy_connect() returns -19, and dpni complains abouti tas an error connecting to thte MAC
<dormito> and nothing in /sys/kernel/debug/devices_deferred
<cambrian_invader> hm, well that looks more like an error connecting to the phy
<cambrian_invader> if you look in e.g. /sys/bus/mdio/devices is the phy there? does it have the right driver or genphy?
<dormito> it's USXGMII PHY, aquantia...oh I wonder if the u-boot settings for aquantia came undone in the update
<dormito> nope, I don't see the phys in /sys/bus/mdio_bus/devices (in case it wasn't a typo, /sys/bus/mdio doesn't exist ion this system)
<dormito> (and for referance, an hour or so ago, I booted this kernel with the 2022.04 u-boot and the interfaces showed up and functioned)
rvalue- has joined #u-boot
<cambrian_invader> sorry, it should be /sys/bus/mdio_bus
rvalue has quit [Ping timeout: 276 seconds]
<cambrian_invader> if you have something like https://github.com/wkz/mdio-tools you can try looking to see if the phys are really absent
<dormito> oh, thats a good idea
<cambrian_invader> and maybe check in /sys/firmware/devicetree/base/ to make sure the MDIO buses have nodes for the phys
rvalue- is now known as rvalue
<dormito> yup the phys exist (and aren't disabled)
<dormito> *in the device tree
<cambrian_invader> hm, maybe the mdio bus had a problem?
<cambrian_invader> if the mdio bus was probed then you should see devices for the phys
___nick___ has joined #u-boot
<dormito> yeah. it's weird that linux is apparently dependant on u-boot for that.
vagrantc has joined #u-boot
___nick___ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
___nick___ has joined #u-boot
absc has joined #u-boot
hanetzer has joined #u-boot
___nick___ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
___nick___ has joined #u-boot
___nick___ has quit [Client Quit]
___nick___ has joined #u-boot
teejay has quit [Ping timeout: 260 seconds]
teejay_ has joined #u-boot
clamor has joined #u-boot
clamor has quit [Read error: Connection reset by peer]
absc has quit [Remote host closed the connection]