Posts
191
Following
31
Followers
191
Linux Kernel developer and maintainer
🇵🇱 🇪🇺 🇰🇷 🇮🇱 🇺🇦 🇨🇭
IRC: krzk
Kernel work related account. Other accounts of mine: @krzk@mastodon.social
krzk
repeated
vbabka

Vlastimil Babka

Thanks Pope for making me angry enough! Don't like your fundraising campaign style, but it worked! #DronesNotWhiteFlags
2
2
14
krzk

Krzysztof Kozlowski

If you ever wondered how Linux kernel can handle multiple devices sharing the same GPIO, you got one more reason to go to Seattle this April:
https://sched.co/1aPvr

My second talk got accepted to LinuxCon / Open Source Summit NA 2024.
0
1
8
krzk

Krzysztof Kozlowski

About current EU and Polish farmer protests, let's digest this meme. Left pic is from Poland, where Polish farmers protest with Soviet Union flag and banner saying:
"Puting clean up mess with Ukraine, Brussels and our government."

Right picture is from Ukraine (quite old btw)...
0
0
1
krzk
repeated
monsieuricon

K. Ryabitsev

In the face of hundreds of thousands murdered in Ukraine, and millions more displaced fleeing Russian military aggression, it is hard to focus on the death of one man. And yet, Navalny meant a lot to the Russian opposition and his death is just another proof that Putin's regime is criminal to the core and cannot be dealt with by appeasement or backroom deals. Ukrainians are the only force actively fighting the Kremlin mafia regime and we should continue to give them all they need to achieve a swift and decisive victory.
0
17
28
krzk

Krzysztof Kozlowski

Is DT schema validation of DTS boards helpful or not? Get ready to find it out during my talk on EOSS 2024 conference in April:
https://sched.co/1aBEf
See you in Seattle!
0
3
9
krzk

Krzysztof Kozlowski

10 years ago I sent a patch to fix one compatible in one Marvell SoC board:
https://lore.kernel.org/linux-devicetree/1410884282-18041-1-git-send-email-k.kozlowski@samsung.com/
Obvious fix but was never picked up.

In 2021 Sebastian tried to fix it:
https://lore.kernel.org/linux-devicetree/20210412230320.382885-2-sebastian.reichel@collabora.com/

Now in 2023 and 2024, Duje tries the same:
https://lore.kernel.org/linux-devicetree/20240125-brownstone-typo-fix-v2-1-45bc48a0c81c@skole.hr/

Will it succeed?
2
1
8
krzk

Krzysztof Kozlowski

Linux v6.8-rc1 comes with new document describing coding style for DTS (Devicetree sources):
https://www.kernel.org/doc/html/latest/devicetree/bindings/dts-coding-style.html

This marks the end of many unwritten rules, varying between subsystems and maintainers. At least, like with every coding style document, in theory. :)
2
10
22
krzk

Krzysztof Kozlowski

Edited 10 months ago
I was always using git branch --edit-description && git format-patch && git send-email, but now I tried preparing and sending patchset with b4 (b4 prep && b4 send). It works great! It is trivial in use and really solves the workflow. I cannot understand why people still Cc wrong people or are unable to send one patchset properly threaded.

Edit: --edit-cover->--edit-description
3
1
15
krzk
repeated
abelvesa

Abel Vesa

FYI, Qualcomm Snapdragon X Elite (X1E80100) now boots to shell with today's -next.

More support is already sent on the list for review:
https://lore.kernel.org/all/?q=X1E80100

And here is a public branch with all support currently available on top of -next:
https://git.codelinaro.org/abel.vesa/linux/-/tree/x1e80100-next
2
7
18
krzk

Krzysztof Kozlowski

Edited 11 months ago
Tensor is coming to the next Linux kernel: v6.8!
I just applied last patches for Linux kernel bringing support for the Google Tensor GS101 SoC (derivative of Samsung Exynos):
https://lore.kernel.org/linux-samsung-soc/170249498744.308886.17508790332822828341.b4-ty@linaro.org/T/#u

Commits will hit tomorrow's linux-next and probably next week I will send pull request with them to SoC (@arnd@society.oftrolls.com and Olof) for the next merge window. Good job Peter Griffin and @LinaroLtd :)
3
13
39
krzk
repeated
q3k@social.hackerspace.pl

q3k blobcatcoffee

I can finally reveal some research I've been involved with over the past year or so.

We (@redford, @mrtick and I) have reverse engineered the PLC code of NEWAG Impuls EMUs. These trains were locking up for arbitrary reasons after being serviced at third-party workshops. The manufacturer argued that this was because of malpractice by these workshops, and that they should be serviced by them instead of third parti
es.

1/4

6
58
2
krzk
repeated
oleksandr@natalenko.name

Oleksandr Natalenko, MSE

A reminder about what Muscovy did to us in 1932/33: https://en.wikipedia.org/wiki/Holodomor. Today is the Remembrance Day: https://en.wikipedia.org/wiki/Holodomor_Memorial_Day

0
3
4
krzk
repeated
anneapplebaum@journa.host

Anne Applebaum

Today is the annual day of remembrance for the Holodomor, the Ukrainian famine. 90 years ago Stalin sent activists to confiscate food from Ukrainian peasants. Millions died.
To mark this day, Putin sent dozens of drones to attack Kyiv.
Like Stalin, Putin wants to erase Ukraine.

2
8
2
krzk

Krzysztof Kozlowski

Edited 11 months ago
Looking at Devicetree sources changes (DTS) could give some insight into which ARM64 platforms are the most active. DTS represents the real hardware, thus any new hardware-block for an existing SoC, new SoC or new board, require new DTS changes. It's an approximation, easy to measure and still quite informative. Let's take a look - the most developed ARM64 platforms in the upstream Linux kernel since last LTS (v6.1):

$ git diff --dirstat=changes,1 v6.1..v6.6 -- arch/arm64/boot/dts/ | sort -nr
44.6% arch/arm64/boot/dts/qcom/
12.2% arch/arm64/boot/dts/ti/
10.4% arch/arm64/boot/dts/freescale/
10.1% arch/arm64/boot/dts/rockchip/
5.0% arch/arm64/boot/dts/nvidia/
4.3% arch/arm64/boot/dts/mediatek/
3.9% arch/arm64/boot/dts/renesas/
3.5% arch/arm64/boot/dts/apple/
3.4% (the rest)
2.2% arch/arm64/boot/dts/amlogic/

Almost 45% of all changes to ARM64-related hardware in the upstream kernel were for Qualcomm SoCs and boards. That's quite a stunning number.
0
1
5
krzk
repeated
monsieuricon

K. Ryabitsev

When patchwork integration is configured, b4 will now retrieve the CI status of each patch as well.
5
9
34
krzk

Krzysztof Kozlowski

Edited 1 year ago
Just reviewed a patch with... four comments coming entirely from my templates. No need to write anything, just hit some templates. Two out of these four comments were for not using in-kernel tools for patch submission/testing (checkpatch.pl and get_maintainer.pl). Eh. :(
2
0
1
krzk

Krzysztof Kozlowski

I announced it before on social.kernel.org, mailing lists and finally in the Linux kernel (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c25223cba5aa9a536392933782d4a7df71d9093b). So one more time, same announcement:
None of the Samsung and Samsung Foundry platforms can bring any new `dtbs_check W=1` warning.

Contributor can easily test it, so sending code which introduces such warnings is considered close to sending code which does not compile. Fast step to get your maintainer grumpy.
0
1
6
krzk

Krzysztof Kozlowski

Nice follow-up of Monday's Plumber's talk - Powering up “discoverable bus-attached” devices on DT-based platforms - BoF session with the same title:
https://lpc.events/event/17/contributions/1654/
It seems @abelvesa and Bartosz have now a acceptable solution to implement.
0
0
2
krzk
repeated
jejb@mastodon.online

James Bottomley

@linuxplumbersconf Youtube Live Stream URLs are now available on the Schedule Overview page (https://lpc.events/event/17/timetable/#all).

Find the track you want and click the paperclip on the upper right corner to bring up the Live Stream Link

2
14
2
krzk

Krzysztof Kozlowski

Edited 1 year ago
Some weeks ago people got scammed on Booking.com with "confirmation of payment method" or whatever they called it. Booking.com systems allowed scammers to send to customers messages about need to pay again. Second time. Booking.com denies.

So here it is: Booking.com still is not secure and scammers are active. Message I just got:
1
0
2
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: