Posts
278
Following
39
Followers
290
Linux Kernel developer and maintainer
#standwithukraine πŸ‡΅πŸ‡± πŸ‡ͺπŸ‡Ί πŸ‡ΊπŸ‡¦ πŸ‡¨πŸ‡­
IRC: krzk
Kernel work related account. Other accounts of mine: @krzk@mastodon.social
GitHub: https://github.com/krzk/
Traveling Instagram / Wanderquak: https://www.instagram.com/wanderquak/
Home brewery: https://brewalot.ch
Our gardening (and worm farm!): https://growalot.ch
@jann If only there was one tree for entire kernel, where everyone would be merging and managing simultaneously... if only ever someone invented a non-distributed revision control system which would help in achieving that. That distributed thing is also so annoying!
0
0
2

Krzysztof Kozlowski

Edited 3 days ago
I just finished updating Ansible scripts for the new 64x core AWS instance and it is already happy building mainline Linux kernel maintainer trees!

Thanks to #Qualcomm for sponsoring the machine.
0
0
2

Krzysztof Kozlowski

Edited 6 days ago
@ljs @lwn @corbet For specific details you would need to go to @monsieuricon rants and emails (or other kernel maintainers trying to run their own mailservers... discussed few times recently on IRC), but in overview: Google and Microsoft in order to protect their email users with lowest possible cost on their side, block entire networks without possibility to challenge or improve it by blocked mail admin. Your IP history of not-sending spam does not even matter - they will block it and don't care.

For a few days already sending emails from korg to anyone @outlook.com is blocked by Microslop.
1
0
0
@corbet @lwn Yes, of course you are right. I even had the same thoughts later - objective news credibility hurt plus possible lawsuits.
1
0
1
@lwn I am in the process of migrating my @kernel.org email setup away from Gmail to Fastmail. Not because I have trouble sending email. I can send easily... the problem is people won't be able to send to me.

I already was not subscribed to most of the kernel mailing lists and used lei/public-inbox. Now I dropped remaining few and move to korgalore for these (workflows, ksummit etc): https://korgalore.docs.kernel.org/
0
0
3

Krzysztof Kozlowski

In case you missed the announcement:
Both - Google/Gmail and Microsoft/Outlook - probably should be considered as evil and non-cooperative email providers.

Our decentralized workflow met reality of big monopolies caring only about themselves. Basically Google and Microsoft (lack of) response is actively impacting kernel development in a negative way.

I know this post will be ignored, so how about removing Google and Microsoft @LWN Kernel Development Statistics, so they will notice the problem?
3
0
4
@monsieuricon Minneapolis? US? No, no, nope, heck no.
1
0
1

Krzysztof Kozlowski

Who would think that removing myself from Linux kernel maintainers was such a good feeling. :)

Naaah, I'm a bit joking, just a proper thing to do instead of hoarding maintainers entry and not replying to emails.
0
0
3
@trini @hzulla That "standard way" was actually developed by someone, e.g. company or hobbyists, so cost money/time. Lack of such investment is not a scandal. It's really harmful language, because it suggests there is here some sort of malice or incompetence or just negligence. Basically it feels like years of mine and your work were part of that negligence. But no.

Our choices or economies are driven by demand and there was no demand for generic bootable ARM phone or laptop. Demand was for a cheap phone or laptop. There are BTW reasons why there is no x86 (laughing at Intel Atom) in embedded, IoT or phone/tablet market. That "general purpose bootloader and OS install" comes with a cost and there was and there is no demand for it.

Scandal would be if someone could not even develop that "general purpose bootloader and OS install", because of vendor lockdown. This is actually partially true for mobile market due to secure boot restrictions, but not for arm64 laptops, not for embedded/IoT.
1
0
1
@trini @hzulla Nothing is locked on Qualcomm ARM laptops. After 15 years to can still develop generic purpose loader or kernel... But if you want someone else to do your job (like they did on ACPI), that's a bit different question and not really a scandal. Scandal is if vendor would lock you out of doing it. Here no one is locked out and you have the freedom to implement whatever you find necessary. What others did not implement in SW what you find necessary is not a scandal.
1
0
1
@EUCommission Picture of "Discover EU" in your post is showing famous Landwasser Viaduct with Swiss train in SWITZERLAND. This is not EU.
1
0
3
And here is the long version from OSS Japan:
https://youtu.be/mF3MQYH3x3s?si=vXBEm8EZIRUohhg3
0
0
1
@Logical_Error This is list of vendors, as explained on earlier slides.
0
0
1
@Logical_Error I don't understand. Qualcomm is the platform.
1
0
0

Krzysztof Kozlowski

1
1
5

Krzysztof Kozlowski

Edited 1 month ago
"... I'll be going very, very, very fast. (...) I work for Qualcomm, I'm maintainer, taratatata..."

That's how you don't waste time of the audience during your speech. :)

Tokyo was cool, that was my third visit to Japan and second trip to Tokyo. But beside the city, time spent for Linux Plumbers Conference is as usual priceless. See you next year in Prague!

https://youtu.be/AN_3EA7gv04?si=1eBljSyw57zuzcNt&t=5
2
3
6
It was just 8 hours for Loongarch contribution and ~2 days for Aspeed (that's also much bigger). Pretty good response time!
0
0
3

Krzysztof Kozlowski

Edited 2 months ago
I don't want to take all the credits, but FWIW, after pointing out publicly DTBs check compliance warnings for some platforms during my OSS Japan talk, two platforms/archs already received patches to fix several warnings (Loongarch and Aspeed).

It seems I will need to keep repeating this talk :)

https://sched.co/29Foi
1
1
7
@corbet We were hanging out in a bar on 39th floor and all felt suddenly we have enough and should call it a day.. :)
0
0
2
You should have named the talk: why Linux kernel is a giraffe?
0
0
1
Show older