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
dominic- has joined #u-boot
Algotech has quit [Ping timeout: 276 seconds]
Algotech has joined #u-boot
prabhakalad has quit [Ping timeout: 252 seconds]
prabhakalad has joined #u-boot
mtoy has quit [Read error: Connection reset by peer]
mtoy has joined #u-boot
jfsimon has quit [Remote host closed the connection]
jfsimon has joined #u-boot
clamor has joined #u-boot
vagrantc_ has quit [Quit: leaving]
swiftgeek has quit [Ping timeout: 260 seconds]
swiftgeek has joined #u-boot
swiftgeek has quit [Ping timeout: 272 seconds]
sakman has joined #u-boot
swiftgeek has joined #u-boot
<shadows> zen_desu: hi
<zen_desu> hi
<shadows> zen_desu: you may refer to the long explanation in cover leter for my series sent to LKML https://lore.kernel.org/lkml/20250502103101.957016-1-e@freeshell.de/
<shadows> short version is don't do that; boot SPI NOR flash mode of JH7110 into U-Boot and use the EFI support there to seek an EFI System Partition on your eMMC.... if possible.
<shadows> long version is that the method used by JH7110 eMMC boot mode "apparently" (I did not research any source or reverse-engineering effort for the zeroth-boot-loader in MaskROM) has some scheme which is incompatible to a GUID Partition Table data structure
<shadows> I spent about two solid days faffing around with it and decided that was as far as I could get without reverse engineering the MaskROM content
<zen_desu> yeah at the time being im getting my head wrapped around the sd booting stuff
<zen_desu> just because i don't want to trash the onboard spi
<shadows> you have serial UART cable? don't worry about bricking the vf2. It's robust, you can always recover it.
<zen_desu> i kinda don't see the point in using GPT for SPLs tho, i guess it works, i'd prefer just using some offset on the storage device
<zen_desu> ok cool, thanks for that
<zen_desu> i've been updating this
<zen_desu> i'd appreciate a second look :D but i have not double checked this info on the reflash process
<zen_desu> https://wiki.gentoo.org/wiki/StarFive_VisionFive_2#SPI_issues_.2F_First_aid_kit i mvoed it here, and it seems simple enough, i;ve used xmodem before
<shadows> that's great! :) more documentation equals "more better" :D
<zen_desu> yeah i agree, i may make a uboot wiki account to change that bit on FW_TEXT_START=0x40000000 FW_OPTIONS=0
<zen_desu> it may be that you needed that on older versions? idk, setting that made it just not work for me
<shadows> ohhh... docs on wiki are generated from the source tree in ".rst" restructured-text format
<zen_desu> ah so it would just be done through a PR to the main source repo?
<shadows> I think Heinrich (xypron) was going to streamline the JH7110 docs a bit, or already has done so... it needs a little bit more tidying up to kind of unify everything and less duplication of common procedures
<shadows> yep all done via git
<zen_desu> i may look into it, you maybe pinged them so hopefully they can fix that bit or maybe explain it to me
<shadows> plus patches to the U-Boot Mailing list. There's some github"-ish" usage by the custodians for certain areas of code but at the end of it they're pulling from mail list patches and then submitting on mail list a request to U-Boot project leader to pull from those custodian branches
<zen_desu> I've gone this long without submitting patches via email but maybe eventually that will change lol
<shadows> oh... yeah, I set up one of the free linux public access shell accounts I'd had for some time just for this kind of developer mail list stuff. It was a couple of weeks for an old guy like me to wrap my mind around that.
<shadows> zen_desu: have a look at this table / identification guide I put together, as well https://freeshell.de/e/riscv64/vf2eeprom/
<zen_desu> ohhh that's nice
<zen_desu> i may add that to the see also bit
<zen_desu> what doe sa checkmark really mean?
<shadows> for example there was a hack at some point to extend Milk-V Mars devicetree at runtime and fix it up in-place in memory after loading so that the Mars CM and Mars CM Lite would function; but that all went away later when upstream Linux devicetree became de facto (and there's not yet any Mars CM or Mars CM Lite devicetree in upstream Linux)
<shadows> [nothing,checkmark,cross] to mean not present, present and functional, formerly present but now absent or not functional
<shadows> zen_desu: browse over https://github.com/geerlingguy/sbc-reviews/issues/22#issuecomment-1908676618 and pick out the parts you find interesting, it is some github issue comment tracking the Milk-V Mars CM for a YouTube content creator's list of SBC's and though now it's a bit stale I was updating the comment frequently
<shadows> for chat on topic of JH7110 that is not strictly about U-Boot also welcome to participate in the Pine64 Star64 room (which I access via Matrix; I think it's also there via other platforms) https://pine64.org/community/#chat-platforms
<zen_desu> thanks for that, i think i will try that in a bit
persmule has quit [Remote host closed the connection]
vagrantc has quit [Quit: leaving]
monstr has joined #u-boot
monstr has quit [Ping timeout: 252 seconds]
clamor has quit [Ping timeout: 248 seconds]
goliath has joined #u-boot
clamor has joined #u-boot
apalos has quit [Read error: Connection reset by peer]
Guest854 has quit [Read error: Connection reset by peer]
kathirav has quit [Read error: Connection reset by peer]
kathirav has joined #u-boot
Guest854 has joined #u-boot
mtoy has quit [Read error: Connection reset by peer]
apalos has joined #u-boot
mtoy has joined #u-boot
gsz has joined #u-boot
monstr has joined #u-boot
rvalue- has joined #u-boot
rvalue has quit [Ping timeout: 260 seconds]
naoki has joined #u-boot
rvalue- is now known as rvalue
rvalue- has joined #u-boot
rvalue has quit [Ping timeout: 276 seconds]
rvalue- is now known as rvalue
gsz has quit [Ping timeout: 265 seconds]
ldevulder has joined #u-boot
mripard has joined #u-boot
gsz has joined #u-boot
alperak has joined #u-boot
persmule has joined #u-boot
monstr has quit [Ping timeout: 252 seconds]
LainIwakura has joined #u-boot
Poltawer has joined #u-boot
monstr has joined #u-boot
sszy has joined #u-boot
monstr has quit [Ping timeout: 252 seconds]
monstr has joined #u-boot
bjoto has quit [Remote host closed the connection]
gsz has quit [Ping timeout: 245 seconds]
LainIwakura has quit [Quit: Client closed]
persmule has quit [Quit: Leaving]
xroumegue has quit [Ping timeout: 248 seconds]
persmule has joined #u-boot
gsz has joined #u-boot
xroumegue has joined #u-boot
jclsn has joined #u-boot
naoki has quit [Quit: naoki]
Poltawer has quit [Quit: WeeChat 4.6.3]
LainIwakura has joined #u-boot
warpme has joined #u-boot
delovoilemon has joined #u-boot
LainIwakura has quit [Ping timeout: 272 seconds]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
bjoto has joined #u-boot
wooosaiiii has quit [Remote host closed the connection]
wooosaiiii has joined #u-boot
wooosaiiii has quit [Remote host closed the connection]
wooosaiiii has joined #u-boot
clamor has quit [Ping timeout: 276 seconds]
clamor has joined #u-boot
goliath has quit [Quit: SIGSEGV]
<Tartarus> Community call at the top of the hour
<Tartarus> ... now
ldevulder has quit [Ping timeout: 248 seconds]
RoganDawes has joined #u-boot
ldevulder has joined #u-boot
delovoilemon has quit [Quit: delovoilemon]
delovoilemon has joined #u-boot
<Tartarus> Hmmmm, I wonder if https://repost.aws/knowledge-center/free-tier-windows-instance would be enough to allow us to have a gitlab runner on Windows and in turn also do the Windows host tools build there and not only in Azure
<Tartarus> (The stm32 PR I just got breaks only on Windows hosts, which is harder to test due to being only in Azure)
clamor has quit [Ping timeout: 248 seconds]
monstr has quit [Remote host closed the connection]
goliath has joined #u-boot
dsimic has quit [Ping timeout: 252 seconds]
dsimic has joined #u-boot
Poltawer has joined #u-boot
warpme has joined #u-boot
sszy has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
ldevulder has quit [Ping timeout: 276 seconds]
macromorgan has quit [Ping timeout: 248 seconds]
macromorgan has joined #u-boot
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
mripard has quit [Quit: WeeChat 4.6.3]
delovoilemon has quit [Quit: delovoilemon]
teejay_ has joined #u-boot
teejay has quit [Ping timeout: 265 seconds]
goliath has quit [Quit: SIGSEGV]
jfsimon has quit [Quit: Leaving]
jfsimon has joined #u-boot
K900 has quit [Remote host closed the connection]
K900 has joined #u-boot
gsz has quit [Ping timeout: 276 seconds]
goliath has joined #u-boot
RoganDawes has quit [Ping timeout: 272 seconds]
jfsimon has quit [Remote host closed the connection]
jfsimon has joined #u-boot
mmu_man has joined #u-boot
Poltawer has quit [Quit: WeeChat 4.6.3]
mmu_man has quit [Ping timeout: 276 seconds]
mmu_man has joined #u-boot