Posts
4830
Following
321
Followers
490
Linux kernel hacker and maintainer etc.

OpenPGP: 3AB05486C7752FE1
jarkko

Jarkko Sakkinen

Edited 1 year ago
En käytä ruokalähettipalveluja, koska bisnesmalli on moraaliton. Omistajien verojen maksu on taas tämän tosiasian valkopesua.Toisten selkänahasta revitty fyffe on väärin, vaikka siitä maksaisi kuinka paljon veroja.

https://www.iltalehti.fi/kotimaa/a/b1cd31b2-5992-4302-ad4c-9d88e38f7fb2

#foodora #wolt
1
4
14
jarkko

Jarkko Sakkinen

Reply to @jarkko
@dpom @neovim A quote from Helix home page: "By starting from scratch we were able to learn from our experience with Vim and make some breaking changes."

This is totally incorrect. It is a different beast. Is Eclipse vim "with some breaking changes"?

Sorry, now I think I've flushed all this out of my system :-) Apologies...
0
0
2
jarkko

Jarkko Sakkinen

Reply to @jarkko
@dpom @neovim And people doing their "new" and "better" thing tend to get bored fast too: https://github.com/ogham/exa/issues/1243. I mean vim and neovim have decades of time span. E.g. the first Amiga version of Vim was implemented in 1988 being older project than even Linux kernel. Many of the maintainers of the new better things were not even born yet.
1
0
1
jarkko

Jarkko Sakkinen

Reply to @jarkko
@dpom @neovim Also I hate when people claim a language being "memory safe". No human creation is. It is for sure a language with strong memory safety properties. I like brutal honesty more than being sexy.
1
0
0
jarkko

Jarkko Sakkinen

Reply to @jarkko
@dpom @neovim E.g. https://social.kernel.org/notice/AbfRBmFLZVwkDl4ei8
1
0
0
jarkko

Jarkko Sakkinen

Reply to @dpom@fosstodon.org
@dpom @neovim Yeah, it is like Haskell community but with volume :-) Try to pointing out a real issue in Rust and you feel like that you are speaking with someone from the Church of Scientology. I still like and use the language but I fully receive and understand your comment.
1
0
1
jarkko

Jarkko Sakkinen

One thing where I would use #rustlang rewrite: vim/neovim clone. Helix/Amp etc. have the problem that they try to do something new.

Actually the best would be if @neovim would join the club of Firefox, Linux etc. and provide shenanigans for rewriting parts of it in Rust. I promise to contribute in this effort, if that ever happens (no time for working on the shenanigans unfortunately).

2
1
3
jarkko

Jarkko Sakkinen

Reply to @vbabka
@vbabka very nice
0
0
1
jarkko

Jarkko Sakkinen

totally missed this https://git-scm.com/docs/git-worktree
0
0
1
jarkko

Jarkko Sakkinen

Reply to @jarkko
Edited 1 year ago

OK, a bit more intensive to get the spacing right (or readable):

>>> ' '.join(list(map(lambda x: x[::-1], list(map(lambda i: val[::-1][i:i + 4], range(0, len(val), 4)))[::-1])))
'1 0001 0001 1001 1110'
0
0
0
jarkko

Jarkko Sakkinen

Reply to @jarkko
i like more traditional calls rather than fancy set theory alike syntax
1
0
0
jarkko

Jarkko Sakkinen

Edited 1 year ago

printing hex in the #python shell:

>>> val = bin(0x1119e)[2:]
>>> ' '.join(list(map(lambda i: val[i:i + 4], range(0, len(val), 4))))
'1000 1000 1100 1111 0'

#note

1
0
0
jarkko

Jarkko Sakkinen

I like the #BeagleBone layout in #BeagleV:

https://www.beagleboard.org/boards/beaglev-ahead

Very nice indeed, should get one.

#riscv #beagleboard
0
0
0
jarkko

Jarkko Sakkinen

Reply to @mcdanlj@social.makerforums.info
@mcdanlj it happens, yes
0
0
0
jarkko

Jarkko Sakkinen

Reply to @risc_v@noc.social
@risc_v nice beaglebone alike layout! hope to get one some day for sure
0
0
0
jarkko
repeated
risc_v@noc.social

RISC-V

.@beagleboardorg launched the BeagleV®-Fire, a new SBC that opens up new horizons for developers, tinkerers and more to explore the vast potential of architecture and FPGA technology: https://riscv.org/news/2023/11/beagleboard-org-makes-fpga-and-risc-v-accessible-with-new-beaglev-fire-single-board-computer-at-150/?hss_channel=tw-2694452875

Original tweet: https://twitter.com/risc_v/status/1723024225127076007

1
1
1
jarkko
repeated
pid_eins@mastodon.social

Lennart Poettering

Edited 1 year ago

Did you know you could control brightness of the red dot on the i of the "ThinkPad" on the top-side of your thinkpad? I sure didn't:

this turns it off:

echo 0 | sudo tee /sys/class/leds/tpacpi\:\:lid_logo_dot/brightness

and this turns it on:

echo 255 | sudo tee /sys/class/leds/tpacpi\:\:lid_logo_dot/brightness

I don't really know what this information is good for, but hey, isn't it awesome to have a 1px display on the outside of your laptop?

7
17
4
jarkko

Jarkko Sakkinen

Reply to @foone@digipres.club
@foone could not agree more. also when doing API/ABI it is good to use explicit size types so that the binary interface stays constant for 32-bit and 64-bit builds. Makes debugging experience so much more lean.
0
0
3
jarkko

Jarkko Sakkinen

Reply to @cfbolz@mastodon.social
Edited 1 year ago
@cfbolz I do that sort of thing over here occasionally and informally. E.g. I had this bug that I was hunting for over a month (yep, was total nightmare at times but I learned RISC-V assembly in the process so I guess it was for profit): https://github.com/keystone-enclave/keystone/issues/378

Then I wrote this post to have something generically applicable to try out in future when I have paging issues in RISC-V: https://social.kernel.org/notice/AbcKucebyfykZkSo4W. I don't want to keep this too formal. I try to remember adding #note to everything that I might want to checkup at times to get some ideas. Sort of scrap book in Mastodon 🙂

It is pretty easy to recall at least the year when I was working "something", and thus I feel that a single hashtag can help a lot already and is low-barrier at the same time.
0
0
1
jarkko

Jarkko Sakkinen

Reply to @jarkko
@liw Physical accident along the lines of Ariane flight V88 is entirely possible in Rust, as it was in ADA. The exception is different (integer overflow) but similar in the sense that you have a default exception behaviour, which can trip your system in unfortunate circumstances.
0
0
0
Show older
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: