Notices by Jani Nikula (jani@fosstodon.org)

Since v6.10 the Linux kernel depends on Python to build, at least if you need support for the drm/msm driver (CONFIG_DRM_MSM=y).

This is used to generate headers from source xml during build, not an unreasonable scenario. I much prefer Python over C or Perl or shell scripting for this type of file and string processing.

Yet I'm unsure what the stance for the Python build dependency is among the powers that be. It may have snug in under their radar.

Should I try it with drm/i915...?

#kernel

I don't know who needs to hear this, maybe you, but you don't need to be good at your hobbies to love them. Enjoy and have fun.

@corbet @brauner

I was going to reply to the original post that we generally try to avoid NAK in the drm subsystem, but then, uh oh.

I think it's something we strive for, anyway.

@nixCraft

I always liked this:

/* We do this three times for luck */
for (i = 0; i < 3; i++) {
intel_de_write(dev_priv, DPLL(pipe), dpll);
intel_de_posting_read(dev_priv, DPLL(pipe));
udelay(150); /* wait for warmup */
}

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/display/intel_dpll.c?h=v6.7-rc2#n1638

@kernellogger I'd think the first response should fall on the downstream kernel providers i.e. distros, especially if the reporter does not know how to build and run upstream kernels and test fixes.

@sima @linear @airlied

On a related note, in most cases any real name policy just crumbles when you realize how difficult it is to actually enforce in practise. Usually it becomes a "name that seems plausibly real to some group of people with a certain cultural background policy".