@kvaneesh @srivatsabhat @sumit

@kvaneesh @srivatsabhat @sumit

Thanks everyone for joining us for a great day of talks and discussions. See you in next meetup

@kvaneesh @srivatsabhat @sumit

Last talk of the day is Who and what's eating my CPUs? Pinpoint it with FlameGraph Visualization by Kaiwan N. Billimoria

@sumit @kvaneesh @srivatsabhat

After a quick coffee break, we are now switching to lighting talks

First one is Hello b4: Modernizing the Linux Kernel Patch Workflow by Radhey Pandey

Hello b4: Modernizing the Linux Kernel Patch Workflow by Radhey Pandey

@kvaneesh
Last talk of this session is
From Fixes to LTS: The Life of a Linux Kernel Patch by Radhey Pandey

@sumit
Last talk of this session is
IOMMUFD: From VFIO Containers to Guest-Owned Page Tables by Harsha Vardhan

@kvaneesh
After a wonderful lunch and great hallway conversations, we are back with next set of talks.

Next is Hey Yocto, build me a custom embedded Linux! Er, no by Kaiwan N. Billimoria

@sumit
After a wonderful lunch and great hallway conversations, we are back with next set of talks.

Next is PatchWise: Automating Linux Kernel Patch Review with AI + Static Analysis by Aditya Chillara

@sumit The second talk in this track is ARM MPAM & MPAM-Fb: Hardware Resource Partitioning in Linux via resctrl by Srivathsa L. Rao

@kvaneesh
Second talk of the track is Safe thread killing for Linux daemons by mixing signals and ARM Assembly by Harshal Dev

I present the latest in U-Boot Qualcomm development. This is a pre-production Fairphone 5 running U-Boot as a full replacement to Qualcomms proprietary EDK2 stack

it has working drivers for the DSI interface, display controller, panel, and a bunch more pesky prerequisites :D

This means unlike in the typical case on a phone where the display has already been configured for us by edk2, we have to turn on all the regulators, configure all the clocks and phys, program the display controller and basically do everything ourselves.

This is the first command mode panel I have working and being a whole different soc to my initial bringup it proves that the drivers are flexible enough to enable broad support.

i hope to eventually land these drivers upstream, starting with the common clock framework port.

track B starts with From NIC to Userspace: Understanding the Linux Network Data Path by Alok Bhatt. Thanks to @kvaneesh for coordinating this track

The track A is starting. First talk is Performance improvements for Linux file based encryption, leveraging Block I/O crypto and hardware inline encryption in storage controllers by Akhilesh Patil. Thanks to @sumit for coordinating the track A

The full schedule of the day:

Thank you @jejb for wonderful talk for developers and leaders. Very good insights

Some key insights from his talk

The keynote of the day is by @jejb about A Brief History of Linux and Open Source: How a bunch of hackers took on the Corporate world and Won

Linux kernel meetup Bangalore, Sep 2026 edition is here. Thanks to Microsoft and @srivatsabhat and Prasad for the logistics

Is your hardware setup secretly exposing your proprietary AI models? 🔒

Join Behan Webster on September 9th to see how Arm CCA and GPU Device Assignment allow you to process sensitive data in hardware-isolated execution environments ("Realms") without sacrificing GPU acceleration.

Register here: https://bit.ly/4frKV67 🔗
#Arm #CCA #ConfidentialComputing #Linaro #OnlineWebinar

CFP for second OSS-India is live now
https://events.linuxfoundation.org/open-source-summit-india/program/cfp/
This will be held in Jio World Convention Centre, Mumbai.

Key dates:
CFP Closes:  Wednesday, 4 March
CFP Notifications: Thursday, 2 April
Schedule Announcement: Tuesday, 7 April
Event Dates: 16-17 June 2026

GPLv2 affirmation…

I don’t generally post here as people have probably noticed, but here’s a pdf of a recent court ruling, and this turns out to be the easiest way for me to link to a copy of it, since I don’t really maintain any web presence normally and I don’t want to post pdf’s to the kernel mailing lists or anything like that.

And the reason I want to post about it, is that it basically validates my long-held views that the GPLv2 is about making source code available, not controlling the access to the hardware that it runs on.

The court case itself is a mess of two bad parties: Vizio and the SFC. Both of them look horribly bad in court - for different reasons.

Vizio used Linux in their TVs without originally making the source code available, and that was obviously not ok.

And the Software Freedom Conservancy then tries to make the argument that the license forces you to make your installation keys etc available, even though that is not the case, and the reason why the kernel is very much GPLv2 only. The people involved know that very well, but have argued otherwise in court.

End result: both parties have acted badly. But at least Vizio did fix their behavior, even if it apparently took this lawsuit to do so. I can’t say the same about the SFC.

Please, SFC - stop using the kernel for your bogus legal arguments where you try to expand the GPLv2 to be something it isn’t. You just look like a bunch of incompetent a**holes.

The only party that looks competent here is the judge, which in this ruling says

Plaintiff contends the phrases, “machine-readable” and “scripts used to control compilation and installation” support their assertion in response to special interrogatory no. 4 that Defendant should “deliver files such that a person of ordinary skill can compile the source code into a functional executable and install it onto the same device, such that all features of the original program are retained, without undue difficulty.”

The language of the Agreements is unambiguous. It does not impose the duty which is the subject of this motion.

Read as a whole, the Agreements require Vizio to make the source code available in such a manner that the source code can be readily obtained and modified by Plaintiff or other third parties. While source code is defined to include “the scripts used to control compilation and installation,” this does not mean that Vizio must allow users to reinstall the software, modified or otherwise, back onto its smart TVs in a manner that preserves all features of the original program and/or ensures the smart TVs continue to function properly. Rather, in the context of the Agreements, the disputed language means that Vizio must provide the source code in a manner that allows the source code to be obtained and revised by Plaintiff or others for use in other applications.

In other words, Vizio must ensure the ability of users to copy, change/modify, and distribute the source code, including using the code in other free programs consistent with the Preamble and Terms and Conditions of the Agreements. However, nothing in the language of the Agreements requires Vizio to allow modified source code to be reinstalled on its devices while ensuring the devices remain operable after the source code is modified. If this was the intent of the Agreements, the Agreements could have been readily modified to state that users must be permitted to modify and reinstall modified software on products which use the program while ensuring the products continue to function. The absence of such language is dispositive and there is no basis to find that such a term was implied here. Therefore, the motion is granted.

IOW, this makes it clear that yes, you have to make source code available, but no, the GPLv2 does not in any way force you to then open up your hardware.

My intention - and the GPLv2 - is clear: the kernel copyright licence covers the software, and does not extend to the hardware it runs on. The same way the kernel copyright license does not extend to user space programs that run on it.