<duskwuff[m]>
Any interest at this time in enhancements to the memory-25x applet? Particularly interested in adding support for 4-byte addressing to handle 32MB+ devices
whitequark[m] has joined #glasgow
<whitequark[m]>
that seems fine, I'm about to replace the underlying engine of memory-25x with QSPI but that shouldn't clash
<whitequark[m]>
since the SPI/QSPI interfaces have been already unified (QSPI is in a branch for now, but not for too long)
<whitequark[m]>
ideally we'd also automatically initialize parameters like that from SFDP, but for now please make it just an argument
<whitequark[m]>
and maybe then we could work autodetection from SFDP
<duskwuff[m]>
Hmm, it'd almost be easier to autodetect from SFDP to begin with. I already know where it is in the parameter table (dword 16, bits 31:14), and it specifies a couple of different ways to handle 32-bit addresses
<whitequark[m]>
that won't work for devices without SFDP
<whitequark[m]>
also, we already have an SFDP parser, no need to mess with dwords
<whitequark[m]>
(also it'd be rather odd to detect addressing mode but not things like page size from SFDP)
<duskwuff[m]>
oh, I see, it isn't using the SFDP parser for anything but ID yet - got it
<whitequark[m]>
the devices without SFDP are not that uncommon
jstein has quit [Ping timeout: 248 seconds]
redstarcomrade has quit [Read error: Connection reset by peer]
<duskwuff[m]>
well here's a stab at it, I'm not super happy with the way the addressing mode gets plumbed through to Memory25xInterface but it works on my test device - https://github.com/GlasgowEmbedded/glasgow/pull/666
abby has joined #glasgow
jstein has joined #glasgow
Eli2_ has joined #glasgow
Eli2 has quit [Ping timeout: 252 seconds]
jstein has quit [Ping timeout: 252 seconds]
<whitequark[m]>
duskwuff (@_discord_237471182566195201:catircservices.org) ah nice! I'll leave feedback in the PR