I always wanted a simple way to put the phone to silent mode when e.g. placing it on the table next to the 🛏️ . Since Biemster got NFC to work on the Oneplus 6/6T (https://github.com/biemster/pmos-openbox-conky/blob/main/nxp_nci_i2c.py) we can leverage that and have feedbackd's profile adjusted when certain RFIDs are seen (https://source.puri.sm/Librem5/feedbackd/-/merge_requests/154). For this to land we want to move the NFC support from a python script to s.th. like nfcd (https://github.com/biemster/pmos-openbox-conky/pull/18#issuecomment-2653920089). Help on this would be appreciated.
[$] LWN.net Weekly Edition for February 13, 2025 https://lwn.net/Articles/1008279/ #tech #linux
Did you know that in the early 1990s, shortly before the first smart phones dropped, "smart calculators" were poised to become the hubs of our of digital lives?
Here's a photo of one such device from Casio. For more calculator history, check out https://lcamtuf.coredump.cx/blog/calculators/
Build a Mars Rover in your home.
Tiny Mouse Ring Uses Prox Sensors
https://hackaday.com/2025/02/10/tiny-mouse-ring-uses-prox-sensors/
EndeavourOS Mercury landed with Linux kernel 6.13, Plasma 6.2.5, Xfce 4.20, dark themes by default, and better installer functionality.
https://linuxiac.com/endeavouros-mercury-brings-fixes-dark-themes-and-improved-installer/
Unix recap for week 6/2025
https://discu.eu/weekly/unix/2025/6/
Get RSS feeds and support this bot with the premium plan: https://discu.eu/premium
A Rust-for-Linux policy document https://lwn.net/Articles/1008865/ #tech #linux
2/ …exceptionally, for Rust, a subsystem may allow to temporarily break Rust code. The intention is to facilitate friendly adoption of Rust in a subsystem without introducing a burden to existing maintainers who may be working on urgent fixes for the C side. The breakage should nevertheless be fixed as soon as possible, ideally before the breakage reaches Linus.
For instance, this approach was chosen by the block layer […]
We believe this approach is reasonable […]"'
Miguel Ojeda, lead maintainer for the "#Rust for #Linux" project, announced a
"Rust #kernel policy":
https://lore.kernel.org/all/CANiq72m-R0tOakf=j7BZ78jDHdy=9-fvZbAT8j91Je2Bxy0sFg@mail.gmail.com/
"'Given the discussions in the last days, I decided to publish this page with what our understanding is:
https://rust-for-linux.com/rust-kernel-policy
I hope it helps to clarify things. I intend to keep it updated as needed."'
To quote one bit:
1/ '"Who is responsible if a C change breaks a build with Rust enabled?
The usual kernel policy applies. […]
However, …
"Just transcoding some audio on the command line on my phone... like ya do"
Good news: GIMP 3.0 RC3 Released
T-Mobile goes live with beta of satellite phone service for the US https://go.theregister.com/feed/www.theregister.com/2025/02/10/tmobile_goes_live_with_beta/ #news
@mntmn assembly was easy, on first boot we were disappointed by a lot of display artifacts - turns out I had not gotten the connection to the display panel quite good enough. Once we fixed that everything works. This thing is super pretty! Thanks!
Welcome Terence Eden as #curl commit author 1342: https://github.com/curl/curl/pull/16270
3/ Ohh, and if you haven't seen this, see also this post from @sima and the reply from @airlied about the #Rust for #Linux DMA drama:
'"The r4l team and drm maintainer team have this sort of thing in hand, it's not like we don't understand the community of the Linux kernel, and having this first reaction to blow shit up and dramatise it just isn't helpful."'