Posts
461
Following
145
Followers
149
The cat is not mine :(

I like cycling, powerlifting, bad video games and metal.
Otherwise, I occupy my time with various bits in RISC-V land.

~useless, placeholder, website: https://www.conchuod.ie/
Good ole DJ Church killing it at hooker today :)
0
0
0
@llvm I'm far from suggesting that the tags be removed, it's more a question for me of wonder what the tag has been given for?
"I don't know how to apply meaning to them" rather than "these tags are useless and should be removed"?
0
0
0
@llvm How is one supposed to know that, and assign appropriate value to the tag, if they do not provide review comments publicly?
0
0
0
@broonie I guess my point was that if the tag is given on the list, you "know" that it's been given for the version that was posted. If it comes from inside an SoC vendor, it may not have been.
1
0
0
@broonie by old do you mean vN-1, or something from some time ago?
If it's the former, at least one can tell what got the tag.
When it's internal, from someone who is not active in a mailing list, it's hard to assign any meaning.
1
0
0
Sending out patches with internal reviewed by tags seems so meaningless to me.
I've never seen these people before, what do their tags mean?
1
0
1
What that treesitter doin'?
0
0
0
https://www.jeffgeerling.com/blog/2023/risc-v-business-testing-starfives-visionfive-2-sbc

Interesting post from @geerlingguy about the visionfive2, but also a bit of a reflection on the RISC-V software ecosystem in general.
0
2
2
@monsieuricon @ljs @monsieuricon working with gmail message-ids has a different problem. In my inbox, I get the message-id "CAK9=C2Uy_0B6D2TGq35sfrGkp9s1Td=cEsidzDPTDhG7Nq5EWw@mail.gmail.com" but the mbox file created by b4 is "CAK9_C2Uy_0B6D2TGq35sfrGkp9s1Td_cEsidzDPTDhG7Nq5EWw@mail.gmail.com.mbx".
Not a big deal, but frequently trips me up!
0
0
1
@ljs @monsieuricon Jokes aside, part of me really wants to submit patches as "Conchubhar O'Dubhlaigh" instead of "Conor Dooley" (both are acceptable under the former wording) but but it'd just cause confusion...
0
0
1
@monsieuricon Interesting post, thanks.

So, submitting a patch with "Signed-off-by: Eagle <eagle@small-medium-company.com>" wouldthen okay, as the IT dept. of small-medium-company could verify it.
Similarly, Marcan could verify that Lina is Lina if something came to pass there.
But $unknown-contributor submits something under their online alias should still be challenged?
0
0
0
Huh, probably wouldn't have known about this had it not appeared here:
https://social.treehouse.systems/@fox/109938758111808053

Certainly nice for the Lina's of the world, but I wonder how far "known identity" goes. "If I google it, I'll find them"?
1
0
1
@marcan If the maintainers are AWOL, they should be removed from MAINTAINERS , as they're not exactly maintaining anything /shrug
0
0
6
@bagder Simon Stalenhag is fantastic!
0
0
1
https://noc.social/@phoronix/109927186270858469

hah, love the unmatched photo! Better off with a picture of the VisionFive 2 that actually supports the extension ;)
0
0
1
Edited 1 year ago
My venerable VG248QE had its display port die this week, so not the best of fortunes for my hardware lately!
1
0
0
Edited 1 year ago
Think I fell victim to a dead Samsung 980 overnight:/

Didn't have the firmware version that's supposedly bad, but system died overnight. Boot was getting stuck decrypting LUKS & now can't even reinstall from a livecd :)
1
0
1
With v6.2 being released the other day, I did a bit of a recap to remind myself of what actually
landed this time around for RISC-V. Figured I may as well share it /shrug

With the V2 on the horizon, Cristian Ciocaltea added the VisionFive v1 DT, which has been a long
time coming! Unfortunately, that platform is still not really supported in mainline and may never
get there given it's reliance on non-coherent DMA that is yet to be supported.
He did post some of the out of tree non-coherent dma patches on the list the other day though, and
while that's unlikely to land anytime soon, I hope it gets there eventually :)

Renesas finally joined the RISC-V party for v6.2, with Geert's PR adding the base DT for the
RZ/Five. This platform *also* relies on non-coherent DMA to be fully supported, but that is
currently a work in progress! That work was done by Lab Prabhakar from Renesas.


Palmer's PR is where the actually interesting stuff happens though...
Binglei Wang added support for rethooks, after a rough start with mailer issues!
Drew Jones, while not reviewing, worked on some nice cleanups to alternatives and extension
handling.
Anup got one of his many new-feature support series over the line for PMEM support.
The T-Head c9xx series cores got support for their non-standard PMU variant upstream thanks to
Heiko who has been somewhat of a champion for that platform.
RV32, not to be left out, landed support for dynamic ftrace. That work was carried out by Jamie
Iles, who, as the 32-bit bpf maintainer, clearly has an interest in that part of the arch.
Support for zstd compressed images gained support also, thanks to the work of Jisheng Zhang.
Tong Tiangen extended support for hugepages, Xianting Tian got the remainder of their
VMCOREINFO series over the line & Lui Shixin got HUGE\_VMA{P,LLOC} support enabled.
Jinyu Tang brought in support for updating the tlb & Hal Feng put the finishing touch on the base
support for the VisionFive v1 by added the serial driver for it.
Notable also is a patch from Cleo John, tidying up some styling, as it was their first :)

A whole bunch of others contributed various bits of cleanup and fixes that landed in the v6.2, PR
and for more on those check out the changelog in Palmer's PR:
https://lore.kernel.org/linux-riscv/mhng-f76eb33c-7cc1-426f-8f29-37f6bb78baec@palmer-ri-x1c9/

There were also 4 fixes PRs sent out over the course of the merge window, however none of these
really contained anything particularly significant. A lot of attention recently has been centred
around text patching, so it is no surprise that a number of the fixes are there too, with, out of
the 16 total patches in -fixes, 5 were in this area. Other than that, we had a good few general
correctness bits, for sparse warnings etc
1
11
8
@ecurtin @llvm @marcan I played around with it some more & it keeps "doing the wrong thing" to the point that I didn't feel I could commit it.
I *think* I'll align the files that I'm responsible for to .clang-format & just run it myself as cleanup in merge commits.
0
0
0
Show older