Tartarus changed the topic of #u-boot to: SOURCE MOVED TO https://source.denx.de/u-boot/u-boot.git / U-Boot v2025.01, v2025.04-rc3 are OUT / Merge Window is CLOSED, next branch is OPEN / Release v2025.04 is scheduled for 07 April 2025 / Channel archives at https://libera.irclog.whitequark.org/u-boot
naoki has quit [Ping timeout: 260 seconds]
naoki has joined #u-boot
naoki has quit [Remote host closed the connection]
naoki has joined #u-boot
naoki has quit [Ping timeout: 260 seconds]
naoki has joined #u-boot
naoki has quit [Ping timeout: 260 seconds]
naoki has joined #u-boot
mmu_man has quit [Ping timeout: 244 seconds]
Daanct12 has joined #u-boot
zibolo has quit [Ping timeout: 246 seconds]
zibolo has joined #u-boot
naoki has quit [Remote host closed the connection]
naoki has joined #u-boot
naoki has quit [Ping timeout: 268 seconds]
naoki has joined #u-boot
naoki has quit [Remote host closed the connection]
naoki has joined #u-boot
goliath has quit [Quit: SIGSEGV]
Jones42 has quit [Ping timeout: 244 seconds]
Jones42 has joined #u-boot
naoki has quit [Quit: naoki]
naoki1 has joined #u-boot
naoki1 is now known as naoki
jclsn has quit [Ping timeout: 272 seconds]
vfazio__ has quit [Remote host closed the connection]
jclsn has joined #u-boot
haritz is now known as saimazoon
rvalue has quit [Ping timeout: 265 seconds]
joeskb7 has quit [Ping timeout: 260 seconds]
rvalue has joined #u-boot
naoki has quit [Quit: naoki]
teejay_ has quit [Quit: leaving]
dsimic has quit [Ping timeout: 272 seconds]
dsimic has joined #u-boot
vagrantc has quit [Quit: leaving]
persmule has quit [Remote host closed the connection]
prabhakalad has quit [Quit: Konversation terminated!]
prabhakalad has joined #u-boot
Stat_headcrabbed has joined #u-boot
Stat_headcrabbed has quit [Client Quit]
Stat_headcrabbed has joined #u-boot
clamor has joined #u-boot
joeskb7 has joined #u-boot
Stat_headcrabbed has quit [Quit: Stat_headcrabbed]
Stat_headcrabbed has joined #u-boot
Stat_headcrabbed has quit [Quit: Stat_headcrabbed]
Stat_headcrabbed has joined #u-boot
<Jones42> regarding "read"ing a fitimage from a raw partition into memory: since there is no file system, is there a way to determine the size of the fitimage, i.e. how many blocks I should read?
<Jones42> Or do people just read the whole partition into memory to be safe?
mmu_man has joined #u-boot
naoki has joined #u-boot
rber|res has quit [Quit: Leaving]
ikarso has quit [Quit: Connection closed for inactivity]
warpme has joined #u-boot
naoki has quit [Quit: naoki]
naoki has joined #u-boot
goliath has joined #u-boot
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
clamor has quit [Ping timeout: 248 seconds]
clamor has joined #u-boot
rvalue has quit [Ping timeout: 246 seconds]
persmule has joined #u-boot
rvalue has joined #u-boot
goliath has quit [Quit: SIGSEGV]
warpme has joined #u-boot
Daanct12 has quit [Quit: WeeChat 4.5.2]
f_[x] has joined #u-boot
<Tartarus> It's best to read the partition, yes
Stat_headcrabbed has quit [Quit: Stat_headcrabbed]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
goliath has joined #u-boot
Stat_headcrabbed has joined #u-boot
naoki has quit [Quit: naoki]
Stat_headcrabbed has quit [Quit: Stat_headcrabbed]
Stat_headcrabbed has joined #u-boot
sakman has quit [Read error: Connection reset by peer]
sakman has joined #u-boot
MyNetAz has quit [Remote host closed the connection]
Stat_headcrabbed has quit [Remote host closed the connection]
MyNetAz has joined #u-boot
prabhakalad has quit [Quit: Konversation terminated!]
ikarso has joined #u-boot
prabhakalad has joined #u-boot
Stat_headcrabbed has joined #u-boot
enok has joined #u-boot
enok has joined #u-boot
enok has quit [Read error: Connection reset by peer]
<clamor> Tartarus: hello! Do you mind if I organize sandbox adjustment along with of graph and video bridge into one pull request? Once sandbox changes are approved of course.
Stat_headcrabbed has quit [Quit: Stat_headcrabbed]
Han50lo85 has joined #u-boot
Han50lo85 has quit [Quit: Han50lo85]
goliath has quit [Quit: SIGSEGV]
<Tartarus> clamor: That sounds good, thanks
<clamor> Tartarus: awesome. Thank you
<dormito> I'm working with the nxp_fspi driver, trying to get it to work with the i.mxrt1170. I noticed however that it has chipset specific info for the lx2160, so I looked at it's referance manual: The lx2160 has 1KiB FIFOs for both the IP RX, and IP TX fifos.. but the u-boot driver data has 512/1024 for the driver data. Anyone know if this is a mistake, or is there a reason it diverges from the RM?
<marex> dormito: maybe u-boot uses half of the fifo for RX and half for TX ?
<marex> git log -p on that driver does indicate nothing ?
clamor has quit [Ping timeout: 244 seconds]
clamor has joined #u-boot
goliath has joined #u-boot
<dormito> hmmm. looks like the driver was pulled from linux in that state... maybe the linux git logs have more info
<marex> apalos: is Jerome around here ?
<marex> dormito: yes
<dormito> Hmm... seems like its first upstream linux commit had it that way too. But looking at the i.mx8 RM, I think the lex2160 data was copied from it (during initial dev), and then never updated.
<marex> dormito: could it be that the 512 is there due to SPI being full duplex ?
<marex> i.e. 512 bytes go out, and at the same time, 512 bytes go in ?
<marex> half fifo for TX, half for simultaneous RX ?
<dormito> I'm still learning about the hw (mostly was thinking this would be a "wire up the device tree" thing), but I read the RM to be indicating there is both a RX fifo, and a TX fifo. Different RMs have thing as being different sizes: e.g. lx2160 has 1024 bytes for both, but one of the i.mx8 series has rx=512,tx=1024
<dormito> so I don't think it's a software division of the fifo size
<marex> dormito: ask the kernel driver author whether there is a bug then ?
<dormito> yeah probably a good idea... it was an @nxp.com email... so they better be able to figure it out. lol
<marex> :)
<apalos> marex: no i dont think he is
clamor has quit [Ping timeout: 268 seconds]
g5pw has quit [Quit: leaving...]
g5pw has joined #u-boot
vagrantc has joined #u-boot
Forty-Bot has quit [Remote host closed the connection]