Jarkko Sakkinen
Posts
4097Following
278Followers
425Entrepreneur at Siltakatu Solutions Oy
OpenPGP: 3AB05486C7752FE1
Jarkko Sakkinen
jarkko
One thing is sure: not travelling to US during this term for any reason. Too much chaos and mayhem. Should be listed high-risk countries to travel into.
3
0
7
Jarkko Sakkinen
jarkko
Promoted GSoC in Finnish because it is factors better investment for future than a regular summer job or some nonsense like that:
https://bsky.app/profile/jarkk0.bsky.social/post/3lh4bzrttac2b
Google is doing the right thing with this and giving back IMHO. Credit given where it is due ;-)
#Google #GSoC #Finnish
https://bsky.app/profile/jarkk0.bsky.social/post/3lh4bzrttac2b
Google is doing the right thing with this and giving back IMHO. Credit given where it is due ;-)
#Google #GSoC #Finnish
0
0
0
Jarkko Sakkinen
jarkko
Escaping the reality to the world of chainsaws :-)
https://www.youtube.com/watch?v=92eifEm0m7w
#chainsaw
https://www.youtube.com/watch?v=92eifEm0m7w
#chainsaw
0
0
0
Jarkko Sakkinen
jarkko
definitely not going to comment to the LWN FOSDEM article :-) i said what i wanted on topic and used my freedom of speech... not the end of the world.
0
0
0
Jarkko Sakkinen
jarkko
julia is cool i use it as my calculator but it is somewhat unstable still (saw the article in LWN).
0
0
2
Jarkko Sakkinen
repeated
repeated
Jason Becker
jsonbecker@indieweb.socialTeen Vogue is still the media we need, this time publishing Dear Trans Kids, You Don’t Need the Government’s Permission to Exist. https://www.teenvogue.com/story/dear-trans-kids-raquel-willis
0
9
0
Jarkko Sakkinen
jarkko
I like to be more hobbyist kernel developer and maintainer than professional kernel developer and maintainer :-)
I made the right call for me of not going to a Linux company after my industry sabbatical.
#linux #developer #maintainer
I made the right call for me of not going to a Linux company after my industry sabbatical.
#linux #developer #maintainer
0
1
3
Jarkko Sakkinen
jarkko
@oleksandr @josefbacik oh dear...
My recent take on topic: https://social.kernel.org/notice/AqdTaAU90fB1H7rlzM
Not discussing about it further :-) People can go nuts.
My recent take on topic: https://social.kernel.org/notice/AqdTaAU90fB1H7rlzM
Not discussing about it further :-) People can go nuts.
0
0
0
Jarkko Sakkinen
repeated
repeated
Jukka O. Kauppinen
jukkaokauppinen@mastodontti.fiSuomen pelimuseo viettää lauantaina kahdeksansia syntymäpäiviään. Ainutlaatuisena herkkuja synttäreillä tarjoillaan myös livemusiikkia. Retropelillisen ja museollisen ohjelman lisäksi luvassa onkin myös väkevää kitarasankarimeininkiä Romeo Knightin custom-soitinarsenaalin ja Basscadetin SID-thereminin kera.
Ja huom: synttäriä voi katsoa myös museon Areenalla ja Paradroidsin keikka on IRL live, sitä saa tulla katsomaan ihan muutaman metrin päästä.
https://www.v2.fi/uutiset/pelit/39578/
0
3
1
@Aissen Thanks for asking that. I'll put a remark to the cover letter. It would not be a problem for me personally. My argument comes from more like doing right things right from the process angle
Unfortunately Ihave had not time to push forward since I've been fixing Windows build issue :-) After I've done my release critical fixes for the next Polkadot release (for PolkaVM) I plan to put focus on this again.
Fixing Windows build was good learning otho. This is how you bootstrap a build for arbitrary target so that the build system won't trip and it will work out Linux/macOS/Windows:
https://github.com/paritytech/polkavm/blob/7715ad466e2d084e86e01e8341eb53ad0d86c3c0/crates/polkavm-test-data/build.rs
Nothing complicated but finding the simple recipe that actually works is sometimes tedious :-) I did not find any example that would be as generically applicable as this...
Unfortunately Ihave had not time to push forward since I've been fixing Windows build issue :-) After I've done my release critical fixes for the next Polkadot release (for PolkaVM) I plan to put focus on this again.
Fixing Windows build was good learning otho. This is how you bootstrap a build for arbitrary target so that the build system won't trip and it will work out Linux/macOS/Windows:
https://github.com/paritytech/polkavm/blob/7715ad466e2d084e86e01e8341eb53ad0d86c3c0/crates/polkavm-test-data/build.rs
Nothing complicated but finding the simple recipe that actually works is sometimes tedious :-) I did not find any example that would be as generically applicable as this...
2
0
1
Jarkko Sakkinen
jarkko
@Aissen
I did that consideration actually.
Here's the summary of reasons of using C for that driver at minimum for the first RFC patch set:
1. The existing code base is in C.
2. I'm not an expert on V4L2.
3. I'm pretty seasoned with the Linux driver model.
I.e. if you start to do too much to the domain per, there might be something "unimportant looking" that you look as "garbage", while you're actually removing something that does something useful.
This is IMHO pretty sound way to look at it. Since it is my hobby project given feedback, I might then re-consider re-implementing it in Rust. It is actually good comment to add to the cover letter.
IMHO, no matter who was doing this I make the right *first* call both from "respect the creators" and also technical angle. I cycled SGX patch set for over two years so writing the same driver a few times is like nothing ;-)
I did that consideration actually.
Here's the summary of reasons of using C for that driver at minimum for the first RFC patch set:
1. The existing code base is in C.
2. I'm not an expert on V4L2.
3. I'm pretty seasoned with the Linux driver model.
I.e. if you start to do too much to the domain per, there might be something "unimportant looking" that you look as "garbage", while you're actually removing something that does something useful.
This is IMHO pretty sound way to look at it. Since it is my hobby project given feedback, I might then re-consider re-implementing it in Rust. It is actually good comment to add to the cover letter.
IMHO, no matter who was doing this I make the right *first* call both from "respect the creators" and also technical angle. I cycled SGX patch set for over two years so writing the same driver a few times is like nothing ;-)
1
0
1