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/

@vegard @marcan @CyReVolt @lschuermann @monsieuricon imho, anyone who's getting into kernel development or who is open to changing their workflow should use b4 right away and avoid using git-send-email

https://b4.docs.kernel.org/en/latest

1
6
1
@janne @hrw probably cos of
git log --oneline --no-merges Documentation/devicetree/bindings/arm/cpus.yaml
...
355d090ecbbc dt-bindings: arm: cpus: Add apple,avalanche & blizzard compatibles
0
0
2
@jarkko @gregkh just to note, it does not have to be part of OpenSBI. It just needs to be a frozen SBI extension. OpenSBI is but one one SBI implementation, and being part of it is not a requirement for patch acceptance.
1
0
1
"Detection of individual cryptography extensions uses the unified software-based RISC-V discovery method.

 At the time of writing, these discovery mechanisms are still a work in progress."

...from the documentation for ratified extensions :)
1
0
4
@sima @nicofee @marcan @nicolas17 unfortunately I know how things work for dt-bindings, and drag may be an apt word ;)
0
0
1
@sima @nicofee @marcan @nicolas17 it'd be nice of the email fallback was automated via get_maintainer and hooked into a b4-relay type thing, so that contributors don't need to give a shit about what is and what isn't cross forge.

Also, since I'm not a DRM contributor, is drm-misc where the dt based stuff for arm etc ends up? That's probably quite a big chunk of where your cross subsystem/forge stuff is, given there's very often bindings & devicetree changes mixed in with drivers?
1
0
1
@marcan @nicofee @nicolas17 @sima (and this isn't some antagonistic questioning shit, I actually want to know how that's going to work)
1
0
1
If there was some tool that gave me my review queue from a forge as something I can handle via my editor & synced my responses, I'd overwhelmingly rather use that than email.
0
0
0
@marcan @sima @nicofee @nicolas17 What I mean is, if you have some changes that affect both drivers/soc/apple and, idk, drivers/dma, how do you interact with the relevant maintainers for that code?
1
0
0
That said, forge ci integration is so so much better. I hate all the hoops that must be jumped through for patch-based CI...
1
0
1
I see today is iteration N of hating email based workflows. My 0.02 € is that I hate both, clunky aul email and clunky new UIs :)
1
0
2
@sima @nicofee @marcan @nicolas17 If you switch to those, how would you interact with the rest of the kernel?
1
0
1
@sima @nicolas17 @nicofee @marcan what would you mean by non mail based tooling?
1
0
0
@jarkko cos of the experimental SBI extension? FWIW, the patch acceptance policy for standard extensions is that you either need to be a frozen extension from RVI or actually available to people for vendor stuff. See
<https://docs.kernel.org/riscv/patch-acceptance.html#submit-checklist-addendum>.

I don't know which of the two your keystone work is intended to be though.
1
0
0
@jarkko I don't think any of those things preclude being in drivers/firmware.
1
0
0
@xahteiwi in a development context, that emote has no meaning to me.
0
0
1
@jarkko kinda random thought of no real merit at this stage of your develop, why's the code in arch/riscv? It seems as if it would be better off in drivers/firmware?
Obv. that doesn't matter at this remove, since you're using experimental SBI extension IDs etc so nothing here is mergeable, but I am curious :)
1
0
0
0
0
1

I'm extremely reluctant to pass much comment on the Israel/Gaza situation because I grew up in an occupied territory where terrorists frequently targeted civilians and arguably the terrorism eventually resulted in a negotiated peace with a vaguely functioning power sharing arrangement, and I do not want that to be the moral of the story

1
1
2
@asb @jangray Zidgaf is going to be my extension.
0
1
2
Show older