Posts
270
Following
39
Followers
287
Linux Kernel developer and maintainer
#standwithukraine 🇵🇱 🇪🇺 🇺🇦 🇨🇭
IRC: krzk
Kernel work related account. Other accounts of mine: @krzk@mastodon.social
krzk

Krzysztof Kozlowski

Reply to @trini@floss.social
@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
krzk

Krzysztof Kozlowski

Reply to @trini@floss.social
@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
krzk

Krzysztof Kozlowski

Reply to @EUCommission@ec.social-network.europa.eu
@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
krzk

Krzysztof Kozlowski

Reply to @krzk
And here is the long version from OSS Japan:
https://youtu.be/mF3MQYH3x3s?si=vXBEm8EZIRUohhg3
0
0
1
krzk

Krzysztof Kozlowski

Reply to @Logical_Error@fosstodon.org
@Logical_Error This is list of vendors, as explained on earlier slides.
0
0
1
krzk

Krzysztof Kozlowski

Reply to @Logical_Error@fosstodon.org
@Logical_Error I don't understand. Qualcomm is the platform.
1
0
0
krzk

Krzysztof Kozlowski

First pulls merged to Linux SoC tree as part of new co-maintainership done!
https://web.git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git/commit/?h=arm/fixes&id=a3b80161fbd06b5dbc0af8f29f8ae58c4aebf0b2
1
1
5
krzk

Krzysztof Kozlowski

Edited 23 days 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
krzk

Krzysztof Kozlowski

Reply to @krzk
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
krzk

Krzysztof Kozlowski

Edited 1 month 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
krzk

Krzysztof Kozlowski

Reply to @corbet
@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
krzk

Krzysztof Kozlowski

Reply to @krzk
You should have named the talk: why Linux kernel is a giraffe?
0
0
1
krzk

Krzysztof Kozlowski

Many types of nodes in the Linux kernel explained by Bartosz Golaszewski from Qualcomm at OSS Summit Japan.
#OSSumit
1
0
2
krzk

Krzysztof Kozlowski

Reply to
@llvm of course it's off, because it requires careful management how you actually resolve conflict, so only good resolutions are recorded. It's additional, complicating step, thus must be conscious opt in...
0
0
0
krzk

Krzysztof Kozlowski

If you ever wondered where do we stand in Linux kernel with DTS validation (dtbs_check) of various platforms, which architectures are fully compliant and where we see nice progress, please join my session on 9th of December in Tokyo during Open Source Summit Japan 2025: Status of DTS Validation in Linux Kernel
https://sched.co/29Foi

I will also have a shortened version at the Linux Plumbers Conference, just a few days after.

#OSSummit #OSSJapan2025 #LinuxPlumbers
0
1
5
krzk
repeated
anneapplebaum@journa.host

Anne Applebaum

This is not a peace plan. It is a proposal that weakens Ukraine and divides America from Europe, preparing the way for a larger war in the future. In the meantime, it benefits unnamed Russian and American investors, at the expense of everyone else.
https://www.theatlantic.com/ideas/2025/11/trumps-war-peace/685024/?gift=hVZeG3M9DnxL4CekrWGK3x5H8-x30wTOq6lDtv0xjW4&utm_source=copy-link&utm_medium=social&utm_campaign=share

1
7
2
krzk

Krzysztof Kozlowski

Reply to @hanfi@social.troll.academy
@hanfi @gregkh Making them public would help people to avoid wasting time in the future by adding the author's email address to ai-slop filters / PLONK. Or adding their domain because sometimes that's representing a company approach.
0
0
0
krzk

Krzysztof Kozlowski 

$ git describe 
v6.18-rc3
$ git shortlog -s -n --no-merges

Oh! 5th place!

Don’t stop me now

I’m having such a good time

I’m having a ball

Don’t stop me now

0
1
8
krzk

Krzysztof Kozlowski

SoC maintainership in the Linux kernel (long time ago called arm-soc) is growing into a group of maintainers. Four new people joined @arnd for SoC: Alexandre Belloni, Linus Walleij and me (yay!) as co-maintainers, and @fustini as a reviewer:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b2a578f3127ab9ef80114cef9b20a2b42a8ee77a

Arnd, previously the sole SoC maintainer, handled pull requests and patches from several other sub-maintainers for each SoC sub-architecture (e.g. Qualcomm, NXP) and other driver trees. The SoC tree was one of the busiest, if not the busiest, trees in kernel - visible on @lwn.net graph: https://lwn.net/Articles/981742/

With this change the load will hopefully spread.
0
9
25
krzk
repeated
kernellogger@hachyderm.io

Thorsten Leemhuis (acct. 1/4)

Edited 2 months ago

TWIMC, the "Linus opposes Link: tags with links to the patch submission" is saga over, as Linus wrote:

""[…] I do think that at least if people use the different domain, I won't complain.

I'm still not convinced it's a great idea, but at least it means that the "this is the source of the commit" is clearly separate from the "this is actual background". […]""

https://lore.kernel.org/all/CAHk-%3Dwj5MATvT-FR8qNpXuuBGiJdjY1kRfhtzuyBSpTKR%2B%3DVtw@mail.gmail.com/

0
3
3
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: