dgilmore changed the topic of #fedora-riscv to: Fedora on RISC-V https://fedoraproject.org/wiki/Architectures/RISC-V || Logs: https://libera.irclog.whitequark.org/fedora-riscv || Alt Arch discussions are welcome in #fedora-alt-arches
guerby has joined #fedora-riscv
Valeria22 has quit [Quit: Konversation terminated!]
davidlt has joined #fedora-riscv
<davidlt> and new disk image is cooking!
<davidlt> binutils 2.41 landed (thanks Nick!)
<davidlt> Time to prep a new GCC 13 build
<davidlt> conchuod, there is a new JH7110 PCIe patch version from Minda.
<davidlt> It looks like v4 is somewhat a minimal change from v3.
<conchuod> Yeah, was addressing a couple bits that I pointed out on v3
<davidlt> bindings seem to be approved too
<davidlt> it might be safe for me to pull this on top of v6.6 kernel
<conchuod> Yeah, I was happy with those on v2 maybe. Certainly last version I was.
<conchuod> I haven't looked at v4 yet, but I don't think either Bjorn or Lorenzo reviewed the v3.
<conchuod> So I doubt that stuff makes 6.6 given the window probably opens next week, but ye I figure it'll be safe for you to do so.
<davidlt> It's probably 3-4 weeks before I try to boot v6.6, that's probably enough for this to get fully approved.
<conchuod> Hopefully.
<davidlt> I want to try jumping into early RC testing this time
<davidlt> v6.5 was a bit problematic
<conchuod> Ye, v6.5 has been pretty messy so far.
<conchuod> This last minute ptrace stuff for vector & the various broken boot things.
<conchuod> I hope not all that much gets picked up for 6.6 since it's so late in cycle & there'd be little linux-next exposure.
<davidlt> It depends on the maintainer. Some really like to cook things in linux-next for a long time.
<davidlt> I would say on RISCV side we tend to pull things quite late, but maybe I am wrong.
<conchuod> I like things that affect me to be in linux-next before the merge window :)
<davidlt> Yeah, but most folks will start testing once there is RC1 (typically a bit later)
<davidlt> Usually things after ~RC4 are stable, new things can still land until RC2.
<conchuod> That's not relevant
<conchuod> There are people & automation that test next, applying things late or not having a tree in next skips that initial phase.
<conchuod> Whether there is another group that tests RCs doesn't really matter, but waiting til then to do any testing at all only decreases the time to fix stuff.
<davidlt> Sure, it's just starting RC cycle the testing expands.
zsun has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
<dgilmore> davidlt: is there a recommended image for the FV2?
zsun has quit [Quit: Leaving.]
<davidlt> dgilmore, not until v6.6-rc shows up
<dgilmore> okay
<djdelorie> davidlt: dead power supply. I'll have to scrounge for another one
<davidlt> djdelorie, ok
davidlt has quit [Remote host closed the connection]
davidlt has joined #fedora-riscv
davidlt has quit [Ping timeout: 245 seconds]