Posts
464
Following
144
Followers
150
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/
@llvm @marcan

How to **help** them stay idiosyncratic??? I need to go watch that.
1
0
0
@marcan @ljs I meant anonymising the submission process of a particular subsystems "quirks". Sorry if I was not clear.
0
0
0
@marcan @ljs

You gonna anonymise submissions for that list? Might have one or two suggestions sadly.
0
0
0
I hope I do manage not to come across as an asshole.
0
0
0
I guess since there is no quote retweet here,
https://social.kernel.org/notice/ARLXuuUYGeIWtYMHbs

>every new contributor has to build that list from scratch and suffer until they figured it out.

Whenever I write something critical I think of one of the reviews I received early on, for something that was admittedly sub-par, and hope not to come across the way that email did.
0
0
4
@bjorntopel I found out that the Monday after is a new bank holiday here.. I suppose I shall see you there :)
0
0
0
@nathanchance "developers will introduce [-Wmaybe-uninitialized] inadvertently and not realize it because GCC never told them about it" tbh stuff like this made me swap to clang-by-default. Got sick of lkp complaining about stuff that gcc missed.
0
0
2
@pdp7 My PWM driver is at v13 or something. Granted v1 was something I wrote before my first driver was even upstream - but god have I made mistakes...
0
0
1
@gmarkall Ah cool. I've always found apt & dnf/yum to do take *forever*, but my arm64 stuff uses pacman so I have never compared the two.
0
0
0
Heh, this would've been nice to have attended year ago:
https://fosdem.org/2023/schedule/event/pwm/

"The audience learns the general concept of PWMs, about the corner cases in their usage and driver design, and how to avoid the common pitfalls often pointed out to authors of new PWM drivers during the review process."
0
1
1
@gmarkall s/stuff ship works/stuff works for the config they ship/
0
0
0
@gmarkall You running mainline + patches, or the tree they ship? Either way, yell if something that should work doesn't? I figure stuff ship works for but probably hasn't see diverse use.
They sent me over some docs, so I was able to look a bit more closely at the power management unit patchset - there's not a lot of drivers to compare against there so that one is mainly what worried me.
1
0
0
@gmarkall Ahh, figured. My internal gauge of LLVM build times comes from running https://github.com/ClangBuiltLinux/tc-build/build-llvm.py which builds all archs by default. 2 hours (with headroom to improve) for the single target build sounds promising in terms of being able to do native building of things.
0
0
0
@gmarkall Out of curiosity, are you only building llvm for riscv?
0
0
0
There were in fact 4 people.
0
0
0
Nearly done with the ~90 minutes, there may be fact be 4 people on this podcast? There were 4 names used & I am now more confused than I was at the start!
1
0
0
35 mins in, listening as I do other things, I could not match the voices to the names of the 3 people in this podcast.
1
0
0
This particular podcast is not helped by presumptions of knowledge about the "who & what" of the topic. In comparison, I quite like the Brad Shoemake/Will Smith FOSS podcast as they a great job introducing the technology/guest before bringing them in.
1
0
0
It's doubly bad for my awful attention span that *requires* consuming content at 1.5x or higher speed.
1
0
0
Listening to a podcast for the first time, where the hosts do not introduce themselves before bringing in their guest is *super* disconcerting.
Now I got 3 voices that I cannot tell apart, rather than having some time to acclimatise to the hosts...
1
0
1
Show older