Krzysztof Kozlowski
Posts
191Following
31Followers
191🇵🇱 🇪🇺 🇰🇷 🇮🇱 🇺🇦 🇨🇭
IRC: krzk
Kernel work related account. Other accounts of mine: @krzk@mastodon.social
Krzysztof Kozlowski
krzk
@kernellogger It boils down whether ACPI is properly implemented on given platform. There are ARM64 platforms running correctly under ACPI, e.g. most of the ARM64 servers, and you don't care about such differences.
The trouble starts when ACPI is not there (so almost all embedded designs, mobile phones/tables) or ACPI is somehow botched (e.g. Qualcomm Snapdragon compute platforms and laptops based on it), because then you go with Devicetree/DTS and everything starts... But such platforms are not consumer devices, usually. And really the Qualcomm Snapdragon for laptops should have just used ACPI.
RE: https://fosstodon.org/@kernellogger/112871174600451364
The trouble starts when ACPI is not there (so almost all embedded designs, mobile phones/tables) or ACPI is somehow botched (e.g. Qualcomm Snapdragon compute platforms and laptops based on it), because then you go with Devicetree/DTS and everything starts... But such platforms are not consumer devices, usually. And really the Qualcomm Snapdragon for laptops should have just used ACPI.
RE: https://fosstodon.org/@kernellogger/112871174600451364
3
0
3
I’ve edited out the link. The LKML patch clearly states that the GPU requires OEM signing; nothing more.
Correct but why is that a problem? The ZAP firmware file needed for this will be most likely available. At least it is available already for two of mentioned earlier Lenovo laptops: Thinkpad Yoga Slim 7 and ThinkPad T14s.
Dmitry’s unimportant and harmless cleanup spurred some weird, harming gossips or uncertainties…
1
0
2
@artagnon @kernellogger And I forgot - also Lenovo ThinkPad T14s, the third consumer-available laptop.
0
0
0
@artagnon @kernellogger Since I am one of folks who receives/gets-cc all the patches for all Qualcomm Snapdragon X1 Elite laptops (and I work on this with Dmitry), I can tell you that several laptops are already supported in decent way. The support varies, because it is work in progress and laptops do not work with ACPI under Linux (ask Qualcomm), thus require DTS.
Except reference or developer devices we already have: Lenovo Thinkpad Yoga Slim 7x and ASUS Vivobook S15.
There could be more easily, but someone has to actually buy that device and submit DTS. Adding support Lenovo Slim 7x was pretty trivial, according to Srinivas who posted the patches.
So which exactly "first-hands" reports do you mean? People trying to run random kernel without DTS hoping that ACPI will work? That never worked any of these devices...
Except reference or developer devices we already have: Lenovo Thinkpad Yoga Slim 7x and ASUS Vivobook S15.
There could be more easily, but someone has to actually buy that device and submit DTS. Adding support Lenovo Slim 7x was pretty trivial, according to Srinivas who posted the patches.
So which exactly "first-hands" reports do you mean? People trying to run random kernel without DTS hoping that ACPI will work? That never worked any of these devices...
1
0
1
@artagnon @kernellogger With such clickbaits, Phoronix goes from poor source of knowledge about Linux kernel to "junk" source.
0
0
0
@artagnon @kernellogger The Phoronix clickbait still goes? That's so bollocks and so weird because Michael Larabel usually understands that stuff... Can we stop spreading this sort of FUD?
All GPUs for all upstream supported boards are enabled. Nothing got disabled by
"default". You have usable laptops. And whatever shady deals you mention, is so imprecise that not worth responding...
All GPUs for all upstream supported boards are enabled. Nothing got disabled by
"default". You have usable laptops. And whatever shady deals you mention, is so imprecise that not worth responding...
1
0
1
Krzysztof Kozlowski
repeated
repeated
A video directly confirms a Russian missile strike on "Okhmatdyt" in Kyiv. It wasn't intercepted and didn't deviate from its coordinates - it was aimed precisely there to cause maximum casualties and inflict the most pain.
SBU investigators have determined that Russia struck "Okhmatdyt" with a Kh-101 missile.
#RussiaIsATerroristState #ArmUkraineNow #Ukraine #EU #Europe #NATOSummit #NatoAllies
SBU investigators have determined that Russia struck "Okhmatdyt" with a Kh-101 missile.
#RussiaIsATerroristState #ArmUkraineNow #Ukraine #EU #Europe #NATOSummit #NatoAllies
2
5
2
Rob also shared guideline on such DT work, so few more details here:
https://lore.kernel.org/linux-devicetree/CAL_JsqJp133hGSkja9tabtsE9D7MSA9JErVkmkcy91piHMgfwg@mail.gmail.com/
https://lore.kernel.org/linux-devicetree/CAL_JsqJp133hGSkja9tabtsE9D7MSA9JErVkmkcy91piHMgfwg@mail.gmail.com/
0
0
3
Krzysztof Kozlowski
krzk
Edited 5 months ago
Since a year we got some contributions for converting Devicetree bindings from TXT to DT schema as part of some sort mentorship programs. This is great although leads to some misunderstandings in that work, considering mentorships did not ask DT maintainers about some sort of guidance. To clarify:
1. Please convert bindings which have active DTS users. First choose bindings with DTS built by arm64 defconfig, then next choice by arm multi_v7 defconfig. Then any other ARM or different architecture DTS.
2. Be sure dt_bindings_check (including yamllint) and checkpatch pass without any warnings. See writing-schema.rst document.
3. Be sure DTS using this binding passes dtbs_check validation. If this means binding needs to be adapted during conversion, mention briefly in commit message changes done comparing to pure TXT->DT schema conversion. Sometimes DTS has to be fixed. Sometimes both - DTS and binding - must be changed, because actual ABI (Linux drivers) is different.
1. Please convert bindings which have active DTS users. First choose bindings with DTS built by arm64 defconfig, then next choice by arm multi_v7 defconfig. Then any other ARM or different architecture DTS.
2. Be sure dt_bindings_check (including yamllint) and checkpatch pass without any warnings. See writing-schema.rst document.
3. Be sure DTS using this binding passes dtbs_check validation. If this means binding needs to be adapted during conversion, mention briefly in commit message changes done comparing to pure TXT->DT schema conversion. Sometimes DTS has to be fixed. Sometimes both - DTS and binding - must be changed, because actual ABI (Linux drivers) is different.
1
0
4
Krzysztof Kozlowski
krzk
That's an interesting session: @cas explaining current status of upstream U-Boot on Qualcomm robotic platforms - using mainline kernel DTS and getting to SystemReady IR.
Slides: https://calebs.dev/u-boot24.pdf
https://www.kitefor.events/events/linaro-connect-24/submissions/183
Slides: https://calebs.dev/u-boot24.pdf
https://www.kitefor.events/events/linaro-connect-24/submissions/183
0
11
29
Krzysztof Kozlowski
krzk
Edited 6 months ago
@abelvesa explaining the hacking setup used during his bringing up of the Qualcomm X Elite compute platform in Linaro:
https://www.kitefor.events/events/linaro-connect-24/submissions/182
https://www.kitefor.events/events/linaro-connect-24/submissions/182
1
1
4
@kernellogger And the cherry on the cake is last sentence: "We’ve published an experimental, raw disk image for a Debian installer..."
so good luck finding there any Qualcomm commits:
https://git.codelinaro.org/linaro/qcomlt/demos/debian-12-installer-image/-/commits/master
so good luck finding there any Qualcomm commits:
https://git.codelinaro.org/linaro/qcomlt/demos/debian-12-installer-image/-/commits/master
1
0
2
@kernellogger It's sad that article misses that most of the upstream work was actually done by @abelvesa from Linaro. :(
1
0
2
Krzysztof Kozlowski
krzk
Just a reminder: only a week to hear me babbling about Linux kernel DTS validation and shared reset GPIOs on Embedded Open Source Summit/OSSNA 2024. Don't miss it and come to say hi!
EOSS: https://sched.co/1aBEf
OSSNA: https://sched.co/1aPvr
EOSS: https://sched.co/1aBEf
OSSNA: https://sched.co/1aPvr
0
3
5
Krzysztof Kozlowski
krzk
@kernellogger Oh, interesting, I did not know about the "delay" argument. The no-stable is so far a bit per subsystem. Some of them, like I think netdev, rely on marking things explicitly cc-stable. Most don't care thus anything with Fixes tag is picked up.
1
0
0
Krzysztof Kozlowski
krzk
@kernellogger That's reasonable classification. Some kernel users also need some time to take new kernel release, thus actual tests and results might be coming 1-2 years after a release.
0
0
1
Krzysztof Kozlowski
krzk
@kernellogger Linus expressed few times that if something was broken for very long time, was not working for long time, it should not be treated as urgent/important fix thus should not go to current RC cycle. Instead, should go via normal development branch, so for the next merge window. I know that stable folks have different point of view - they also expressed it.
I personally follow exactly the same approach in handling fixes: if something was broken for long time, it is regular bugfix thus goes to "for-next" branch, not "fixes / for-linus / for-current-rc".
Now, if a regression was unnoticed for 8 years, it kinda fits above criteria.
I personally follow exactly the same approach in handling fixes: if something was broken for long time, it is regular bugfix thus goes to "for-next" branch, not "fixes / for-linus / for-current-rc".
Now, if a regression was unnoticed for 8 years, it kinda fits above criteria.
1
0
3
@sam_ravnborg so far lore got my emails, but that does not mean they will pass spam filters on receiver's side.
0
0
0
Krzysztof Kozlowski
krzk
@sam_ravnborg I use b4, but maybe you meant b4 relay? I used kernel.org, but I wonder how emails from other domain will be treated (From is @linaro, smtp is mail.kernel.org).
3
0
0